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

@paul-bfi/bfi-design-system

v0.2.125

Published

Next-gen design system for the British Film Institute

Downloads

8

Readme

📽 BFI Design Sytem

Netlify Status CircleCI

CURRENTLY IN BETA. SOME THINGS MIGHT NOT WORK

The next-gen design system for the British Film Institute.

🍿 Demo and docs

👉 BFI design system is here.

This is a living documentation powered by Storybook, where you can see all the available components and their variations.

🎬 Using the design system

npm install bfi-design-system

// Install peer dependencies
npm install react react-dom styled-components @reach/router

Import the components you'd like to use into your app. For example:

import React from "react"
import { Card } from "bfi-design-system"

const MyComponent = () =>
    <Card>My content</Card>

Each component has documentation in the design system explaining the avaliable props, how to use it, and any guidence on using it.

💻 Developing the design system

You need node and npm installed.

  1. Clone the repo and npm i
  2. npm run dev will start up the Storybook playground and start rollup watching for changes.

If you want, you can also include this repo in another app as if it were an npm package using npm link. This is great for developing both side-by-side.

How to publish a new version to NPM

  1. Ensure all tests pass with npm test
  2. If the snapshot tests are out of date due to changes in the components then ensure all is working and update them with npx jest --updateSnapshot
  3. Increment the next version number in the package.json file.
  4. npm publish. This will:
    • Run the tests
    • Bundle and transpile the code
    • Create and publish a tarball to NPM
  5. If you are wanting to utilise the updated design system, for example in the BFI web frontend you will then need to update the version number of the design system in the package.json file within that repo.

🧪 Testing

We use jest and react-test-renderer to run snapshot tests on all components.

npm test runs all the tests.

If you make changes to the output of components, you can regenerate the snapshot files with jest --updateSnaphot.

The snapshot test cases themselves come from the same stories.jsx file colocated with each component.

🧼 Linting

We use eslint and jsx-a11y to detect potential accessibility issues. Some code editors will automatically pick up problems, and it runs automatically with the jest tests, but you can also lint manually with npm run lint.

To-do list

  • Add more add-ons to the Storybook playground
  • Typescript support?
  • Update the styled-components dependency to ~5.0.0