open-index/open-npm huggingface dataset:
npm package: @mcadam/portfinder
Description: CLI to find available ports for monorepo development with git worktrees
Author: Omar
Latest version: 1.0.0

# Portfinder

A simple CLI tool to find available ports for monorepo development with multiple git worktrees.

## Platform Support

**⚠️ Mac/Linux only** - This tool requires shell command substitution support (`$()`), which is not available in Windows cmd.exe.

## Installation

Install in your monorepo root:

```bash
npm install portfinder
# or
pnpm add portfinder
```

## Usage

Use command substitution to set the PORT environment variable:

```bash
PORT=$(portfinder 3000) next dev
```

### In package.json scripts

```json
{
  "scripts": {
    "dev": "PORT=$(portfinder 3000) next dev --turbopack"
  }
}
```

### With multiple environment variables

```json
{
  "scripts": {
    "dev": "PORT=$(portfinder 3000) API_PORT=$(portfinder 4000) node server.js"
  }
}
```

### Monorepo setup with different base ports

```json
// apps/web/package.json
{
  "scripts": {
    "dev": "PORT=$(portfinder 3000) next dev"
  }
}

// apps/admin/package.json
{
  "scripts": {
    "dev": "PORT=$(portfinder 3100) next dev"
  }
}

// apps/api/package.json
{
  "scripts": {
    "dev": "PORT=$(portfinder 3200) node server.js"
  }
}
```

## How it works

1. When you run `portfinder 3000`, it checks if port 3000 is available
2. If port 3000 is taken, it automatically finds the next available port (3001, 3002, etc.)
3. The command outputs only the port number to stdout
4. Shell command substitution captures this output and sets it as an environment variable

## Example workflow with git worktrees

When running multiple worktrees of the same monorepo:

- **Worktree 1**: `pnpm dev` → apps run on ports 3000, 3100, 3200
- **Worktree 2**: `pnpm dev` → apps automatically use ports 3001, 3101, 3201
- **Worktree 3**: `pnpm dev` → apps automatically use ports 3002, 3102, 3202

No port conflicts, no manual configuration needed!

## License

MIT
npm package: @mcaddon/kit
Description: Handles building, packaging, and copying an mcaddon project
Latest version: 0.2.0

# @mcaddon/kit

Easiest way to get started with a new Minecraft Addon with GameTest integration.

Quickest way to get started:

```bash
npm init mcaddon my-addon
cd my-addon
npm install # or pnpm install, yarn, etc.
npm run dev
```

## License

[MIT](../../LICENSE)
npm package: @mcaligares/button-component
Description: *Psst — looking for an app template? Go here --> [sveltejs/template](https://github.com/sveltejs/template)*
Author: mcaligares@gmail.com
Latest version: 0.0.1

*Psst — looking for an app template? Go here --> [sveltejs/template](https://github.com/sveltejs/template)*

---

# component-template

A base for building shareable Svelte components. Clone it with [degit](https://github.com/Rich-Harris/degit):

```bash
npx degit sveltejs/component-template my-new-component
cd my-new-component
npm install # or yarn
```

Your component's source code lives in `src/Component.svelte`.

You can create a package that exports multiple components by adding them to the `src` directory and editing `src/index.js` to reexport them as named exports.

TODO

* [ ] some firm opinions about the best way to test components
* [ ] update `degit` so that it automates some of the setup work


## Setting up

* Run `npm init` (or `yarn init`)
* Replace this README with your own


## Consuming components

Your package.json has a `"svelte"` field pointing to `src/index.js`, which allows Svelte apps to import the source code directly, if they are using a bundler plugin like [rollup-plugin-svelte](https://github.com/sveltejs/rollup-plugin-svelte) or [svelte-loader](https://github.com/sveltejs/svelte-loader) (where [`resolve.mainFields`](https://webpack.js.org/configuration/resolve/#resolve-mainfields) in your webpack config includes `"svelte"`). **This is recommended.**

For everyone else, `npm run build` will bundle your component's source code into a plain JavaScript module (`dist/index.mjs`) and a UMD script (`dist/index.js`). This will happen automatically when you publish your component to npm, courtesy of the `prepublishOnly` hook in package.json.
npm package: @mcaligares/react-native-google-cast
Description: React Native wrapper for the Google Cast SDK for iOS and Android
Author: Petr Bela
Latest version: 4.0.12

[![npm version](https://badge.fury.io/js/react-native-google-cast.svg)](https://badge.fury.io/js/react-native-google-cast)

# react-native-google-cast

This library wraps the native Google Cast SDK for Android and iOS (and maybe web/Chrome in the future), providing a unified JavaScript interface.

It is written in TypeScript so types will always be up-to-date.

## Version overview

| RNGC | React Native | Purpose                                                                                                                                               |
| ---- | ------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
| 1.x  | 🤷‍♂️           | Old version implemented for Google Cast SDK v2 with manual discoverability. Not maintained anymore.                                                   |
| 3.x  | >=0.40       | Rewrite of the library for Google Cast SDK v3 with automatic session management. Only bug fixes will be merged.                                       |
| 4.x  | >=0.60       | Current version with a completely rewritten API, closely resembling native Android/iOS(/Chrome?) APIs. We highly recommend to use the latest version. |

## Documentation

https://react-native-google-cast.github.io/docs/getting-started/installation

## Example

Refer to the [example](example/) folder to find a React Native version of the CastVideos reference app.

## Playground

Refer to the [playground](playground/) folder to find a sample app demonstrating the available APIs provided by the library.

## Expo

As this library requires native dependencies that are not available in the default Expo bundle, you'll need to [eject to bare workflow](https://docs.expo.io/bare/customizing/). That will enable you to continue using Expo for the parts of the app that don't need casting, and then test Cast-specific functionality in a standalone build.

## Troubleshooting

See [Troubleshooting](https://react-native-google-cast.github.io/docs/getting-started/troubleshooting) in the docs.

## Contribution

1. Read [CONTRIBUTING.md](CONTRIBUTING.md)
2. Fork the repo
3. Implement your shiny new thing
4. Demonstrate how to use it in the [playground project](playground/)
5. Document the functionality in JSDoc and the [docs](docs/)
6. Create a pull request