open-index/open-npm huggingface dataset:
npm package: @pcnate/raspberry-pi-camera
Description: nodejs camera application to connect to server via socket.io
Author: Nathan Baker
Latest version: 1.0.4

# raspberry-pi-camera
[![Build status](https://dev.azure.com/pcnate/raspberry-pi-camera/_apis/build/status/raspberry-pi-camera-CI)](https://dev.azure.com/pcnate/raspberry-pi-camera/_build/latest?definitionId=1)
![](https://img.shields.io/npm/v/@pcnate/raspberry-pi-camera.svg)
![](https://img.shields.io/github/license/pcnate/raspberry-pi-camera.svg)

nodejs raspberry pi camera application to upload images to server. It is designed to be setup once and left alone. Additional configuration will be added to the server side.

> You will need a server to receive the image stream generated by the camera. I recommend [raspberry-pi-camera-server](https://github.com/pcnate/raspberry-pi-camera-server)

# Standalone Install

1) `npm install -g @pcnate/raspberry-pi-camera`
2) probably need ot exit terminal and reopen/reconnect
3) `raspberry-pi-camera-config`
4) `raspberry-pi-camera`

# Automatic startup with pm2

1) `npm install -g pm2 @pcnate/raspberry-pi-camera`
2) probably need to exit terminal and reopen/reconnect
3) `pm2 startup`
4) `raspberry-pi-camera-config`
5) `pm2 start raspberry-pi-camera --name cam`
6) `pm2 save`

# Configuration

1) `raspberry-pi-camera-config`
2) enter url to upload to
3) leave GUID blank
4) leave image path alone, (stores in RAM to save SD card)
npm package: @pcode-at/eslint-config-typescript
Description: A shared ESLint configuration to be used across all pcode projects
Author: pcode
Latest version: 0.0.6

# @pcode-at/eslint-config-typescript

