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

@pillarbiosci/design_library

v0.2.25

Published

Pillar's Design Pattern Library

Downloads

8

Readme

Pillar Design Library Readme

Storybook configuration.

To run storybook you should Follow these steps

  1. Clone repo into folder of your choice
  2. Checkout development branch
  3. Run npm install
  4. Copy the storybook configuration from launch.default.json to new file launch.json
  5. Launch storybook
    • VS Code users: Use the run/debug panel in the lefthand toolbar to launch storybook.
      1. Click the Run and Debug icon
      2. Select Storybook from the dropdown at the top & press the play icon
      3. The storybook site will launch in your default web browser.
    • Alternatively/non-VS Code users:
      1. Run npm run storybook
      2. The storybook site will launch in your default web browser.

Interactions Panel can be open by pressing D on your keyboard when focused on a story.

Eslint Configuration

  1. install the vscode eslint plugin (by microsoft millions of downloads).
  2. open a .js file and open the command palette (ctrl+shift+p)
  3. choose ESLINT Show Output channel

Only need to do this once and then its set up and running.

Styleint Configuration

  1. install the vscode stylelint plugin.
  2. open a .scss file and open the command palette (ctrl+shift+p)
  3. errors and warnings should show in the file and the problems tab if there are any.

npm Configuration

  1. Go to https://www.npmjs.com/ and create an account with a username and password.
  2. Your user must be added to the pillarbiosci Origization (Ask Marc About invite email)
  3. Run npm login
  4. login with your username and password.
  5. Run npm whoami to confirm you are logged in.
  6. Go to https://www.npmjs.com/~<your user name>/tokens
  7. create access token.
  8. create a .env file in the root directory and add NPM_TOKEN=<your access token>

Build Pacakge and Publish to npm.

This is mostly automated now. All you need to do prior to opening a pull request is bump the version (which will also be automated soon)

npm version patch // (for development merge) or npm version minor // (for master merge)

---This is automated, only run if needed---

  1. In package.json increment the version by 0.0.1
  2. Run rm -rf ./node_modules; npm install
  3. Run rm -rf ./dist; npm run build The ./dist folder now contains a build from your current branch.
  4. Run npm init --scope=@pillarbiosci first time only.
  5. Run npm publish