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

@ginterdev/next-showcase

v0.1.0-rc.16

Published

Very simple and basic alternative for Storybook working on Next.js

Downloads

5

Readme

@ginterdev/next-showcase

Very simple and basic alternative for Storybook working on Next.js.

Next Showcase Screenshot

Warning :warning:

  1. This tool is completely Next.js-based, so it cannot be used without it (for now). It has potential for working with non-Next.js apps, though.
  2. For now I am just experimenting. I DO NOT recommend using it for anything that is not just having fun after hours.
  3. If you have questions or proposals use GitHub issues.

This package makes some assumptions:

  • you are using Next.js (>= 9)
  • you are using Typescript (>= 3.9)
  • your pages directory is process.cwd()/pages

Installation

yarn add --dev @ginterdev/next-showcase

# or

npm i -D @ginterdev/next-showcase

Usage

Step 1

Start your Next.js application in watch mode.

next dev -p 3000

Step 2 (optional)

:warning: This has to be done ONLY if you have custom App component.

Wrap you custom App component with withShowcase. This will skip all specific stuff for your project implemented inside getInitialProps as well and your custom component. You don't want to render header or footer as part of showcase page.

import { withShowcase } from '@ginterdev/next-showcase';

function App() {
  // Implementation ommitted.
  return ...;
}

export default withShowcase(App);

Step 3

Create your first stories file inside src directory (relative to process.cwd()).

import type { ShowcaseStories } from '@ginterdev/next-showcase';

// Import of `Button` is ommitted.

const stories: ShowcaseStories = {
  'My First Story': () => <Button />,
  'My Story With Dark Mode': {
    dark: true,
    Story: () => <Button />,
  },
};

// Default export is important.
export default stories;

Step 4

Finally run a watch server that will automatically update the showcase page whenever you add or modify some *.stories.tsx files.

npx @ginterdev/next-showcase

# Now go to http://localhost:3000/_next-showcase 🚀

Make sure to add pages/_next-showcase to your .gitignore.

Customizing

You can set your own pathname instead of default /_next-showcase by specifying a configuration option in .ginterdevrc.js file:

// .ginterdevrc.js

module.exports = {
  'next-showcase': {
    entryDir: 'ui-kit',
  },
};

Now your stories will be accessible under /ui-kit.
(Notice that now you have to gitignore pages/ui-kit instead of pages/_next-showcase).