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

@weareberyl/design-system

v1.25.0

Published

[![CircleCI](https://circleci.com/gh/team-blaze/beryl-design-system/tree/master.svg?style=svg&circle-token=d8409120cfde757b08a2b9fe928fd56bd1f3a785)](https://circleci.com/gh/team-blaze/beryl-design-system/tree/master)

Downloads

734

Readme

Beryl Design system

CircleCI

Primitive components for react-native-web & Beryl branded components

yarn add @weareberyl/design-system

For web

You also need to install peer dependencies:

yarn add react react-dom react-art

For native

Everything should work as normal without any changes.

Running the storybook

yarn start

Testing changes in other projects

We'll use yalc to better simulate a npm package publish and install. So, first, follow the steps from yalc to install it in your machine.

Setup

On beryl-design-system folder:

yarn build # builds the design system package
yalc publish # publishes as a npm package, but locally

On basis-engineering folder (or any other project):

yalc add @weareberyl/design-system # install from the "local npm"
yarn install # make sure added dependency is used, yarn.lock is updated
yarn start # make sure packager is restarted

Making changes

After making changes to the design system code, we need to publish the changes once again.

On beryl-design-system folder:

yarn build # builds the design system package with the changes
yalc publish --push # updates the published local package

On basis-engineering folder (or any other project):

yarn install # make sure added dependency updated
yarn start # make sure packager is restarted

Cleanup

On basis-engineering folder (or any other project):

yalc remove @weareberyl/design-system # puts back the symlink to the npm package
yarn install # updates yarn.lock

Deploying the storybook

yarn storybook:build
yarn storybook:deploy

Releasing the package

Releases are managed by git tags. So to make a release do git tag with your version eg 0.1.4-rc.1, then push the tag. Note unlike git tags npm packages can't be hard pushed over.

Accessibility

Make sure we add accesibility tags mentioned here: https://github.com/necolas/react-native-web/blob/master/docs/guides/accessibility.md

Api decisions

Largely inspired by jxnblk and rebass read this - http://jxnblk.com/blog/defining-component-apis-in-react/

  • Everything in /primitives is essentially a implementation of rebass with react-native-web, which should be highly configureable agnostic components.
  • Everything in /components are beryl specific configurations and composistions of the primitive components.