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

zooniverse-react-components

v0.14.2

Published

Zooniverse-React-Components ===========================

Downloads

19

Readme

Zooniverse-React-Components

Build works against Node 16 and NPM 8.

What the repo name says

npm ci to install dependencies

Components should be added to the src/components folder and an export to src/index.js

Any default styles can be added as a stylus file in src/css.

npm test to run mocha tests

npm version [semver new version] will run helper preversion and postversion scripts. preversion will run the tests. version will run npm run build which will build the production css and js. postversion will push the updated repo and the updated git tag to github.

Contributing

If you're using npm link to test the library with your app, then you may need to adjust your webpack configuration for compiling of your javascript files in development. Webpack docs do provide a cautionary note about using symlink packages with Webpack: https://webpack.js.org/configuration/module/#rule-conditions. An example webpack configuration:

{
  test: /\.jsx?$/,
  include: path.resolve(__dirname, 'src'),
  exclude: path.resolve(__dirname, 'node_modules'),
  use: [
    'babel-loader'
    // 'eslint-loader' uncomment if you want to use eslint while compiling
  ]
}

Publishing

  1. Add the new version to the changelog.
  2. npm version major|minor|patch to test, build, and push a new tagged version. https://github.com/zooniverse/Zooniverse-React-Components/blob/3b9a027132e85480b6882fa53129186ef4a128a1/package.json#L16-L19
  3. Publish the new tag as a release on GitHub.
  4. npm publish --dry-run to double-check the release.
  5. npm publish.