npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

next-nacos

v1.0.0

Published

A command-line tool to sync configurations from Nacos configuration center to Next.js projects.

Readme

next-nacos

A command-line tool to sync configurations from Nacos configuration center to Next.js projects.

Introduction

next-nacos is a convenient command-line tool that synchronizes configurations from the Nacos configuration center to the .env file of a Next.js project, making it easy to use these configurations in both client-side and server-side components.

Global Installation

npm install -g next-nacos

Or Install as a Project Dependency

npm install next-nacos --save-dev

Usage

  1. Create a configuration file .nextnacos.js in the root directory of the project.

  2. Execute the command to sync configurations:

    # When installed globally
    next-nacos
       
    # When installed as a project dependency
    npx next-nacos
       
    # Or execute after adding the command to the scripts in package.json
    npm run sync-config

Configuration File

Create a .nextnacos.js file in the root directory of the project. Example content:

module.exports = function defineConfig() {
  return {
    // Nacos server address
    serverAddr: 'localhost:8848',
    // Configuration ID
    dataId: 'next-app-config',
    // Configuration group
    group: 'DEFAULT_GROUP',
    // Optional: Namespace
    namespace: 'your-namespace-id',
    // Optional: Username
    username: 'nacos',
    // Optional: Password
    password: 'nacos'
  };
};

Configuration File

Configuration Item Description

Valid configuration items are Nacos configuration items:

| Configuration Item | Type | Description | Required | |--------|------|------|----------| | serverAddr | string | Nacos server address, in the format host:port | Yes | | dataId | string | The configuration ID to obtain | Yes | | group | string | The group to which the configuration belongs | Yes | | namespace | string | The namespace ID to which the configuration belongs | No | | username | string | Username for accessing Nacos | No | | password | string | Password for accessing Nacos | No | | requestTimeout | number | Request timeout in milliseconds, default 6000 | No |

Using Configurations in Next.js

After configuration synchronization, a .env file will be generated in the root directory of the project with the following content format:

NEXT_PUBLIC_NACOS='{"key":"value",...}'

In a Next.js project, you can access the configuration via process.env.NEXT_PUBLIC_NACOS:

// Use in pages or components
const AppConfig = JSON.parse(process.env.NEXT_PUBLIC_NACOS || '{}');

console.log(AppConfig.apiUrl);

Integrating into Project Workflow

  1. Install dependencies

    npm install next-nacos --save-dev
  2. Create the configuration file .nextnacos.js

  3. Add scripts to package.json:

    {
      "scripts": {
        "sync-config": "next-nacos",
        "dev": "npm run sync-config && next dev",
        "build": "npm run sync-config && next build"
      }
    }
  4. Run the development environment:

    npm run dev

Running Tests

npm test

License

MIT