open-index/open-npm huggingface dataset:
npm package: @jveguo16/buffer-is-img
Description: Determine if the file is in image format
Latest version: 0.0.3

# buffer-is-img

[![NPM version](https://img.shields.io/npm/v/@jveguo16/buffer-is-img.svg?style=flat)](https://npmjs.org/package/@jveguo16/buffer-is-img)
[![NPM downloads](http://img.shields.io/npm/dm/@jveguo16/buffer-is-img.svg?style=flat)](https://npmjs.org/package/@jveguo16/buffer-is-img)

根据 `Buffer` 判断当前是否为图片格式 并 返回图片的类型

不是图片类型返回 `""` 空字符串

```javascript
const { bufferIsImg } = require("@jveguo16/buffer-is-img");

const type = bufferIsImg(file);
```

## LICENSE

MIT
npm package: @jveguo16/is-gitignore
Description: Determine whether the file is ignored
Latest version: 0.0.1

# @jveguo16/is-gitnore

[![NPM version](https://img.shields.io/npm/v/@jveguo16/is-gitignore.svg?style=flat)](https://npmjs.org/package/@jveguo16/is-gitignore)
[![NPM downloads](http://img.shields.io/npm/dm/@jveguo16/is-gitignore.svg?style=flat)](https://npmjs.org/package/@jveguo16/is-gitignore)

判断文件是不是 `.gitignore` 文件中忽略的文件

## Install

```bash
npm install @jveguo16/is-gitignore
# or
yarn add @jveguo16/is-gitignore
```

## Sample

```js
// .gitignore
// [
//   '.DS_Store',        '/node_modules',
//   'npm-debug.log*',   'yarn-debug.log*',
//   'yarn-error.log*',  'test/unit/coverage',
//   'test/e2e/reports', 'selenium-debug.log',
//   '.idea/',           '.vscode/',
//   '.cache',           'coverage',
//   '.eslintcache',     'package-lock.json',
//   'stat/',            'temp/',
//   'dist/'
// ]

const gitIgnore = require("@jveguo16/is-gitignore");

const _ignore = gitIgnore.ignore({ folderPath: 'D:/test' });

// file or folder not exist
const res = _ignore.isIgnore("dist/index1.js"); // false
const res = _ignore.isIgnore("dist1"); // false

// file or folder is exist
const res = _ignore.isIgnore("dist/index.js"); // true
const res = _ignore.isIgnore("dist/"); // true
const res = _ignore.isIgnore("/dist"); // true
```

## LICENSE

MIT
npm package: @jveko/zsign-wasm
Description: WASM bindings for zsign iOS code signing
Latest version: 0.1.1

# @jveko/zsign-wasm

WebAssembly bindings for [zsign-rs](https://github.com/jveko/zsign-rs) — iOS code signing in the browser.

## Features

- **Mach-O Signing** — Sign single-arch and FAT/Universal binaries
- **CodeResources** — Build `_CodeSignature/CodeResources` with file hashes
- **Streaming Hashes** — Hash large files in chunks to avoid memory pressure
- **Certificate Loading** — Parse PKCS#12 (`.p12`) files
- **Provisioning Profiles** — Extract entitlements
- **Pure Rust** — No native dependencies, runs in any WASM environment

## Usage

```javascript
import init, { WasmSigner } from '@jveko/zsign-wasm';

await init();

// Load credentials
const signer = new WasmSigner(p12Bytes, "password", profileBytes);
signer.set_main_executable("App");

// Hash resource files for CodeResources
signer.hash_file("Base.lproj/Main.storyboardc", storyboardData);
signer.hash_file("Assets.car", assetData);

// Build CodeResources and sign the main executable
const codeResources = signer.build_code_resources();
const signed = signer.sign_macho_fat(
  machoData,
  "com.example.app",
  infoPlistData,
  codeResources
);
```

### Streaming large files

```javascript
// For files too large to fit in memory at once
for (const chunk of fileChunks) {
  const isFinal = chunk === fileChunks.at(-1);
  signer.hash_file_chunk("large-asset.car", chunk, isFinal);
}
```

### Parse Mach-O metadata

```javascript
const info = WasmSigner.parse_macho(binaryData);
console.log(info.is_fat, info.slices_count);
```

### Parse Info.plist

```javascript
const plist = WasmSigner.parse_info_plist(plistData);
console.log(plist.bundle_id, plist.executable);
```

## Building from source

```bash
# Requires wasm-pack: https://rustwasm.github.io/wasm-pack/
wasm-pack build crates/zsign-wasm --target web --release --scope jveko
```

## License

MIT
npm package: @jvenusaur/build-ui-18
Description: Code your own site builders with React
Author: LuisMPS
Latest version: 0.1.0-alpha.24

# Build-UI for React JS

Build-UI is a simple library thought for React developers packed with features that allow them to effortlessly create website builders. It comes with drag and drop functionality, undo-redo logic, site serialization and deserialization along with some other interesting tools out of the box. Because of the way it is built, it also supports other features such as SSR and component dynamic loading without you having to worry about their implementations.

Please be aware that Build-UI is currently an early-stage project in development phase. 

# Overview 🔎

With Build-UI, you can create anything from a very simple to a fully-featured website builder. Build-UI lets you create your website builder on top of your own or third-party React Components. With Build-UI, you only need a lightweight extra layer of code to handle website-building logic, which is made as simple and as transparent as possible.

# Installation 💻

You can install via npm with the command:

```
npm install --save build-ui
```

# Demo 🕹️

A cool demo is now live at https://luismps.github.io/build-ui/demo/. You can also play and experiment with the demo in your local environment.

```shell
> git clone https://github.com/LuisMPS/build-ui/
> cd build-ui/examples/demo
> npm install
> npm run dev
```

# Documentation 📖

Visit our documentation at [https://luismps.github.io/build-ui/](https://luismps.github.io/build-ui/) to learn more about Build UI 😃.

# Tutorial ✏️

Go check out our tutorial at: https://luismps.github.io/build-ui/docs/tutorials/how-to-read
npm package: @jvenusaur/react-router-auth-google
Description: Google OAuth2 strategy for React Router Auth
Author: JVenusaur
Latest version: 1.0.3

# Remix Auth - Strategy Template

> A template for creating a new Remix Auth strategy.

If you want to create a new strategy for Remix Auth, you could use this as a template for your repository.

The repo installs the latest version of Remix Auth and do the setup for you to have tests, linting and typechecking.

## How to use it

1. In the `package.json` change `name` to your strategy name, also add a description and ideally an author, repository and homepage keys.
2. In `src/index.ts` change the `MyStrategy` for the strategy name you want to use.
3. Implement the strategy flow inside the `authenticate` method. Use `this.success` and `this.failure` to correctly send finish the flow.
4. In `tests/index.test.ts` change the tests to use your strategy and test it. Inside the tests you have access to `jest-fetch-mock` to mock any fetch you may need to do.
5. Once you are ready, set the secrets on Github
   - `NPM_TOKEN`: The token for the npm registry
   - `GIT_USER_NAME`: The git username you want the bump workflow to use in the commit.
   - `GIT_USER_EMAIL`: The email you want the bump workflow to use in the commit.

## Scripts

- `build`: Build the project for production using the TypeScript compiler (strips the types).
- `typecheck`: Check the project for type errors, this also happens in build but it's useful to do in development.
- `lint`: Runs ESLint against the source codebase to ensure it pass the linting rules.
- `test`: Runs all the test using Jest.

## Documentations

To facilitate creating a documentation for your strategy, you can use the following Markdown

```markdown
# Strategy Name

<!-- Description -->

## Supported runtimes

| Runtime    | Has Support |
| ---------- | ----------- |
| Node.js    | ✅          |
| Cloudflare | ✅          |

<!-- If it doesn't support one runtime, explain here why -->

## How to use

<!-- Explain how to use the strategy, here you should tell what options it expects from the developer when instantiating the strategy -->
```
npm package: @jverneaut/gutenberg-webpack-plugin
Description: A lightweight, developer-friendly alternative to @wordpress/scripts that simplifies the setup and build process for custom Gutenberg blocks.
Author: Julien Verneaut
Latest version: 2.0.0

# GutenbergWebpackPlugin

A lightweight webpack plugin that simplifies the setup and build process for custom Gutenberg blocks. It’s designed to integrate easily into any existing Webpack configuration with minimal boilerplate.

It uses a lot of parts from [@worpress/scripts](https://developer.wordpress.org/block-editor/reference-guides/packages/packages-scripts/).

It also integrates nicely with my other package: [HTML To Gutenberg](https://github.com/jverneaut/html-to-gutenberg).

## Installation

```sh
# Install GutenbergWebpackPlugin
npm install --save-dev @jverneaut/gutenberg-webpack-plugin

# Install Webpack (if not already set up)
npm install --save-dev webpack webpack-cli
```

## Usage

```js
// webpack.config.js
import GutenbergWebpackPlugin from "@jverneaut/gutenberg-webpack-plugin";

export default {
  entry: "./index.js", // your main app entry for non-Gutenberg stuff

  plugins: [
    // "./blocks" is your blocks folder
    new GutenbergWebpackPlugin("./blocks", {
      outputPathPrefix: "blocks", // optional, default is "blocks"
    }),
  ],
};
```

If you have issues making it work with an existing webpack config that is already setup to build CSS and SASS files, you can use the `disableCssLoaders` and `disableSassLoaders` options.

```js
new GutenbergWebpackPlugin("./blocks", {
  disableCssLoaders: true,
  disableScssLoaders: true,
});
```

This will prevent conflicts between the two and should properly handle styles as long as your webpack config is standard enough.

## Block Structure

Given an input folder that looks like this:

```
blocks/
└── example-block/
    ├── block.json
    ├── edit.js
    ├── index.js
    └── render.php
```

In your block.json, reference files like so:

```json
{
  "name": "custom/example-block",
  "editorScript": "file:./index.js",
  "render": "file:./render.php"
}
```

The plugin will:

- Add index.js as a Webpack entry named `blocks/custom/example-block/index`
- Copy `block.json`, `render.php`, and any other referenced files into the final build output directory
- Create the `*.asset.php` files with `@wordpress/dependency-extraction-webpack-plugin`

## Output

Output files will be written to:

```
dist/
└── blocks/
    └── custom/
        └── example-block/
            ├── block.json
            ├── index.asset.php
            ├── index.js
            ├── render.php
```
npm package: @jverre/oscar
Description: Oscar MCP server with share tool
Author: jverre
Latest version: 0.1.4

# Oscar MCP Server

A simple Model Context Protocol (MCP) server with a single "share" tool that does nothing.

## Installation

```bash
npx -y @jverre/oscar
```

## Usage

The server runs on stdio and provides a single tool called "share" that accepts content but performs no action.

## Tool

- **share**: Takes a `content` parameter (string) and returns a message indicating it was called

## Development

```bash
npm install
npm run dev
```

## Build

```bash
npm run build
```

## License

MIT