based on [@seancroach/eslint-config-typescript](https://github.com/seancroach/eslint-config-typescript)

## Highlights

-   Enforces all the recommended TypeScript practices
-   Ensures your code adheres to the [Prettier Style Guide](https://prettier.io/)
-   Lints your import statements to follow the best conventions
-   Applies best practices on ESLint directive comments such as
    `/* eslint-disable */`

Like many shared configurations, you _could_ write all the configurations
yourself, but why do that when it's already right here to use!

## Installation

`@pcode-at/eslint-config-typescript` has a few peer dependencies that have to
be downloaded alongside it:

-   [`eslint`](https://eslint.org/)
-   [`prettier`](https://prettier.io/)
-   [`typescript`](https://www.typescriptlang.org/)

Install `@pcode-at/eslint-config-typescript` and its peer dependencies through
`npm`:

```
npm install --save-dev @pcode-at/eslint-config-typescript eslint prettier typescript
```

## Usage

You can configure ESlint a variety of ways. We suggest to do a majority of your
configurations from your `package.json`:

```json
{
    "name": "my-new-project",
    "eslintConfig": {
        "extends": "@pcode-at/eslint-config-typescript"
    }
}
```

## License

This package is available as open source under the terms of the [MIT License](https://github.com/seancroach/eslint-config-typescript/blob/latest/LICENSE.md).
npm package: @pcode-at/tinacms-seo
Description: SEO package for TinaCMS
Author: @pcode-at
Latest version: 2.0.0

# TinaCMS SEO

## Mission and Vision
Our vision of this package is to create the one stop shop for all your SEO concerns using [TinaCMS](https://tina.io/), similar to the Wordpress Plugin [Yoast](https://yoast.com/wordpress/plugins/seo/).

## Getting started
Follow these 5 steps to include tinacms-seo in your project:

1. Install the package:

```
npm install @pcode-at/tinacms-seo
``` 

or

```
yarn add @pcode-at/tinacms-seo
``` 

 depending on your package manager.

**NOTE**: If you are using `yarn` (or an `npm` version that doesn't install peer dependencies automatically) then you have to install used peer dependencies by yourself manually:
```
yarn add next-seo
```
 


2. Import the required schema parts from the package:
```
import { defaultSeoPageProps, seoPageProps } from "@pcode-at/tinacms-seo";
```

3. Include it in your schema:

```
  ...
  {
      label: "Pages",
      name: "pages",
      path: "content/pages",
      fields: [
        seoPageProps,
        {
          ... fields
        },
      ],
      ...
    },
```

4. Congratulations! 🎉 Now you should see an editable SEO object in your sidebar:

![image](https://user-images.githubusercontent.com/29887207/161561181-4a2d6dae-a8f6-4cfd-8a5a-259f71222876.png)

![image](https://user-images.githubusercontent.com/29887207/161561313-4bd08fc9-e82d-4e9e-bea6-379351e298dc.png)

### Expert mode

For usability reasons we do not expose all fields in ```defaultSeoPageProps``` and ```seoPageProps```. If you have a usecase for full control about all seo relevant fields you can import ```expertDefaultSeoPageProps``` and ```expertSeoPageProps```.
npm package: @pcode-at/tsconfig
Description: A shared TypeScript configuration I use across my projects.
Author: pcode
Latest version: 0.0.5

# @pcode-at/tsconfig

A shared TypeScript configuration for pcode projects based on [@seancroach/tsconfig](https://github.com/seancroach/tsconfig).

## Highlights

-   Enables strict options which enforce type safety
-   Enables linting options which enforce a higher quality of code
-   Enables importing `.json` files directly within TypeScript
-   Targets Node v10 to ensure compatibility with all active LTS Node versions

Of course, you _could_ write all the configurations yourself, but why do that when
it's already right here to use!

## Installation

Install `@pcode-at/tsconfig` through `npm`:

```
$ npm install --save-dev @pcode-at/tsconfig
```

## Usage

In your `tsconfig.json` file, extend `@pcode-at/tsconfig` using the `extends` field:

```jsonc
{
    "extends": "@pcode-at/tsconfig"
    // ...
}
```

## License

This package is available as open source under the terms of the [MIT License](https://github.com/pcode-at/tsconfig/blob/latest/LICENSE.md).
npm package: @pcoliveira90/pdd
Description: Patch-Driven Development CLI — safe, resilient and guided code changes
Author: Paula Oliveira
Latest version: 0.6.1

# PDD - Patch-Driven Development

[![npm version](https://img.shields.io/npm/v/@pcoliveira90/pdd)](https://www.npmjs.com/package/@pcoliveira90/pdd)
[![CLI Self Validation](https://github.com/pcoliveira90/pdd/actions/workflows/cli-self-validation.yml/badge.svg)](https://github.com/pcoliveira90/pdd/actions/workflows/cli-self-validation.yml)
[![License: MIT](https://img.shields.io/github/license/pcoliveira90/pdd)](https://github.com/pcoliveira90/pdd/blob/main/LICENSE)
[![Node >=18](https://img.shields.io/badge/node-%3E%3D18-339933?logo=node.js&logoColor=white)](https://nodejs.org/)

> Entregue mudancas seguras em sistemas reais.

PDD e um framework orientado a CLI para bugfix e evolucao de features em sistemas existentes.  
Ele padroniza como o time investiga, planeja, valida e documenta mudancas.

Versoes por idioma: [README padrao](README.md) | [English](README.en.md)

## Por que usar PDD

- Execucao worktree-first para desenvolvimento paralelo mais seguro
- Artefatos estruturados de mudanca (`delta-spec`, `patch-plan`, `verification-report`)
- Fluxo consistente para Cursor, Claude Code e GitHub Copilot
- Quality gates nativos (`doctor`, validacao e checagens de CI)

## Instalacao

Requisitos:
- Node.js >= 18
- Git disponivel no PATH

Executar sem instalacao global (recomendado):

```bash
npx @pcoliveira90/pdd --version
```

Instalacao global (opcional):

```bash
npm install -g @pcoliveira90/pdd
pdd --version
```

## Inicio rapido

```bash
# 1) Inicialize o PDD no repositorio atual
npx @pcoliveira90/pdd init --here

# 2) Rode um fluxo de correcao
npx @pcoliveira90/pdd fix "login nao salva incomeStatus"
```

## Comandos principais

```bash
pdd init --here
pdd doctor
pdd status
pdd fix "descricao do bug" [--dry-run] [--no-validate] [--open-pr]
pdd version
```

Comando de analise por IA:

```bash
pdd-ai --provider=openai --task=analysis "descricao do bug"
```

## Resumo do fluxo

1. Entender comportamento atual e causa raiz
2. Gerar artefatos em `changes/<change-id>/`
3. Validar testes/lint/build
4. Preparar artefatos de PR e revisar na IDE

## Alinhamento entre IDEs

O PDD mantem intencoes equivalentes entre ferramentas:

- Cursor: `.cursor/commands/pdd-*.md`
- Claude Code: `.claude/commands/pdd-*.md`
- GitHub Copilot: `.github/prompts/pdd-*.prompt.md`

## Documentacao

- `docs/getting-started.md`
- `docs/installation-and-setup.md`
- `docs/fix-workflow.md`
- `docs/manifesto.md`

## Objetivo

Motor de execucao confiavel para mudancas seguras em software real.