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

@boostxyz/boost-ui

v0.10.3

Published

## Best Practice

Downloads

985

Readme

@boostxyz/boost-ui

Best Practice

  1. Don't compose primitive component packages (ie. Don't include a <Button> in a <Card>). Allow the implementor to use them together.

Adding a Component

Latest Steps

  • pnpm run ui:add -- table (or whatever component)
    • this will install to packages/ui/src/components/*.tsx
  • pnpm run ui:integrate table.tsx (or whatever the output file is)
    • answer the steps to generate packages/ui/src/components/MyComponent/*
  • Integrate your component for testing in apps/nextjs/src/apps/page.tsx
    • Add an accompanying *.stories.tsx for the component in apps/storybook/stories

Former Steps

  • pnpm run ui:add -- table (or whatever component)
    • this will install to packages/ui/src/components/*.tsx
  • It's probably best to stop your dev server so it can rebuild when you add the new component.
    • Restart it after you've stubbed out your component
  • Create the component directory structure to introduce the new component:
    • Duplicate a simple component (like Badge) and rename the component to your new one (including the copied files)
      • BaseBadge -> BaseNewThing
  • Copy everything except the imports from the downloaded component file, and replace everything below the imports with it
  • Rename all of the new components to be prefixed with Base
  • Replace all tailwind utility classes with a single styles.BaseComponent declaration, and apply them in the accompanying BaseComponent.module.css
    • To ensure legibility, split each class name at the space, and turn it into a new @apply line
    • Remove all dark: directives, as these will be controlled using :global(.dark) .some-class {}