open-index/open-npm huggingface dataset:
npm package: @raycohen-test-org/react-scripts
Description: Configuration and scripts for Create React App.
Latest version: 1.1.1

# react-scripts

This package includes scripts and configuration used by [Create React App](https://github.com/facebookincubator/create-react-app).<br>
Please refer to its documentation:

* [Getting Started](https://github.com/facebookincubator/create-react-app/blob/master/README.md#getting-started) – How to create a new app.
* [User Guide](https://github.com/facebookincubator/create-react-app/blob/master/packages/react-scripts/template/README.md) – How to develop apps bootstrapped with Create React App.
npm package: @raycohen/react-scripts
Description: Configuration and scripts for Create React App.
Latest version: 1.1.1

# react-scripts

This package includes scripts and configuration used by [Create React App](https://github.com/facebookincubator/create-react-app).<br>
Please refer to its documentation:

* [Getting Started](https://github.com/facebookincubator/create-react-app/blob/master/README.md#getting-started) – How to create a new app.
* [User Guide](https://github.com/facebookincubator/create-react-app/blob/master/packages/react-scripts/template/README.md) – How to develop apps bootstrapped with Create React App.
npm package: @raydak/eslint-plugin-pulumi
Description: ESLint plugin with useful rules for Pulumi code.
Author: raydak
Latest version: 1.0.3

# Pulumi ESLint Plugin

[![npm version](https://img.shields.io/npm/v/@raydak/eslint-plugin-pulumi)](https://www.npmjs.com/package/@raydak/eslint-plugin-pulumi)
[![license](https://img.shields.io/npm/l/@raydak/eslint-plugin-pulumi)](LICENSE)
[![build status](https://github.com/raydak-labs/eslint-plugin-pulumi/actions/workflows/ci.yml/badge.svg)](https://github.com/raydak-labs/eslint-plugin-pulumi/actions)

ESLint plugin for Pulumi projects using TypeScript to enforce best practices and coding standards.

This repository is derived from [pulumi/eslint-plugin-pulumi](https://github.com/pulumi/eslint-plugin-pulumi) which is not really maintained.

## Differences to [pulumi/eslint-plugin-pulumi](https://github.com/pulumi/eslint-plugin-pulumi)

- this plugin is in active development
- lints bad usages of `OutputInstance`s correctly (see below)
- contains a recommended ruleset

### Example of bad code being detected

```ts
const db = new aws.rds.Instance(...);
new aws.ssm.Parameter("db-port", {
  name: "/my-db/port",
  type: aws.ssm.ParameterType.String,
  value: `${db.port}`, // this is wrong
  // value: pulumi.interpolate`${db.port}`, // this is better
});
```

## Usage

Install the dependencies:

```sh
npm install -D @raydak/eslint-plugin-pulumi eslint typescript-eslint
# or pnpm add -D @raydak/eslint-plugin-pulumi eslint typescript-eslint
```

This plugin requires ESLint v9.0.0 or later using the flat configuration.

Configure ESLint by adding an `eslint.config.mjs`, see [eslint.config.mjs](../test-playground/eslint.config.mjs) for an example:

```js
import { defineConfig } from "eslint/config";
import tseslint from "typescript-eslint";
import eslintPluginPulumi from "@raydak/eslint-plugin-pulumi";

export default defineConfig(
  {
    languageOptions: {
      // configure the parser explicitly
      parser: tseslint.parser,
      // required for pulumi eslint rules as it requires type information
      parserOptions: {
        projectService: true,
      },
    },
  },
  eslintPluginPulumi.configs.recommended,
);
```
npm package: @raydeck/create-weweb-component
Description: With NPM:
Author: Weweb
Latest version: 1.0.13

# @weweb/create-component

## Scaffolding Your First [weweb.io](https://www.weweb.io/) custom elements

With NPM:

```bash
$ npm init @weweb/component
```

With Yarn:

```bash
$ yarn create @weweb/component
```

Then follow the prompts!

You can also directly specify the project name and the type of source code you want to develop via additional command line options. For example, to scaffold a custom element project, run:

```bash
npm init @weweb/component my-element --type element
```

Currently supported type are:

- `element`
- `section`
npm package: @raydeck/fastlane
Description: JS Interface for many fastlane actions designed for react-native 
Author: Ray Deck
Latest version: 2.0.1

# Fastlane-js

Javascript interface to Fastlane

## Requirements

**Fastlane** is required to have been installed: use `gem install Fastlane`

## Installation

```
yarn add @raydeck/fastlane
```

## Class Fastlane

### async doAction(action, arguments) => Promise<Any>

Returns the same result as running this Fastlane result in Ruby would. (note that there are excceptions where the Fastlane socket driver delivers suboptimal serializations of Ruby objects, such as with the action `adb_devices`). Starts the session automatically when you ask for the first action.

### async close() => Promise<Void>

Closes the connection to fastlane.

## async withFastlane(options: FastlaneOptions, func (fastlane: Fastlane)=> Promise)

The main helper function to control a Fastlane session.

- `options` (optional): Object of options to pass to the fastlane session:
  - `isInteractive: Boolean` whether to pass stdin/stdout of the socket server to the calling client. This should be `true` when you might need to respond to requests for, say, apple logins.
  - `port: Int` specify the port number of the connection (default `2000`)
- `func`: async function (returning a promise) containing the block of code to run during the Fastlane session, passed the `Fastlane` instance as its first and only argument. Note the session is initialized right before executing the function and closed right afterward.

## Example

```js
await withFastlane(async (fastlane) => {
  await fastlane.doAction("send_to_testflight", {
    application_id: "xxxx" /*...*/,
  });
});
// is the same as
await withFastlane({ isInteractive: true, port: 2000 }, async (fastlane) => {
  await fastlane.doAction("send_to_testflight", {
    application_id: "xxxx" /*...*/,
  });
});
// is the same as
await withFastlane(async ({ doAction }) => {
  await doAction("send_to_testflight", { application_id: "xxxx" /*...*/ });
});
// is the same as
const fastlane = new Fastlane(2000, true);
await fastlane.doAction("send_to_testflight", {
  application_id: "xxxx" /*...*/,
});
fastlane.close();
// is the same as
const fastlane = new Fastlane();
await fastlane.doAction("send_to_testflight", {
  application_id: "xxxx" /*...*/,
});
fastlane.close();
```

## Additional Helper functions

### async init(isInteractive = true) => Socket

Imperatively initialize the child Fastlane server process and connect using sockets. The socket is returned as a convenience, but don't mess with it unless you really know what you are doing.

- **isInteractive**: Boolean of whether to pass stdin/stdout of the socket server to the calling client. This should be `true` when you might need to respond to requests for, say, apple logins.

**Note**: This is run by default at the start of `withFastlane`

### async close() => Void

Close the connection to the Fastlane socket server and terminate the Fastlane socket server process.

**Note**: This is run by default at the end of `withFastlane`
npm package: @raydeck/local-assets
Description: Elevate asset directories from designated dependencies to the module for distribution
Author: Ray Deck
Latest version: 1.3.3

# local-assets

Local asset hoister from dependencies

## Usage

```
❯ yarn -s local-assets --help
Usage: local-assets [options] [command]

Options:
  -h, --help       display help for command

Commands:
  start            hoist local assets from dependencies
  set-path <path>  set the local assets path (currently ./assets)
  set-usedev       use dev dependencies for asset path search (currently
                   false)
  set-nodev        do not use dev dependencies for asset path search
                   (currently false)
  help [command]   display help for command

```

## Commands

`local-assets` uses subcommands for its execution pattern

### local-assets start

Recursively copy the contents from the subdirectory paths specified by the "path" (e.g. `/assets`) from each dependency (and devDependency if that setting is on) to the "path" relative to project root. E.g. from dependency `my-dependency` files and folders in `node_modules/my_dependency/assets` into `./assets`.

### local-assets set-path <newPath>

Establish the relative path to both receive assets from and load them into your root project

### local-assets set-usedev

Use development dependencies (in `devDependencies`) as well as main `dependencies` to find assets

### local-assets set-nodev

Do not use development dependencies.
npm package: @raydeck/make-appsync-client
Description: Make modern apollo client linked to appsync
Author: Ray Deck
Latest version: 1.0.2


<a name="readmemd"></a>

# make-appsync-client


<a name="_librarymd"></a>


# @raydeck/make-appsync-client - v1.0.2

## Index

### Functions

* [makeClient](#const-makeclient)

## Functions

### `Const` makeClient

▸ **makeClient**(`__namedParameters`: object): *object*

*Defined in [src/index.tsx:15](https://github.com/rhdeck/make-appsync-client/blob/97cc77d/src/index.tsx#L15)*

**Parameters:**

▪ **__namedParameters**: *object*

Name | Type |
------ | ------ |
`graphqlEndpoint` | string |
`introspectionQueryResultData` | object |
`region` | string |

**Returns:** *object*

* **Provider**: *FunctionComponent‹object›*

* **client**: *ApolloClient‹NormalizedCacheObject›*
npm package: @raydeck/mcp-registry-validator
Description: A validator tool for MCP server.json files to ensure they meet publication criteria
Latest version: 1.0.0

# MCP Registry Validator

A TypeScript-based validator tool for MCP `server.json` files to ensure they meet publication criteria for the MCP registry.

## Installation

Install globally via npm:

```bash
npm install -g mcp-registry-validator
```

Or use with npx (no installation required):

```bash
npx mcp-registry-validator
```

## Usage

### Validate in current directory

```bash
npx mcp-registry-validator
```

This will look for `server.json` in the current directory.

### Validate in a specific directory

```bash
npx mcp-registry-validator path/to/directory
```

This will look for `server.json` in the specified directory.

### Validate a specific file

```bash
npx mcp-registry-validator path/to/server.json
```

This will validate the specific file at the given path.

## Exit Codes

- **0**: Validation successful, no errors found
- **1**: Validation failed with errors

## What it validates

The validator checks the following:

### Required Fields
- `$schema`
- `name`
- `title`
- `description`
- `version`
- `packages` (non-empty array)

### Field Length Limits
- `title`: max 50 characters
- `description`: max 100 characters
- `homepage`: max 200 characters

### Name Format
Must follow the pattern: `io.github.username/server` or `com.domain/server`

### Version Format
Must follow semantic versioning (e.g., `1.0.0`)

### Homepage (if present)
Must be a valid HTTP(S) URL

### Package Configuration
Each package must have:
- `registryType`: one of `npm`, `pypi`, `nuget`, `oci`, `mcpb`
- `identifier`: max 100 characters
- `version`
- `transport.type`: one of `stdio`, `sse`, `streamable-http`

### Environment Variables (if present)
- Descriptions must be max 200 characters
- Lists required environment variables

## Development

### Build

```bash
npm install
npm run build
```

### Test locally

```bash
npm run dev
```

## License

MIT
npm package: @raydeck/merge-graphql
Description: Stitch together graphql schemas from dependencies
Author: Ray Deck
Latest version: 1.2.0


<a name="_climd"></a>

# Usage
```bash
npx @raydeck/merge-graphql [options]
```
# Options
* -o --output \<`path-to-schema.graphql`> File to emit results to (default: `/Users/ray/Documents/GitHub/merge-graphql/schema.graphql`)
* -p --path \<`path-to-workspace`> Path to workspace (default: `/Users/ray/Documents/GitHub/merge-graphql`)

<a name="_librarymd"></a>


# @raydeck/merge-graphql - v1.2.0

## Index

### Functions

* [mergeDependencies](#mergedependencies)
* [mergeFromGlobs](#mergefromglobs)

## Functions

###  mergeDependencies

▸ **mergeDependencies**(`startPath`: string): *Promise‹string›*

*Defined in [index.ts:11](https://github.com/rhdeck/merge-graphql/blob/521df48/src/index.ts#L11)*

Extract and merge graphql schemas from dependencies into a single string.

Gets all from schemas/common and then just the ones for your project (identified in schemas/{name})

**Parameters:**

Name | Type | Default | Description |
------ | ------ | ------ | ------ |
`startPath` | string | process.cwd() | Path to start looking at package.json and associated node_modules  |

**Returns:** *Promise‹string›*

___

###  mergeFromGlobs

▸ **mergeFromGlobs**(`globs`: string[]): *Promise‹string›*

*Defined in [index.ts:36](https://github.com/rhdeck/merge-graphql/blob/521df48/src/index.ts#L36)*

Merge schema files found in an array of glob strings into a single schema file

**Parameters:**

Name | Type | Description |
------ | ------ | ------ |
`globs` | string[] | array of glob strings (ex: ./schemas/*.graphql)  |

**Returns:** *Promise‹string›*
npm package: @raydeck/passcode
Description: Random alphanumeric passcode generator
Author: Ray Deck
Latest version: 2.0.0

# passcode

Node.js passcode generator

## Installation

```
yarn add @raydeck/passcode
```

## Usage: makePasscode([length = 6], [characterset = "number"]): Promise<string>

### Return value

Promise for a string that contains the random passcode. Best used with async/await as in example below.

### Arguments

#### length

How long to make the passcode. Must be positive integer. Defaults to 6

#### characterset

Key of an avaiable set of characters to randomly generate from. Available keys:

1. number (digits 0-9)
2. alphanumeric (lowercase letters plus numbers)
3. loweralphanumeric (same as alphanumeric)
4. upperalphanumeric (uppercase letters plus numbers)
5. allalphanumeric (uppercase, lowercase and numbers - maximum entropy)
6. lowercase (lowercase letters a-z)
7. uppercase (uppercase letters a-z)

Defaults to "number".

## Example

```js
const makePasscode = require("@raydeck/passcode");

const sixDigitCode = await makePasscode();

const tenCharacterCode = await makePasscode(10, "alphanumeric");
```
npm package: @raydeck/react-native-fix-ios-server-port
Description: Package can change the port being used by the dev server.
Author: ironluffy55
Latest version: 1.0.0

# react-native-fix-server-port
Package can change the port being used by the dev server. 

Removes manual step for projects where dev server needs to run port different from 8081 (default). Which can save time if rm -rf node_module is executed a lot

Notes:
1. iOS only
2. New port is saved to package.json
3. Enter 'yarn rnsp' to start react-native server with the new port

Credit:
Package created using react-native template generated by 'react-native-cli-cli'

TODO:
This is a dirty method that changes the files I know x-ante are required for port change to work. Need to look at how dev server spins up so I can write more intelligent code