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

@grogqli/webapp

v0.11.0

Published

The react webapp that provides a UI for interacting with grogqli features.

Downloads

2

Readme

@grogqli/webapp

The react webapp that provides a UI for interacting with grogqli features.

Development via Storybook

  • in monorepo root: npm start

  • in this package: npm run storybook

What was done to add Grogqli to this project's Storybook workflow?

This assumes the grogqli server has a previously saved workflow:

  • install grogqli addon

    • npm i -D @grogqli/storybook
  • add reference to grogqli addon in .storybook/main.js

    // .storybook/main.js
    module.exports = {
      addons: ['@grogqli/storybook'],
      // ...other configs
    };
  • added msw service worker to the next.js public subdirectory

    • mkdir public && npx msw init ./public
  • pass static assets option to npm storybook start script

    • "storybook": "start-storybook -p 6006 -s public"
  • set the links in apollo-client.ts to the same schemaUrl of the given schema recording

  • setup params

    • TODO show this
  • set env vars

    • publicPath
      • set the STORYBOOK_GROGQLI_PUBLIC_PATH env var either 1) inline storybook execution OR 2) in a .env file
    • schemaMappings
      • pass a string to string:string object that maps the schemaUrl(s) that are queried to the appropriate schemaId(s) found in the respective grogqli data
      type SchemaMappings = {
        [schemaUrl: string]: string;
      };