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

catastrophee

v0.0.5

Published

Reusable components, models and utils for react and mobx apps

Downloads

4

Readme

Catastrophee Development

Cloning the repo

Running examples

Make sure you:

  • are using node version >=8.0.0 <11.0.0
  • have yarn installed

Then run

yarn install
yarn start

Storybook will be available on http://localhost:9001, it should open automatically for you on your browser. If it doesn't, go to that link.

Any changes to any of the stories, packages components will be loaded instantly.

Ready to develop components?

All components are available in the /packages folder. Each folder is a different library, has its own version and can be published separately. We currently have 3 packages:

  • models: gets published to @catastrophee/models
  • styles: gets published to @catastrophee/styles
  • uicommon: gets published to @catastrophee/ui

More information about each component is available in their own README.

Updating and publishing components

After you improved a component, you need to publish a new version so it is available for everyone to use. To publish, make sure you are in the root folder and run the following command:

lerna publish

It will ask you to update the version, you can update the version number and continue. Don't forget to push your updates to master after you are done. I would like anyone to know the oficial published version by looking at the package.json in the repo.

Example: You just updated the JumpMenu compononent in the uicommon library. Make sure you are in root folder and run lerna publish.

Note: At the moment of this writing, consider Catastrophee components a BETA testing library. If you are reading this note it means it is still beta. I will remove this warning once it is not beta anymore. This means that components are not all bullet proof yet and may need updates. I will try to make a note in the readme to let you know what features may be missing or what not, but the components available should give you at least the basics.

Updating Storybook

In the root folder

yarn run build-storybook
git add storybook-static/
git commit -m "Update docs"
git push origin mater

Note when you run yarn run build-storybook it will create a bunch of js and d.ts files in the packages folder, don't commit those to master. Please only commit the storybook-static folder