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

@ultimaker/react-web-components

v7.0.3

Published

Ultimaker's unified react component and style library for front-end web

Downloads

449

Readme

React Web Components

Warning: this library is considered deprecated. New simple components should live in stardust-web.

Build Dependabot Status

Installation

Make sure you have the following dependencies installed on your machine:

  • node.js 8.x
  • npm

Then clone this repository.

Run storybook

npm install
npm run start

Build storybook

Normally done automatically during CI.

npm install
npm run build

You can now serve the static content in the /public folder.

Release to npm

To make a new release, run npm version with the right parameters (see example). This will update the package.json file, commit the changes and create an annotated tag. After pushing, the CI will pick this up and publish it to npm. You should also make a release on github to document the changes.

See https://docs.npmjs.com/cli/version for supported parameters to npm version.

example (%s here will be automatically replaced with the new version number):

npm version patch -m "Upgrade to %s for reasons"
git push --follow-tags