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 🙏

© 2025 – Pkg Stats / Ryan Hefner

sushi-bazooka

v0.20.1

Published

Component-based JavaScript library

Readme

Sushi Bazooka

Component-based JavaScript library

Sushi Bazooka has a set of reusable, little opinionated components — what means they will be most likely be missing styling until you add it yourself. Opinionated properties will be commented-out in the code to serve as examples of where you should be styling things.

Including your styles

You should include your styles after including the base styles from Sushi Bazooka. In your main SCSS file it might look like the following:

@import "node_modules/sushi-bazooka/sass/components/chaser"; // base styles
@import "mysite/components/chaser"; // opinionated styles

Wait... I'm overriding rules now

Yes, you are. And, of course, this is pretty bad. But at least now you have a somewhat pre-built list of JavaScript components that can be used as-is if you'd like or can be overridden with your own styles.

But if you think that's not a good reason to break the cleanliness of your code, clean-css got you covered with the merge flags in its Level 2 Optimizations. Win-win.

Sushi Base

Most components rely on the global spacing variables included by default in Sushi Base and it's assumed that you will include Sushi Bazooka alongside Sushi Base. Working with Sushi Bazooka own its own is not supported and will not work unless you spend a fair amount of time building its dependencies from scratch.

Variables

Some components (like Reveal) may have opinionated but required properties (like Reveal's transition duration). Those properties have a default reasonable value and may be customized through variables, which are set at the very beginning of each component's SCSS file. Usually we don't go that route because maintaining a big set of variables defeats the purpose of using an object-oriented approach to CSS, but sometimes (like inside a placeholder class that can't be easily overridden) that's the only way to make things work while keeping a minimum of customization options.

Current customizable global variables are:

  • $globalTransitionTimingFunction CSS easing function, default: ease-in-out -- Global timing function to be used for all transitions. Any easing function from easings.net should work on all major browsers.
  • $globalBorderRadius pixels, default: 3px -- Base border radius used across

You can see more variables in settings/_variables.scss, where you will also find further comments on their use.

No JS