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

next-parade

v0.1.0

Published

Lightweight UI component stories and documentation showcase for [Next.js](https://nextjs.org/).

Downloads

4

Readme

🚩 Parade!

Lightweight UI component stories and documentation showcase for Next.js.

⚠️ Pre-alpha: This is a proof-of-concept. You will be disappointed!

Why? It's easy and fast. No additional steps in CI/CD. No need to align webpack config.

Usage

npm install next-parade
yarn add next-parade

Configure and render it on a page:

// ./pages/index.js
import parade from "next-parade";
import withStaticProps from "next-parade/props";

const context = require.context("../src/components", true, /\.js/); // ❗ relative path and regex
export default parade(context);
export const getStaticProps = withStaticProps(context, "src/components"); // path from project root

By convention React Component should be the default export from a file.

children props require annotation.

Prior art

  • Storybook - runs on top of 'create-react-app'
  • Docz - runs on Gatsby. It's where I copied lib/docgen from
  • Styleguidist - looks slim and promising. I did not have the opportunity use it nor to dive in it's code yet.

Idea behind this project is to prove that something simillar can be done on Next.js

Development

npm run dev
yarn dev

Open http://localhost:3000 with your browser to see the result.

Roadmap

  • ~~live edit props~~
  • source code preview/copy
  • parse markdown
  • order of elements (sort)
  • add "last build" to website

Advanced example

// ./pages/showcase.tsx
import { GetStaticProps } from "next";
import parade from "next-parade";
import withStaticProps from "next-parade/props";
import styles from "../styles/Home.module.css";

const context = require.context("../components", true, /\/[A-Z]\w\.tsx/);
const ComponentsParade = parade(context);

const Home = ({ ...props }) => (
  <div className={styles.container}>
    <ComponentsParade
      {...props}
      title="Styleguide"
      style={{ maxWidth: "600px" }}
    />
  </div>
);

export default Home;

export const getStaticProps: GetStaticProps = async (context) => {
  const output = withStaticProps(context);
  return {
    ...output,
    props: {
      ...output.props,
      // additional props and overrides
    },
  };
};