open-index/open-npm huggingface dataset:
npm package: @next-sekai/sonolus-next-sekai-engine
Description: A new Project Sekai inspired engine for Sonolus
Author: qwewqa
Latest version: 1.9.4

# Next SEKAI Sonolus Engine

A new Project Sekai inspired engine for [Sonolus](https://sonolus.com).

## Installation

```
npm install @next-sekai/sonolus-next-sekai-engine
```

## Documentation

### `version`

Package version.

### `databaseEngineItem`

Partial database engine item compatible with [sonolus-express](https://github.com/Sonolus/sonolus-express).

### `susToUSC(sus)`

Converts sus chart to USC (Universal Sekai Chart).

- `sus`: sus chart.

### `uscToLevelData(usc, offset?)`

Converts USC (Universal Sekai Chart) to Level Data.

- `usc`: usc chart.
- `offset`: offset (default: `0`).

### Assets

The following assets are exposed as package entry points:

- `EngineConfiguration`
- `EnginePlayData`
- `EngineWatchData`
- `EnginePreviewData`
- `EngineTutorialData`
- `EngineRom`
- `EngineThumbnail`

In Node.js, you can obtain path to assets `import.meta.resolve('sonolus-pjsekai-engine/EngineConfiguration')`.
npm package: @next-template/blog-components
Description: Reusable React component
Author: Jimmy Moon
Latest version: 1.0.0

# components for blog

> My usable React component

# Install

```sh
yarn add @next-template/components

or

npm install --save-dev @next-template/components
```

# Usage

```
import { Layout, Hero, Container, Post } from '@next-template/components'
```

# License

MIT @ [Jimmy Moon](https://jimmy.im)
npm package: @next-theme/eslint-config
Description: ESLint config for projects under theme NexT organization.
Author: NexT
Latest version: 0.0.5

# @next-theme/eslint-config

[![npm-image]][npm-url]
[![lic-image]](LICENSE)

[ESLint](https://www.github.com/eslint/eslint) config for projects under [theme NexT](https://github.com/next-theme) organization.

## Installation

![size-image]
[![dm-image]][npm-url]
[![dt-image]][npm-url]

There are two ways to install this configuration preset with `ESLint`: globally or locally (recommended).

### Global Installation

```bash
npm install -g eslint
npm install -g @next-theme/eslint-config
```

### Local Installation

```bash
npm install --save-dev eslint
npm install --save-dev @next-theme/eslint-config
```

## Usage

If the file `.eslintrc.json` does not exists in the required repository, you will need to create it:

```json
{
  "extends": "@next-theme",
  "root": true
}
```

Next, you can choose to install the ESLint plugin for your editor. For example, use [Visual Studio Code](https://github.com/Microsoft/vscode/) with [ESLint](https://marketplace.visualstudio.com/items?itemName=dbaeumer.vscode-eslint) plugin installed.

[npm-image]: https://img.shields.io/npm/v/@next-theme/eslint-config.svg?style=flat-square
[lic-image]: https://img.shields.io/npm/l/@next-theme/eslint-config?style=flat-square

[size-image]: https://img.shields.io/github/languages/code-size/next-theme/eslint-config?style=flat-square
[dm-image]: https://img.shields.io/npm/dm/@next-theme/eslint-config?style=flat-square
[dt-image]: https://img.shields.io/npm/dt/@next-theme/eslint-config?style=flat-square

[npm-url]: https://www.npmjs.com/package/@next-theme/eslint-config
npm package: @next-theme/plugins
Description: Plugins for Hexo theme NexT.
Author: Mimi
Latest version: 8.27.0

# NexT Plugins

[![Npm Version](https://img.shields.io/npm/v/@next-theme/plugins?style=for-the-badge)](https://npmjs.org/package/@next-theme/plugins)
[![Npm Downloads Month](https://img.shields.io/npm/dm/@next-theme/plugins?style=for-the-badge)](https://npmjs.org/package/@next-theme/plugins)
[![Npm Downloads Total](https://img.shields.io/npm/dt/@next-theme/plugins?style=for-the-badge)](https://npmjs.org/package/@next-theme/plugins)
[![License](https://img.shields.io/npm/l/@next-theme/plugins?style=for-the-badge)](https://npmjs.org/package/@next-theme/plugins)

This plugin provides the code for all optional third-party frontend libraries used by NexT. By default, NexT loads these libraries via CDN. However, in some cases, these CDNs may be unavailable (e.g., when the site is deployed in an intranet environment without internet access). In such situations, by installing this plugin and configuring the theme accordingly, Hexo can bundle the library code into the generated blog files, enabling offline deployment.

## Installation

```bash
npm install @next-theme/plugins
```

## Debug

First execute the following command in Hexo site root directory to ensure that the plugin is installed correctly.

```bash
npm install
```

If the warning persists, then the solution depends on how you installed NexT.

1. Installed NexT through npm:
    Make sure the version numbers of `@next-theme/plugins` and `hexo-theme-next` are the same.

1. Installed NexT through git:
    1. If you are using the latest master branch: **Ignore this warning**.
    1. If you are using the latest release version:
        Make sure the version numbers of `@next-theme/plugins` and `hexo-theme-next` are the same.

Feel free to raise new issues you find in this plugin.
npm package: @next-translate/sdk
Description: Official SDK to connect with next-translate platform
Author: Lenodev team
Latest version: 0.1.1

### Next Translate

Official SDK to integrate your translation system into your Next.js application.


### 🚀 Feature

    Auto fetch the translate from next-translate platform

    Support getStaticProps, getServerSideProps

    Organize translations by locale and namespace

### 📥 Installation

```bash
npm install @next-translate/sdk
# or
yarn add @next-translate/sdk
```

### 🔧 Setting

1.Get token

    Login via `https://next-translate.com` and navigate to Developer page on next-translate platform

    Generate API token

### How to use in Nextjs project

1. Support getStaticProps

Example: pages/index.tsx

```bash
import { loadServerTranslations } from '@next-translate/sdk';

export async function getStaticProps({ locale }: { locale: string }) {
  return loadServerTranslations('YOUR_API_TOKEN', locale, ['common', 'homepage']);
}

export default function Home({ translations }: any) {
  return (
    <div>
      <h1>{translations.common.hello}</h1>
      <p>{translations.homepage.welcome}</p>
    </div>
  );
}
```

2. Support newest version of Nextjs

   In next.config.js or middleware.ts in Nextjs

```bash
import { createTranslateClient } from '@next-translate/sdk';

const client = createTranslateClient({ token: process.env.NEXT_TRANSLATE_TOKEN });

const translations = await client.getTranslations({ locale: 'en', namespace: 'common' });

console.log(translations.title); // Hello
```

And we can use it like this.

```bash
const translations = await i18nClient.getTranslations({
  locale: 'vi',
  namespace: 'common',
});

```

### 📁 Structural translation (On the platform)

Each locale may have many namespace

Example namespace `common`:

```bash
{
  "hello": "Xin chào",
  "logout": "Đăng xuất"
}
```

👨‍💻 License

MIT © 2025 – Built with ❤️ by Lenodev team
npm package: @next-vue/compiler-sfc
Description: @next-vue/compiler-sfc
Author: Evan You
Latest version: 3.0.0-alpha.10

# @vue/compiler-sfc

> Lower level utilities for compiling Vue single file components

This package contains lower level utilities that you can use if you are writing a plugin / transform for a bundler or module system that compiles Vue single file components into JavaScript. It is used in [vue-loader](https://github.com/vuejs/vue-loader).

The API surface is intentionally minimal - the goal is to reuse as much as possible while being as flexible as possible.

## API

TODO
npm package: @next-vue/reactivity
Description: @next-vue/reactivity
Author: Evan You
Latest version: 3.0.0-alpha.10

# @vue/reactivity

## Usage Note

This package is inlined into Global & Browser ESM builds of user-facing renderers (e.g. `@vue/runtime-dom`), but also published as a package that can be used standalone. The standalone build should not be used alongside a pre-bundled build of a user-facing renderer, as they will have different internal storage for reactivity connections. A user-facing renderer should re-export all APIs from this package.

For full exposed APIs, see `src/index.ts`. You can also run `yarn build reactivity --types` from repo root, which will generate an API report at `temp/reactivity.api.md`.

## Credits

The implementation of this module is inspired by the following prior art in the JavaScript ecosystem:

- [Meteor Tracker](https://docs.meteor.com/api/tracker.html)
- [nx-js/observer-util](https://github.com/nx-js/observer-util)
- [salesforce/observable-membrane](https://github.com/salesforce/observable-membrane)

## Caveats

- Built-in objects are not observed except for `Map`, `WeakMap`, `Set` and `WeakSet`.
npm package: @next-vue/runtime-core
Description: @next-vue/runtime-core
Author: Evan You
Latest version: 3.0.0-alpha.10

# @vue/runtime-core

> This package is published only for typing and building custom renderers. It is NOT meant to be used in applications.

For full exposed APIs, see `src/index.ts`. You can also run `yarn build runtime-core --types` from repo root, which will generate an API report at `temp/runtime-core.api.md`.

## Building a Custom Renderer

``` ts
import { createRenderer } from '@vue/runtime-core'

const { render, createApp } = createRenderer({
  patchProp,
  insert,
  remove,
  createElement,
  // ...
})

// `render` is the low-level API
// `createApp` returns an app instance with configurable context shared
// by the entire app tree.
export { render, createApp }

export * from '@vue/runtime-core'
```

See `@vue/runtime-dom` for how a DOM-targeting renderer is implemented.
npm package: @next-vue/runtime-dom
Description: @next-vue/runtime-dom
Author: Evan You
Latest version: 3.0.0-alpha.10

# @vue/runtime-dom

``` js
import { h, createApp } from '@vue/runtime-dom'

const RootComponent = {
  render() {
    return h('div', 'hello world')
  }
}

createApp().mount(RootComponent, '#app')
```
npm package: @next-vue/runtime-test
Description: @next-vue/runtime-test
Author: Evan You
Latest version: 3.0.0-alpha.8

# @vue/runtime-test

``` js
import { h, render, nodeOps, dumpOps } from '@vue/runtime-test'

const App = {
  data () {
    return {
      msg: 'Hello World!'
    }
  }
  render () {
    return h('div', this.msg)
  }
}

// root is of type `TestElement` as defined in src/nodeOps.ts
const root = nodeOps.createElement('div')
render(h(App), root)

const ops = dumpOps()
console.log(ops)
```
npm package: @next-with-offline/next-plugin
Description: Next.js plugin for generating a service worker.
Author: Cansin Yildiz
Latest version: 4.0.1

# @next-with-offline/next-plugin
[![size](https://img.shields.io/bundlephobia/minzip/@next-with-offline/next-plugin)](https://bundlephobia.com/result?p=@next-with-offline/next-plugin)
[![dependencies](https://img.shields.io/librariesio/release/npm/@next-with-offline/next-plugin)](https://libraries.io/npm/@next-with-offline%2Fnext-plugin)
[![build](https://img.shields.io/travis/com/cansin/next-with-offline)](https://travis-ci.com/github/cansin/next-with-offline)
[![downloads](https://img.shields.io/npm/dm/@next-with-offline/next-plugin)](https://www.npmjs.com/package/@next-with-offline/next-plugin)
[![license](https://img.shields.io/github/license/cansin/next-with-offline)](https://github.com/cansin/next-with-offline/blob/master/LICENSE)

Next.js plugin for generating a Workbox. Intended to be used alongside
[@next-with-offline/react-hook](https://www.npmjs.com/package/@next-with-offline/react-hook) and
[@next-with-offline/service-worker](https://www.npmjs.com/package/@next-with-offline/service-worker).
Read [the top level documentation](https://github.com/cansin/next-with-offline#readme) for more information about usage.

## Install

```bash
yarn add @next-with-offline/next-plugin
```

## Basic Usage

Update or create `next.config.js` with

```js
const withOffline = require("@next-with-offline/next-plugin");

module.exports = withOffline({
  offline: {
    path: "/offline",
  },
  workbox: {
    dest: "public",
    swDest: "sw.js",
    swSrc: "worker.js",
    // .
    // ..
    // ... other workbox-webpack-plugin.InjectManifest options
  },
  // .
  // ..
  // ... other Next.js config
});
```

Add `public/sw.js` and `public/sw.js.map` to your `.gitignore`

```git
public/sw.js
public/sw.js.map
```
npm package: @next-with-offline/react-hook
Description: React hook for registering/using a Workbox.
Author: Cansin Yildiz
Latest version: 4.0.3

# @next-with-offline/react-hook
[![size](https://img.shields.io/bundlephobia/minzip/@next-with-offline/react-hook)](https://bundlephobia.com/result?p=@next-with-offline/react-hook)
[![dependencies](https://img.shields.io/librariesio/release/npm/@next-with-offline/react-hook)](https://libraries.io/npm/@next-with-offline%2Freact-hook)
[![build](https://img.shields.io/travis/com/cansin/next-with-offline)](https://travis-ci.com/github/cansin/next-with-offline)
[![downloads](https://img.shields.io/npm/dm/@next-with-offline/react-hook)](https://www.npmjs.com/package/@next-with-offline/react-hook)
[![license](https://img.shields.io/github/license/cansin/next-with-offline)](https://github.com/cansin/next-with-offline/blob/master/LICENSE)

React hook for registering/using a Workbox. Intended to be used alongside
[@next-with-offline/next-plugin](https://www.npmjs.com/package/@next-with-offline/next-plugin) and
[@next-with-offline/service-worker](https://www.npmjs.com/package/@next-with-offline/service-worker).
Read [the top level documentation](https://github.com/cansin/next-with-offline#readme) for more information about usage.

## Install

```bash
yarn add @next-with-offline/react-hook workbox-window
```

## Basic Usage

```js
import React from "react";

import { useOffline } from "@next-with-offline/react-hook";

export default function Component() {
  useOffline({
    offlinePath: "/offline",
    registerOptions: {},
    scriptURL: "sw.js",
    showReloadPrompt: false,
  });

  return <p>Hello World!</p>;
}
```
npm package: @next-with-offline/service-worker
Description: Code utilities for configuring a service worker.
Author: Cansin Yildiz
Latest version: 4.0.0

# @next-with-offline/service-worker
[![size](https://img.shields.io/bundlephobia/minzip/@next-with-offline/service-worker)](https://bundlephobia.com/result?p=@next-with-offline/service-worker) 
[![dependencies](https://img.shields.io/librariesio/release/npm/@next-with-offline/service-worker)](https://libraries.io/npm/@next-with-offline%2Fservice-worker) 
[![build](https://img.shields.io/travis/com/cansin/next-with-offline)](https://travis-ci.com/github/cansin/next-with-offline) 
[![downloads](https://img.shields.io/npm/dm/@next-with-offline/service-worker)](https://www.npmjs.com/package/@next-with-offline/service-worker) 
[![license](https://img.shields.io/github/license/cansin/next-with-offline)](https://github.com/cansin/next-with-offline/blob/master/LICENSE)

Code utilities for configuring a service worker. Intended to be used alongside 
[@next-with-offline/next-plugin](https://www.npmjs.com/package/@next-with-offline/next-plugin) and 
[@next-with-offline/react-hook](https://www.npmjs.com/package/@next-with-offline/react-hook).
Read [the top level documentation](https://github.com/cansin/next-with-offline#readme) for more information about usage. 

## Install

```bash
yarn add @next-with-offline/service-worker
```

## Basic Usage

```js
import hasOffline from "@next-with-offline/service-worker";

hasOffline({
  cleanupOutdatedCaches: true,
  offlineGoogleAnalytics: false,
  offlinePath: "/offline",
  showReloadPrompt: false,
});
```
npm package: @next-zero/babel-preset-jsx-flow
Description: config babel for NextJs
Author: vHades
Latest version: 0.3.2

# @next-zero/babel-preset-jsx-flow

Babel preset config for next-zero.

## Installation

```
yarn add --dev eslint @next-zero/babel-preset-jsx-flow
```

*Note: We're using `yarn` to install deps. Feel free to change commands to use `npm` 3+ and `npx` if you like*

## Usage

Add to your babel config (`.babelrc`):

```json
{
    "presets": "@next-zero/jsx-flow"
}
```
npm package: @next-zero/eslint-config
Description: config eslint for NextJS
Author: vHades
Latest version: 0.3.4

# @next-zero/eslint-config

Eslint config utilizing Airbnb config, Flow, Prettier and Jest support.

Plugins and configs used:
* [eslint-config-airbnb](https://yarnpkg.com/en/package/eslint-config-airbnb)
* [eslint-config-prettier](https://yarnpkg.com/en/package/eslint-config-prettier)
* [eslint-plugin-flowtype](https://yarnpkg.com/en/package/eslint-plugin-flowtype)
* [eslint-plugin-jest](https://yarnpkg.com/en/package/eslint-plugin-jest)

Additionally, it sets these environments:
```json
{
  "env": {
    "browser": true,
    "es6": true,
    "node": true
  }
}
```

## Installation

```
yarn add --dev eslint @next-zero/eslint-config
```

*Note: We're using `yarn` to install deps. Feel free to change commands to use `npm` 3+ and `npx` if you like*

## Usage

Add to your eslint config (`.eslintrc`, or `eslintConfig` field in `package.json`):

```json
{
    "extends": "@next-zero"
}
```

### Example of extending the configuration

```json
{
    "extends": "@next-zero",
    "rules": {
        "global-require": 0,
        "prefer-destructuring": 0
    }
}
```
npm package: @next.id/sdk
Description: Next.ID JavaScript SDK
Author: NextDotID
Latest version: 0.0.0-20230105165153-0fcfb9b

# @nextdotid/sdk

[![Publish][publish-badge]][publish-workflow]

[publish-badge]: https://github.com/nextdotid/sdk/actions/workflows/publish.yml/badge.svg
[publish-workflow]: https://github.com/nextdotid/sdk/actions/workflows/publish.yml

[Next.ID](https://next.id) JavaScript SDK

## Features

- [Proof Client](src/proof)
- [Key-Value Client](src/kv)

## Installation

- [Unstable channel](docs/UNSTABLE.md)

## LICENSE

[MIT](LICENSE)
npm package: @next/gh-issues
Description: GitHub issues we use at Next.
Author: Wayne Ashley Berry
Latest version: 2.2.1

# gh-issues

> GitHub issues for new repos at [Next](https://github.com/we-are-next)

[![npm](http://img.shields.io/npm/v/@next/gh-issues.svg?style=flat)](https://www.npmjs.com/package/@next/gh-issues)
[![js-standard-style](https://img.shields.io/badge/code%20style-standard-brightgreen.svg?style=flat)](https://github.com/feross/standard)
[![Build Status](https://travis-ci.org/we-are-next/gh-issues.svg?branch=master)](https://travis-ci.org/we-are-next/gh-issues)
[![Dependency Status](https://david-dm.org/we-are-next/gh-issues.svg)](https://david-dm.org/we-are-next/gh-issues)
[![devDependency Status](https://david-dm.org/we-are-next/gh-issues/dev-status.svg)](https://david-dm.org/we-are-next/gh-issues#info=devDependencies)

#### Usage

```js
var getIssues = require('@next/gh-issues')

getIssues(function (issues) {
  //
})
```

#### Deployment

To get new or updated issues to be used with our GitHub webhooks you need to do
the following:

1. Publish a new release of this package on NPM
2. Update the [package.json](https://github.com/we-are-next/gh-webhooks/blob/master/package.json) over in [we-are-next/gh-webhooks](https://github.com/we-are-next/gh-webhooks)
3. If the tests pass, the updated webhooks will be automatically deployed.

If you're making a lot of updates and find publishing slow and tedious,
check out [cut-release](https://www.npmjs.com/package/cut-release).
npm package: @next/gh-labels
Description: GitHub labels we use at Next.
Author: Wayne Ashley Berry
Latest version: 1.0.1

# gh-labels

> GitHub labels for [Next](https://github.com/we-are-next)

[![npm](http://img.shields.io/npm/v/@next/gh-labels.svg?style=flat)](https://www.npmjs.com/package/@next/gh-labels)
[![js-standard-style](https://img.shields.io/badge/code%20style-standard-brightgreen.svg?style=flat)](https://github.com/feross/standard)
[![Build Status](https://travis-ci.org/we-are-next/gh-labels.svg?branch=master)](https://travis-ci.org/we-are-next/gh-labels)
[![Dependency Status](https://david-dm.org/we-are-next/gh-labels.svg)](https://david-dm.org/we-are-next/gh-labels)
[![devDependency Status](https://david-dm.org/we-are-next/gh-labels/dev-status.svg)](https://david-dm.org/we-are-next/gh-labels#info=devDependencies)

#### Deployment

To get new or updated labels to be used with our GitHub webhooks you need to do
the following:

1. Publish a new release of this package on NPM
2. Update the [package.json](https://github.com/we-are-next/gh-webhooks/blob/master/package.json) over in [we-are-next/gh-webhooks](https://github.com/we-are-next/gh-webhooks)
3. If the tests pass, the updated webhooks will be automatically deployed.

If you're making a lot of updates and find publishing slow and tedious,
check out [cut-release](https://www.npmjs.com/package/cut-release).

#### Usage

##### CLI

To manually add labels to _an existing repo_, there are two things that
you'll need.

Firstly, install [github-labels](https://www.npmjs.com/package/github-labels):

```sh
npm install --global github-labels
```

Then, get a local copy of the
[config.json](https://github.com/we-are-next/gh-labels/blob/master/config.json)
in this repo.

```sh
git clone git@github.com:we-are-next/gh-labels.git
```

Cool! Now you can run the following command to create labels:

```sh
labels -c gh-labels/config.json user/repo
```

You may optionally remove any existing labels by using the force option:

```sh
labels -c gh-labels/config.json -f user/repo
```

##### Node

```sh
npm install --save @next/gh-labels
```

```js
var labels = require('@next/gh-labels')

labels.forEach(function (label) {
  // do something
})
```
npm package: @next/rs-win32-x64-msvc
Description: This is the **x86_64-pc-windows-msvc** binary for `@next/rs`
Latest version: 0.0.0-canary.1677543101064

# `@next/rs-win32-x64-msvc`

This is the **x86_64-pc-windows-msvc** binary for `@next/rs`