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 🙏

© 2025 – Pkg Stats / Ryan Hefner

next-config

v0.1.0

Published

Universal runtime configuration in Next.js project using [node-config](https://github.com/lorenwest/node-config)

Readme

Next.js + Config

Universal runtime configuration in Next.js project using node-config

Installation

npm install --save config next-config

or

yarn add config next-config

Usage

Create a next.config.js in your project

// next.config.js
const withConfig = require("next-config");
module.exports = withConfig();

Create a custom document pages/_document.js

import Document, { Head, Main, NextScript } from "next/document";
import htmlescape from "next/dist/server/htmlescape";
import config from "config";

const __NEXT_CONFIG__ = { ...config };
// exclude server config
delete __NEXT_CONFIG__.server;

export default class extends Document {
  render() {
    return (
      <html>
        <Head />
        <body>
          <Main />
          <script
            id="__NEXT_CONFIG__"
            type="application/json"
            nonce={this.props.nonce}
            crossOrigin={this.props.crossOrigin || process.crossOrigin}
            dangerouslySetInnerHTML={{
              __html: htmlescape(__NEXT_CONFIG__)
            }}
          />
          <NextScript />
        </body>
      </html>
    );
  }
}

Create a config file config/default.json

{
  "universalConfigA": "UNIVERSAL_CONFIG_A",
  "universalConfigB": "UNIVERSAL_CONFIG_B",
  "server": {
    "secretA": "SECRET_A",
    "secretB": "SECRET_B"
  }
}

Create a page file pages/index.js

import config from "config";

const IndexPage = () => (
  <div>
    Hello World!<br />
    ${config.get("universalConfigA")}
    <br />
    ${config.get("universalConfigB")}
    <br />
  </div>
);

IndexPage.getInitialProps = () => {
  console.log(config.get("server.secretA"));
  console.log(config.get("server.secretB"));
  return {};
};

export default IndexPage;

Configuring Next.js

Optionally you can add your custom Next.js configuration as parameter

// next.config.js
const withConfig = require("next-config");
module.exports = withConfig({
  webpack(config, options) {
    return config;
  }
});