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

@navinc/base-react-components

v22.22.1

Published

Nav's Pattern Library

Downloads

12,026

Readme

@navinc/base-react-components

Is split into two different parts: Storybook, and Base Components. Storybook is used for development and testing of the ui and for reference for developers on the implementation details of an UI component. The readme files for each component inside Storybook acts as the Styleguide. Lastly, Base Components is the directory containing all of our base reusable components which gets published as the npm package.

You can view the current build of Storybook here.

Bug Reporting: For technical issues post to ux-guild or front-end-team slack channel. For design issues talk to a designer.

Quick start

Please run all commands from the monorepo root.

  1. npx lerna run start --stream --scope=@navinc/base-react-components - Make changes and watch them at http://localhost:9009/
  2. Watch and run your tests with npx lerna run test:watch --stream --scope=@navinc/base-react-components
  3. Test in pipsqueak with ./bin/copy-package brc pip or to continuously copy over to pip npx lerna run dev:pip --stream --scope=@navinc/base-react-components
  4. When it works as you need it to, build it: npx lerna run build --stream --scope=@navinc/base-react-components
  5. Run the tests post build: npx lerna run test --stream --scope=@navinc/base-react-components

Getting Started with Storybook

To start Storybook, go to the monorepo root and run the following:

npx lerna run start --stream --scope=@navinc/base-react-components

And go to http://localhost:9009/

Contributing

Adding a new Base Component: Copy the pattern used with other base components. Each component should have its own folder with a structure similar to

/parts/...js  //Optional
/index.js
/readme.md
/story.js

If it makes sense, organize related components by putting them in their own sub directory, ei: /typography, but prefer a flat file structure.

IMPORTANT: Don't forget to add them to the main base-components/index.js file.

When should you add a new component? Good question! You should add a component to our base components when you have found a good reusable abstraction of a piece of our ui. Make sure the team agrees with the abstraction and that it has been passed off by design then add it and and create a pull request for it.

Testing Locally in pipsqueak before publishing Assuming pipsqueak and base-react-components are both in ~/{user}/nav/ you can use bin/copy-to-pip and it will build base-react-components and manually put it in the node_modules folder in pipsqueak for you. Then you can restart pipsqueak and see your changes.

Updating a Base Component: This can be dangerous waters. Its super easy to update global components now, but be careful cause this will change it everywhere its used! Make sure to be smart about changes you make and to thoroughly test your changes! If you do make global changes, make sure you bump the major version.

Building

Base Components

npx lerna run build --stream --scope=@navinc/base-react-components

Storybooks

npx lerna run build:storybook --stream --scope=@navinc/base-react-components

And open /public/base-react-components/index.html to test storybook.

Testing

  1. npx lerna run test --stream --scope=@navinc/base-react-components This will run Vitest and our linter.

Using base-react-components in your own projects

  1. Install it in your project npm i @navinc/base-react-components
  2. Use it! Ex: import { Copy } from '@navinc/base-react-components'
  3. Refer to Storybook for implementation details for each component.

Add-ons

We use the following add-ons are in Storybooks. Please read their documentation for more details.

  • Controls: allow you to edit React props dynamically using the Storybook UI.
  • Viewport: allows your stories to be displayed in different sizes and layouts
  • Actions: used to display data received by event handlers.
  • Options: used to set configure the Storybook UI.
  • a11y: accessibility testing. story.
  • Info : Shows additional info in the storybook ui about a component

App TODO/Wishlist

  • Add back Loki
  • Add eslint from pip
  • Automate most of the build in the pipeline
  • Add https://github.com/buildit/storybook-addon-versions