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

@sergioengineer/next-manifest

v0.0.1

Published

Route manifest for next.js

Downloads

1

Readme

⚡ Next Manifest ⚡

About

Next manifest is a package which generates a blitzjs-like route manifest for NextJs projects. Instead of writing plain urls, you can reference nextjs' pages through the Routes object.

  • /url1/${param}/test.jsx

becomes

  • Routes.Test(param)

  • /url1/${param}/test.jsx?foo=bar

becomes

  • Routes.Test(param, [{foo: "bar"}])

Next manifest also calculates route collisions.

Imagine the following folder tree:

  • -> [test] / test.jsx (component name Test1)
  • -> test / [test].jsx (component name Test2)

The second route takes priority over the first one whenever the first parameter is named "test". That's because, in nextjs, exact name's have higher priority than dynamic params. The left most priority discrepancy is the most important one.

So, if you call Test("test") You'll get an exception telling you that you are trying to redirect the user to a route which collides with one of higher priority.

Usage

yarn next-manifest

A folder can also be provided where the genereted routeManifest.js will be saved to.

yarn next-manifest --out="manifestFolder"

Next manifest can also run with --watch flag.

yarn next-manifest --out="manifestFolder" --watch

Collision detection is disabled by default when NODE_ENV is set to "production";