open-index/open-npm huggingface dataset:
npm package: @jscanvas/local-client
Description: This project was bootstrapped with [Create React App](https://github.com/facebook/create-react-app).
Latest version: 2.0.0

# Getting Started with Create React App

This project was bootstrapped with [Create React App](https://github.com/facebook/create-react-app).

## Available Scripts

In the project directory, you can run:

### `npm start`

Runs the app in the development mode.\
Open [http://localhost:3000](http://localhost:3000) to view it in the browser.

The page will reload if you make edits.\
You will also see any lint errors in the console.

### `npm test`

Launches the test runner in the interactive watch mode.\
See the section about [running tests](https://facebook.github.io/create-react-app/docs/running-tests) for more information.

### `npm run build`

Builds the app for production to the `build` folder.\
It correctly bundles React in production mode and optimizes the build for the best performance.

The build is minified and the filenames include the hashes.\
Your app is ready to be deployed!

See the section about [deployment](https://facebook.github.io/create-react-app/docs/deployment) for more information.

### `npm run eject`

**Note: this is a one-way operation. Once you `eject`, you can’t go back!**

If you aren’t satisfied with the build tool and configuration choices, you can `eject` at any time. This command will remove the single build dependency from your project.

Instead, it will copy all the configuration files and the transitive dependencies (webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except `eject` will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.

You don’t have to ever use `eject`. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.

## Learn More

You can learn more in the [Create React App documentation](https://facebook.github.io/create-react-app/docs/getting-started).

To learn React, check out the [React documentation](https://reactjs.org/).
npm package: @jscells/local-client
Description: This project was bootstrapped with [Create React App](https://github.com/facebook/create-react-app).
Latest version: 1.0.1

# Getting Started with Create React App

This project was bootstrapped with [Create React App](https://github.com/facebook/create-react-app).

## Available Scripts

In the project directory, you can run:

### `npm start`

Runs the app in the development mode.\
Open [http://localhost:3000](http://localhost:3000) to view it in the browser.

The page will reload if you make edits.\
You will also see any lint errors in the console.

### `npm test`

Launches the test runner in the interactive watch mode.\
See the section about [running tests](https://facebook.github.io/create-react-app/docs/running-tests) for more information.

### `npm run build`

Builds the app for production to the `build` folder.\
It correctly bundles React in production mode and optimizes the build for the best performance.

The build is minified and the filenames include the hashes.\
Your app is ready to be deployed!

See the section about [deployment](https://facebook.github.io/create-react-app/docs/deployment) for more information.

### `npm run eject`

**Note: this is a one-way operation. Once you `eject`, you can’t go back!**

If you aren’t satisfied with the build tool and configuration choices, you can `eject` at any time. This command will remove the single build dependency from your project.

Instead, it will copy all the configuration files and the transitive dependencies (webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except `eject` will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.

You don’t have to ever use `eject`. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.

## Learn More

You can learn more in the [Create React App documentation](https://facebook.github.io/create-react-app/docs/getting-started).

To learn React, check out the [React documentation](https://reactjs.org/).
npm package: @jschady/scaffold-cli
Description: AI-first CLI orchestrator for Next.js, Vercel, Supabase, and GitHub
Latest version: 0.1.2

# scaffold-cli

CLI tool for bootstrapping full-stack Next.js projects. Provisions GitHub, Supabase, and Vercel in a single command, keeps environment variables in sync, and stores all API tokens in your OS keychain.

## Install

```bash
npm install -g @jschady/scaffold-cli
```

## Prerequisites

Before running any commands, generate API tokens for each service:

- **GitHub** — Personal Access Token with `repo` and `delete_repo` scopes
- **Vercel** — API Access Token from `vercel.com/account/settings/tokens`
- **Supabase** — Access Token from `app.supabase.com/account/tokens`

## Usage

### `scaffold login`

Validates and stores your GitHub, Vercel, and Supabase tokens in the OS keychain. Run this once before anything else.

```bash
scaffold login
```

### `scaffold init`

Bootstraps a new full-stack project end-to-end. Creates a Next.js app, GitHub repo, Supabase project, and Vercel deployment, then wires up all environment variables automatically.

```bash
cd ~/projects
scaffold init
```

You will be prompted for:
- Project name
- Package manager (pnpm, bun, or npm)
- GitHub repo visibility
- Supabase region
- Which services to provision

After `init` completes, your project directory contains a `.scaffold/state.json` ledger (git-ignored) that tracks all provisioned resources.

### `scaffold sync`

Pulls the latest API keys from Supabase and env vars from Vercel, then writes them to `.env.local`. Run this from inside your project directory.

```bash
cd my-project
scaffold sync
```

### `scaffold check`

Verifies that all stored tokens are present and that each cloud service is reachable.

```bash
scaffold check
```

### `scaffold nuke`

Tears down all provisioned resources for the current project — deletes the GitHub repo, Supabase project, and Vercel project. Requires confirmation. Run from inside your project directory.

```bash
cd my-project
scaffold nuke
```

### `scaffold reflect`

*(Coming soon)*

## How tokens are stored

Tokens are stored in the native OS keychain (macOS Keychain, Windows Credential Manager, or Linux Secret Service) via `keytar`. They are never written to disk in your project directory.

## Project state

`scaffold init` creates a `.scaffold/state.json` file inside your project that tracks resource IDs for Vercel, Supabase, and GitHub. This file is automatically added to `.gitignore`. Do not delete it manually — `scaffold nuke` uses it to clean up resources.

## License

MIT