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

@applydigital_latam/eslint-plugin-nextpublic

v2.0.1

Published

ESLint plugin to check if NEXT_PUBLIC variables are justified in .nextpublicrc file

Readme

eslint-plugin-nextpublic

ESLint plugin to verify that NEXT_PUBLIC variables are justified in a .nextpublicrc file. The justification text should have a minimum length of 20 characters.

Installation

First, you need to install ESLint:

npm i eslint --save-dev

Then, install @applydigital_latam/eslint-plugin-nextpublic:

npm i -D @applydigital_latam/eslint-plugin-nextpublic

Usage

Add nextpublic to the plugins section in your .eslintrc file. You can omit the eslint-plugin- prefix:

{
  "plugins": ["@applydigital_latam/eslint-plugin-nextpublic"]
}

Then configure the rules you want to use:

{
  "rules": {
    "@applydigital_latam/eslint-plugin-nextpublic/require-justification": "error"
  }
}

Or use the recommended configuration:

{
  "extends": ["plugin:@applydigital_latam/eslint-plugin-nextpublic/recommended"]
}

Important: You must use "--no-cache" flag when running ESLint to ensure that the plugin is loading the env vars and the justification file correctly on each execution.

Rules

require-justification

This rule verifies that all environment variables starting with NEXT_PUBLIC_ have a justification in the .nextpublicrc file.

.nextpublicrc File

You must create a .nextpublicrc file in the root of your project with justifications for each NEXT_PUBLIC variable:

NEXT_PUBLIC_API_URL="This URL is public because it is necessary for client API calls"
NEXT_PUBLIC_FEATURE_FLAG="This flag is public because it controls features visible on the client"

Alternatively, you can use JSON format:

{
  "NEXT_PUBLIC_API_URL": "This URL is public because it is necessary for client API calls",
  "NEXT_PUBLIC_FEATURE_FLAG": "This flag is public because it controls features visible on the client"
}

Example

If you have a NEXT_PUBLIC_API_KEY variable in your code but haven't justified it in the .nextpublicrc file, ESLint will show an error:

error: NEXT_PUBLIC variable 'NEXT_PUBLIC_API_KEY' requires justification in .nextpublicrc file

To resolve this error, you must add a justification in the .nextpublicrc file:

NEXT_PUBLIC_API_KEY="It's public because we have no issues sharing the URL, it's safe to have it public"