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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@putout/plugin-nextjs

v3.0.0

Published

🐊Putout plugin adds ability to migrate to latest version of Next.js

Downloads

41

Readme

@putout/plugin-nextjs NPM version

🐊Putout plugin adds ability to migrate to latest version of Next.js. Not Bundled.

Install

npm i putout @putout/plugin-nextjs -D

Add .putout.json with:

{
    "plugins": ["nextjs"]
}

Rules

Here is list of rules:

{
    "rules": {
        "nextjs/create-app-directory": "on",
        "nextjs/remove-a-from-link": "on",
        "nextjs/convert-page-to-head": "on",
        "nextjs/move-404-to-not-found": "on",
        "nextjs/update-tsconfig": "off",
        "nextjs/update-tsconfig-file": "on"
    }
}

remove-a-from-link

Next.js 12: <a> has to be nested otherwise it's excluded, Next.js 13: <Link> always renders <a> under the hood.

Check out in 🐊Putout Editor.

❌ Example of incorrect code

import Link from 'next/link';

export default function Nav() {
    <Link href="/about">
        <a>
            About
        </a>
    </Link>;
}

✅ Example of correct code

import Link from 'next/link';

export default function Nav() {
    <Link href="/about">
        About
    </Link>;
}

convert-page-to-head

In the pages directory, the next/head React component is used to manage <head> HTML elements such as title and meta . In the app directory, next/head is replaced with a new head.js special file.

Check out in 🐊Putout Editor.

❌ Example of incorrect code

import Head from 'next/head';

export default function Page() {
    return (
        <>
            <Head>
                <title>
                    My page title
                </title>
            </Head>
        </>
    );
}

✅ Example of correct code

export default function Head() {
    return (
        <>
            <title>
                My page title
            </title>
        </>
    );
}

create-app-directory

For new applications, we recommend using the App Router. This router allows you to use React's latest features and is an evolution of the Pages Router based on community feedback.

(c) nextjs.org

Check out in 🐊Putout Editor.

+app/

move-404-to-not-found

pages/404.js has been replaced with the not-found.js file.

(c) nextjs.org

Check out in 🐊Putout Editor.

-app/pages/404.js
+app/not-found.js

update-tsconfig

If you're using TypeScript, you need to update your tsconfig.json file with the following changes to make it compatible with Next.js.

(c) nextjs.org

Add ./dist/types/**/*.ts and ./next-env.d.ts to the include array.

Check out in 🐊Putout Editor.

tsconfig.json:

{
-    "includes": []
+    "includes": ["./dist/types/**/*.ts", "./next-env.d.ts"]
}

The rule disabled by default. To enable use update-tsconfig-file or update .putout.json with:

{
    "match": {
        "tsconfig.json": {
            "nexts/update-ts-config": "on"
        }
    },
    "plugins": ["nextjs"]
}

update-tsconfig-file

Enables update-tsconfig for tsconfig.json without using match.

Run redlint to generate .filesystem.json and then lint. Check out in 🐊Putout Editor.

License

MIT