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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@edvisor/product-language

v0.11.107

Published

Edvisor.io product-language components

Readme

product-language

This library was generated with Nx.

Storybook Guidelines

Bellow there are some goals to drive our way to build the design system stories with Storybook

  • The structure on Figma and Storybook needs to stay with the same names (consistency is the key). Please tell us if you detect some structure that aren't following that

  • Developers from the engineering team shouldn't need to open the code on their editors in order to understand and see how the things is working

    • The stories page from each component should be clear with what they have and what they don't have. In that case, use (or add) those information on Changelog (Roadmap)section
  • Components pages should be small and easy to understand. Don't be afraid to create a lot of pages to same component with their variations

    • Display only the props that can change the component behavior/display
  • Display best practices thinking on developers usage (if the situation required that)

  • Incrementally, we should have some pages that can render something nearly the mockups world, in order to make easy to figure out the components working together

Foundations Pages

Bellow there are some goals about the Foundations pages

  • Explain the guidelines and the fundamentals from a Design Perspective
  • Can teach developers people to learn about how the design works
  • This kind of pages don't need to show code/how to use

Running unit tests

Run nx test product-language to execute the unit tests via Jest.