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

@flatfile/design-system

v5.3.0

Published

flatfile's design system

Downloads

27

Readme

Design system

This is the home for Flatfile's design system and component library. Please visit Installation for more detailed guidelines.

Developing locally

Using NPM:

First and foremost run npm install

To run Storybook npm run storybook

To test npm test

Building a new component

To create a new component, run npm run createComp {ComponentName}. The template folder contains a file for your component, docs, css, and tests. Don't forget to export your component from src/index.ts

Publishing to NPM

On your branch, run npm run changeset from the root of this repo and select @flatfile/design-system. Select the correct version update (major/minor/patch) and provide a message for what has changed. A changeset markdown file will be added that should be merged with your PR. Once merged, this will trigger a Github action to create a PR to update the version and publish the package.

Accessibility

Design system is built on top of React-Aria which provides accessibility and behavior according to WAI-ARIA Authoring Practice.

In order to use keyboard interactions in Mac OS (Safari and Firefox):

  1. Enable keyboard as a mouse via system preferences.
  2. In Safari: check Preferences > Advanced > Press tab to highlight each item on a page.

Review process

We require an approval from a member of the design team and a member of the engineering team.

Installation

npm install @flatfile/design-system

or

yarn add @flatfile/design-system

Consuming

Some components implicitly assume the existence of a global Tooltip component, make sure it exists by wrapping your app with AMPWrapper

import { Button } from '@flatfile/design-system'

Testing locally with separate project repo

If you have made changes within the design system repo and would like to test the new package locally:

  • From this repo
    • npm run pack:prod (or npm run build && npm pack)
  • In the consuming repo's package.json, update the design system dependency to
    • "@flatfile/design-system": "file:./path/to/flatfile-design-system-x.x.x.tgz"
  • In the consuming repo
    • npm i
  • Restart the application