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

carbon-graveyard

v0.0.0

Published

Deprecated code from the carbon-react package.

Downloads

4

Readme

Carbon Graveyard

:skull: Where code comes to die.

All components and modules in this repository are no longer actively maintained, but are available for use if your application heavily relies on them. Ideally you should look to remove any dependency on this code.

Any code contributed to this repository should feature an associated README file with instructions on why it was deprecated and what alternatives you should look to use.

Making a Release

  • Update the version. You can either do this manually in the package.json file and run npm install to update the package-lock.json file, or you can run npm version x.x.x --no-git-tag-version.
  • Generate the release notes: ./script/generate-release-notes.sh.
  • Create a pull request with your changes into the release branch.
  • Once merged create a tag in GitHub from release for your new version number.
  • Check the release branch out locally and ensure the code is all up to date, publish the tag to npm with npm publish.
  • Merge release back into master to finish the release.