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

@aller/shiny

v0.53.3

Published

Shiny components for your React application. Check out the [storybook](https://dbmedialab.github.com/shiny/)!

Downloads

395

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

toremeektoremeekaslak2800aslak2800roninjcroninjcmariusjnmariusjnlobuntolobuntokonrad-jkonrad-joyvigrioyvigrigoodlebygoodlebyjimoejimoevnorvikvnorvikkevinmidboekevinmidboe

Keywords

Readme

Dependabot Status Travis badge install size

Ev'rythings shiny, cap'n, not to fret!

Shiny

Shiny components for your React application. Check out the storybook!

In Aller Media, we use shiny as part of a four-layered frontend system:

  1. shiny (dumb frontend components): Makes stuff look good
  2. wolverine-frontend (smart web app): Translates from what something is to what it should look like; handles state; renders pages
  3. wolverine-api (smart API layer): Decides what we should display to the user; composes pages
  4. wolverine-fetcher (dumb API layer): Fetches data from backend systems

Releasing

Primary way (np)

  1. Make sure your changes are in master
  2. Run yarn release
  3. Follow the interactive release guide

Alternate way (vanilla)

(After you have merged you changes into master)

  1. Get the latest version, and checkout a release branch for npm work. The release branch is necessary because the master branch is protected.
# Replace x.x.x with your new version number
git checkout master && git pull && yarn && git checkout -b release/x.x.x
  1. Publish it! Yarn will prompt you to for a new version number. Until we have reached 1.0.0, breaking changes or new features should trigger a minor version bump, while bug fixes should trigger a patch version bump. In other words: Don't inadvertently release 1.0.0!
yarn publish
  1. yarn publish will have created a commit with your new version number, and tagged your release in git for you. Push both the commit and the tagged release to GitHub.
git push --tags -u origin release/x.x.x

  1. Create and merge a pull request for the branch

  2. Add release notes by opening the visiting Shiny's releases overview page on GitHub, clicking your newly pushed release and then clicking the "Edit tag" button.

Relation to Firefly (the TV series)

The name is very inspired!