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

style-bubble

v1.0.5

Published

style components in isolation

Downloads

16

Readme

StyleBubble: Use new styled components inside old codebases in splendid isolation

Problem statement

You're starting to introduce styled-components to an existing React codebase that already has quite a lot of CSS/SASS/postCSS. Your styled components are lovely, but they keep going askew because of inherited or top-level element styles. So you have empty wrapper tags to escape CSS rules, or manually set unset in a lot of places, or use all at various levels in subtle and hard-to-reason about ways.

In any case, you will end up with with very specific properties and undocumented interactions that will become tomorrow's mysterious layout tech debt. Or you could use a tiny component with zero nonpeer-dependencies that helps you create the styles you need in the present without creating problems in the future.

Using StyleBubble

npm i style-bubble
#or
yarn add style-bubble
import React from 'react';
import StyleBubble from 'style-bubble';

// deep in the bowels of a legacy enterprise app...
<main className="enormous-page-legacy-styling-that-your-team-does-not-own">
    <section className="foo pony bar baz some__sass__from__2014">
        <StyleBubble resetType="initial">
            <MyNewIsolatedWidget/>
        </StyleBubble>
    </section>
</main>

Less time spent sifting through the ruins of a forgotten styling civilization is also less time spent falling into their traps.

Remember that StyleBubble is designed to protect you from inadvertent inheritance. If you actually do want to inherit some things, StyleBubble is best paired with a ThemeProvider below it.

API

resetType. Functionality and browser support are as defined by the CSS all spec, defaults to initial.