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

brokoli-ui

v10.45.2

Published

An UI design language and React UI library

Downloads

2,499

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

ioanaroceanuioanaroceanuaniculaeaniculae0xzenus0xzenusfilip-voltzfilip-voltzvoltzprotocolvoltzprotocol

Keywords

Readme

brokoli-ui

| Statements | Branches | Functions | Lines | | --------------------------- | ----------------------- | ------------------------- | ----------------- | | Statements | Branches | Functions | Lines |

Installation

  1. Run yarn
  2. Run npx husky install to activate husky

Run

  1. Run yarn storybook

Contributing

Branching model

In the UI world you should branch off main when building a feature. So just go on main, pull latest and then branch out of it. Create your PR against main.

Branch naming is quite standard, we tried to duplicate what we have done for the committing messages, following standard commit message format: [https://www.conventionalcommits.org/en/v1.0.0/].

Branch names can start with the prefixes found in the regex under '.husky/pre-commit'.

Short summary:

DEVELOPING

  • create a branch from main, follow the naming convention for a branch
  • wait for approval, resolve comments and make sure you have a green build
  • merge to main using Rebase and merge

Cloudflare

brokoli-ui uses Cloudflare to automate the process around creating builds that can be shared with the stakeholders. What this means is that any push to a branch will create an environment for the team to test against!

These are sites hosted on Cloudflare and the build from main can be found at brokoli.reya.xyz.

Rules

Environment branches (main)

  • merges to branch main always deploy to brokoli.reya.xyz with ENV variables specific for main

Candidate branches:

  • commits on branches that follow the pattern feat/*, fix/*, chore/*, refactor/* and test/*. Please follow these patterns.

Tools

Helpful tools to install to improve your development life!