open-index/open-npm huggingface dataset:
npm package: @shuvamk/create-node-server
Description: A CLI tool to create production-ready Node.js backend servers with TypeScript, Express, and best practices
Author: Shuvam Kumar
Latest version: 1.5.0

# Express TypeScript Starter

A production-ready Express.js starter template with TypeScript, featuring comprehensive tooling, security best practices, and monitoring capabilities.

## Features

- 🚀 **TypeScript** - Write better, more maintainable code
- 📊 **OpenTelemetry** - Distributed tracing out of the box
- 🔒 **Security** - Helmet, CORS, and rate limiting preconfigured
- 📝 **API Documentation** - Swagger/OpenAPI integration
- 🪵 **Logging** - Structured logging with Pino
- 🔍 **Error Tracking** - Sentry integration
- ⚡ **Performance** - Response compression
- 🧪 **Testing** - Jest setup for unit tests
- 💅 **Code Quality** - ESLint, Prettier, and Git hooks

## Quick Start

```bash
npx create-express-ts-starter my-app
cd my-app
npm install
npm run dev
```

## Available Scripts

- `npm run dev` - Start development server with hot reload
- `npm run build` - Build for production
- `npm start` - Start production server
- `npm run lint` - Lint code with ESLint
- `npm run format` - Format code with Prettier
- `npm test` - Run tests

## Environment Variables

Copy `.env.example` to `.env` and configure:

```bash
cp .env.example .env
```

See `.env.example` for all available options.

## Project Structure

```
src/
├── config/         # Configuration files
├── controllers/    # Route controllers
├── middleware/     # Express middleware
├── models/         # Database models
├── routes/         # Route definitions
├── services/       # Business logic
├── types/          # TypeScript types
├── utils/          # Utility functions
└── index.ts        # App entry point
```

## API Documentation

Swagger documentation is available at `/api-docs` when running the server.

## Monitoring & Observability

### Sentry
Error tracking and performance monitoring. Configure via `SENTRY_DSN` in `.env`.

### OpenTelemetry
Distributed tracing enabled by default. Configure endpoint via `OTEL_EXPORTER_OTLP_ENDPOINT`.

## Security

- Helmet for security headers
- CORS protection
- Rate limiting
- Request validation

## Contributing

1. Fork the repository
2. Create your feature branch
3. Commit using conventional commits
4. Push to your branch
5. Create a pull request

## License

MIT
npm package: @shuvi/dll
Description: update webpack development compiled speed
Latest version: 0.0.1-pre.6

# Dynamic DLL

update webpack development compiled speed 

## Steps

1. new a DynamicDll

    ```javascript
    const dynamicDll = new DynamicDll({
        cwd: process.cwd(), // the root dir of your app
        webpackLib: webpack, // webpack
        webpackPath: '', // webpackpath default ''
        tmpBase: join(cwd, DEFAULT_TMP_DIR_NAME), // Dynamic DLL files dir
        includesLibs, // the libary you want include
        excludeLibs, // the libary you want exclude
        shared, // mf shared of Dynamic DLL
      });
    ```

