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

@cyverse-de/ui-lib

v7.1.1

Published

This project was bootstrapped with [Create React App](https://github.com/facebook/create-react-app).

Downloads

6

Readme

This repo serves as a common React component and util library for CyVerse's Discovery Environment user interfaces, such as the Discovery Environment and VICE.

Publishing to npm registry

Once your PR is accepted, Please merge your branch with master from your command-line and update the version. Then push your commits to master. This will trigger the workflow to build, run test and publish. All other steps listed under Development Workflow are optional.

npm run deploy-storybook

This will deploy any changes or updates to our components' code and stories to GitHub pages for users to see and test the functionality of the components.

Development Workflow

In the project directory, you can run:

npm install

Installs the project's dependencies.

npm run storybook

Launches the Storybook application for fast development and debugging. Generally, for any component in ui-lib there should be a story. Stories are also used to run the tests.

npm test

Launches the test runner in the interactive watch mode. All tests should pass before creating a merge request. See the section about running tests for more information.

npm version patch | minor | major

Once you've merged your changes, this will bump the version number of the project. Note: merge you changes from command-line only

Generally:

  • patch is used for backwards-compatible bug fixes.
  • minor is used when you add functionality in a backwards-compatible manner.
  • major is used when you make incompatible changes

git push --tags

After pushing the version bump created with npm version, you'll need to also push the new version's tag. The git push command will only push the file changes created by npm version, but it will not push tags.

In order to add the new tag to the public repo, you can use the command git push --tags. This will push all tags in your local repo to the public repo (if they're not already there).

If you have other local tags that you don't want to push to the public repo, then you can push only the tag created by npm version with a command like git push origin <new-tag-name>; or if you've named your local fork of the public repo upstream, then git push upstream <new-tag-name>.

(This project was bootstrapped with Create React App.)