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

@alberto91base/prueba-react-components

v0.2.38

Published

A simple template for a custom React component library

Downloads

26

Readme

Add component to storybook library and upload to npm

  1. Create component files, including tests and story
  2. Change import lines in scss files to adapt to project folder structure.
  3. Add component to index.js file at root level
  4. Execute chromatic to check if component is ok yarn chromatic
  5. Execute command MSG="(here we put the information about the task)" yarn upgrade-(patch/minor/major)
  6. Execute command npm publish to upload to npm
  7. In repo/s where this component is used, use yarn upgrade @npm_leadtech/legal-lib-components --latest,
  8. Change imports to use @npm_leadtech/legal-lib-components and delete component files.

Last modification instead of git commit we must write the following command

MSG="(here we put the information about the task)" yarn upgrade-(patch/minor/major)

NPM credentials

Private account

Chromatic

Url de acceso al Chromatic del proyecto https://www.chromatic.com/builds?appId=6561c745020967e7c053b406

Para ejecutar: yarn chromatic

Trabajo con yalc

  • Instale golbalmente yalc (solo la primera vez) npm i yalc -g
  • En la librería, tras realizar los cambios necesarios, compile y publique yarn build && yalc publish
  • En el proyecto donde se desea utilizar la librería ejecute: yalc add @npm_leadtech/legal-lib-components apuntando a la versión que generó previamente el paso anterior
  • Desde la librería agregue los cambio en el proyecto destino: yalc push