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

eslint-plugin-nextjs-no-getinitialprops

v0.3.0-rc.0

Published

[![npm version](https://img.shields.io/npm/v/eslint-plugin-nextjs-no-getinitialprops.svg)](https://www.npmjs.com/package/eslint-plugin-nextjs-no-getinitialprops)

Downloads

4

Readme

eslint-plugin-nextjs-no-getinitialprops

npm version

ESLint plugin to disallow usage of getInitialProps in Next.js applications.


❌ Why?

getInitialProps is considered legacy in Next.js and is discouraged in favor of getStaticProps, getServerSideProps, or newer data fetching methods in the App Router.

This plugin enforces that getInitialProps is not used anywhere in your codebase.


📦 Installation

npm install --save-dev eslint-plugin-nextjs-no-getinitialprops

or with yarn:

yarn add --dev eslint-plugin-nextjs-no-getinitialprops

🛠 Usage

Add the plugin and rule to your ESLint config:

{
  "plugins": ["nextjs-no-getinitialprops"],
  "rules": {
    "nextjs-no-getinitialprops/nextjs-no-getinitialprops": "error"
  }
}

✅ Rule: nextjs-no-getinitialprops

This rule disallows using or assigning getInitialProps on Page components.

❌ Incorrect Examples

// Static method in a React class component
class Page extends React.Component {
  static getInitialProps() {
    return {};
  }
}

// Direct assignment
Page.getInitialProps = () => {
  return {};
};

// Object literal assignment
const Page = {};
Page.getInitialProps = function () {
  return {};
};

✅ Correct Examples

// Preferred Next.js data fetching method
export async function getServerSideProps() {
  return { props: {} };
}

// Safe static method
class Page extends React.Component {
  static someOtherMethod() {
    return {};
  }
}

// Valid assignment
const Page = {};
Page.render = () => <div>Hello</div>;

📚 Examples of Detected Patterns

The plugin will detect and report:

| Pattern Type | Code Snippet | |--------------------------|----------------------------------------------------| | Static class method | static getInitialProps() {} | | Assignment expression | Page.getInitialProps = () => {} | | Property inside object | Page = {}; Page.getInitialProps = function () {}|

All of these will trigger a linting error with the message:

"Unexpected use of getInitialProps method or function"


🧪 Running Tests

To run the tests:

npm install
npm test

Next steps

This is a first quick version of the plugin, next steps will be :

  • Add TypeScript
  • Better tests
  • Better bundling

📄 License

MIT © 2025