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

mantecao

v0.3.0

Published

A react UI library for resmio

Downloads

4

Readme

#mantecao resmio UI Library powered by react components

##Cool, how does it work? Do you really care? This is what you need to know

###To develop:

  • from the root folder run npm install (takes a while the first time)
  • Code the element (you can mimic src/TestComponent)
  • Require and instantiate the react element in src/index.dev.js
  • Then run npm start to start the dev server
  • In your browser go to http://localhost:3000

###To run the tests:

  • Write the tests inside the component folder (check src/TestComponent)
  • Import the test in src/tests.js
  • Now you have two options:
    • npm test -> runs the js linter and the tests
    • npm test:only -> runs only the tests

###To publish:

  • Run the tests, if they fail fix the code
  • Once the tests are passing commit your code
  • From the root folder run npm version patch (or check this for version types)
  • If you haven't do npm adduser resmio and ask someone for the password
  • Run npm publish it will build the lib and push it to npm

###I hate those linting errors, I want to express myself with my code. We are all artists, I know. You can run npm run lint:fix to have the linter fix the errors automatically