1. server static files of Dynamic DLL build

    [connect middleware type](https://github.com/senchalabs/connect#use-middleware)
    ```typescript
    dynamicDll.middleware = async (req: IncomingMessage, res: ServerResponse, next: (...args: any[]) => any){
        // ...
    }
    ```

1. set specific depConfig config what will be use Dynamic DLL's webpack
    ```typescript
    const depConfig = {};
    depConfig.module={
        // ...
    }
    depConfig.plugins={
        // ...
    }
        // ...
    dynamicDll.depConfig = depConfig; // at last
    ```
1. modifyWebpackChain by dynamicDll.modifyWebpack or dynamicDll.modifyWebpackChain if you use WebpackChain
   ```typescript
   const config = dynamicDll.modifyWebpack(orignalConfig);
   ```
   ```typescript
    chain = await dynamicDll.modifyWebpackChain(chain, resolveEntryFile)
    ```
1. make sure webpack entry is [dynamic-entry](https://webpack.js.org/configuration/entry-context/#dynamic-entry)
   1. config with webpack chain can do this step by [webpack-virtual-modules](https://www.npmjs.com/package/webpack-virtual-modules)
   ```typescript
   // origin config
   {
     entry:{
         main: 'index.js'
     }
   }
   // webpack chain
   chain.plugin('dll-virtual-modules-plugin').use(VirtualModulesPlugin,[
     {
        './virtual-modules.js': 'import ("index.js")',
     }
   ])
   ```
npm package: @shuvi/electron-cli
Description: Enable electron support for shuvi.
Latest version: 0.0.1-beta.54

# @shuvi/electron-cli

Enable electron support for shuvi.

## How to use

1. Install the package.
   ```
   yarn add -D @shuvi/electron-cli
   ```
2. Runt the start command.
   ```
    shuvi-electron start
   ```

## CLI Options

- `start` - start the electron in development mode

  ```
   Flags:
    --host  hostname
    --port  port
  ```

- `build` - bundle project in production mode.
  ```
   Env:
    OUTPUT_PATH    path to output path. (optional)
    PUBLIC_PATH    webpack public path. (optional)
  ```
npm package: @shuvi/swc-linux-arm-gnueabihf
Description: This is the **linux-arm-gnueabihf** binary for `@shuvi/swc`
Latest version: 1.0.0-rc.8

# `@shuvi/swc-linux-arm-gnueabihf`

This is the **linux-arm-gnueabihf** binary for `@shuvi/swc`
npm package: @shuvi/swc-linux-arm64-musl
Description: This is the **linux-arm64-musl** binary for `@shuvi/swc`
Latest version: 1.0.0-rc.8

# `@shuvi/swc-linux-arm64-musl`

This is the **linux-arm64-musl** binary for `@shuvi/swc`
npm package: @shuvi/swc-linux-x64-gnu
Description: This is the **x86_64-unknown-linux-gnu** binary for `@shuvi/swc`
Latest version: 1.0.0-rc.8

# `@shuvi/swc-linux-x64-gnu`

This is the **x86_64-unknown-linux-gnu** binary for `@shuvi/swc`
npm package: @shuvi/swc-linux-x64-musl
Description: This is the **linux-x64-musl** binary for `@shuvi/swc`
Latest version: 1.0.0-rc.8

# `@shuvi/swc-linux-x64-musl`

This is the **linux-x64-musl** binary for `@shuvi/swc`
npm package: @shuvi/swc-win32-arm64-msvc
Description: This is the **win32-arm64-msvc** binary for `@shuvi/swc`
Latest version: 1.0.0-rc.8

# `@shuvi/swc-win32-arm64-msvc`

This is the **win32-arm64-msvc** binary for `@shuvi/swc`
npm package: @shuvi/swc-win32-ia32-msvc
Description: This is the **win32-ia32-msvc** binary for `@shuvi/swc`
Latest version: 1.0.0-rc.8

# `@shuvi/swc-win32-ia32-msvc`

This is the **win32-ia32-msvc** binary for `@shuvi/swc`
npm package: @shuvi/swc-win32-x64-msvc
Description: This is the **x86_64-pc-windows-msvc** binary for `@shuvi/swc`
Latest version: 1.0.0-rc.8

# `@shuvi/swc-win32-x64-msvc`

This is the **x86_64-pc-windows-msvc** binary for `@shuvi/swc`
npm package: @shuyangli/spotify-cli
Description: CLI for building Spotify playlists and controlling Spotify Connect playback. Designed to be driven by an LLM agent.
Author: shuyangli
Latest version: 0.0.1

# spotify-cli

A small CLI for building Spotify playlists and controlling Spotify Connect
playback. Designed to be driven by a [Hermes
agent](https://hermes-agent.nousresearch.com/), but works fine standalone.

Every command emits a single JSON object/array on stdout. Errors land on
stderr in a `{"error": {...}}` envelope with a non-zero exit code.

## Install

```sh
npm install -g spotify-cli
```

Or from source:

```sh
git clone <this-repo>
cd spotify-cli && npm install && npm run build && npm link
```

Requires Node ≥ 20.

## Authenticate

1. Register an app at <https://developer.spotify.com/dashboard>.
2. In the app settings, add `http://127.0.0.1/callback` as a redirect URI.
   (The CLI uses an ephemeral loopback port — Spotify accepts any port for
   `127.0.0.1` redirects, but the URI must be registered.)
3. Export your client ID and run `auth login`:

```sh
export SPOTIFY_CLIENT_ID=xxxxxxxxxxxxxxxxxxxxxxxx
spotify-cli auth login
```

The token is cached at `~/.config/spotify-cli/token.json` (mode `0600`) and
auto-refreshed before expiry.

## Examples

```sh
# Search and build
spotify-cli search "miles davis" --type artist
spotify-cli playlist create --name "Tonight"
spotify-cli playlist add 7vxxx... spotify:track:aaa spotify:track:bbb

# Connect playback
spotify-cli devices list
spotify-cli playback transfer <deviceId> --play
spotify-cli playback play --context-uri spotify:playlist:7vxxx...
spotify-cli playback volume 30
```

See `spotify-cli --help` for the full surface.

## Rate limiting

Spotify enforces a per-app rolling 30-second quota. The CLI:

- Serializes outbound requests within a process and inserts a minimum
  inter-request gap (default 250 ms; override with
  `SPOTIFY_CLI_MIN_INTERVAL_MS`).
- Honors `Retry-After` on 429 responses with jittered retries.
- Backs off exponentially on 5xx (max 3 attempts).
- Refreshes the access token automatically on 401 (once per request).

**If you're driving this from an agent, never issue `spotify-cli` calls in
parallel** — the CLI's pacer only protects against intra-process bursts; the
quota is shared across all processes using the same app.

## Hermes skill

The `skill/` directory packages this CLI as a Hermes agent skill. See
[`skill/SKILL.md`](skill/SKILL.md). Publish with:

```sh
hermes skills publish skill --to github --repo <owner>/<repo>
```

## Development

```sh
npm install
npm test          # 57 unit/integration tests, no network
npm run build
npx tsx src/index.ts --help
```

## License

MIT
npm package: @shuyun-ep-team/create-app
Description: 数云项目模板集成cli
Author: @shuyun-ep-team
Latest version: 0.0.1

# @shuyun-ep-team/create-app

数云项目模板集成 cli

## Getting started

```sh
npm init @shuyun-ep-team/app

or

npx @shuyun-ep-team/create-app
```

## 项目配置

项目模板配置(src/congig/template.ts)

```js
// 项目模板列表(eg)
export const TEMPLATE_LIST = [
  {
    name: '麒麟企业版脚手架',
    value: 'npx @shuyun-ep-team/cli',
  },
  {
    name: '麒麟移动端项目',
    value: 'npx kylin-mobile -C',
  },
];
```

## 本地测试

```sh
1.打包编译
npm run build:test
2.测试
npm test
```