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

open-stylable

v1.0.0

Published

Web component where styles leak in, but they don't leak out

Downloads

5

Readme

open-stylable

Tiny (<0.5kB min+gz) proof-of-concept implementation of an "open-stylable" web component. It can be styled from the global <head>, even though it uses shadow DOM.

So basically: styles leak in, but they don't leak out.

<head>
  <style>div { color: red }</style>
</head>
<body>
  <my-component>
    #shadow-root
      <div>I'm red!</div>
  </my-component>
</body>

Demo

Usage

Install:

npm install open-stylable

Then use as a mixin:

import { OpenStylable } from 'open-stylable'

class MyComponent extends OpenStylable(HTMLElement) {
  constructor() {
    super()
    this.attachShadow({ mode: 'open' }).innerHTML = '<div>Hello world</div>'
  }
}

This custom element will use shadow DOM, but any styles from the <head> will be copied into its shadow root.

connectedCallback and disconnectedCallback

If you use connectedCallback or disconnectedCallback, be sure to call super:

class MyComponent extends OpenStylable(HTMLElement) {
  connectedCallback() {
    super.connectedCallback()
    /* Your code */
  }
  disconnectedCallback() {
    super.disconnectedCallback()
    /* Your code */
  }
}

In a framework

The OpenStylable mixin allows you to use whatever constructor you like. For instance, with a Lit component:

class MyComponent extends OpenStylable(LitElement) {
  /* ... */
}

Limitations

This only works with open shadow DOM, not closed shadow DOM.

Also, it doesn't work with selectors that cross shadow boundaries, such as body.foo *.

Additionally, it only works for <style> and <link rel="stylesheet"> tags in the <head>. More exotic ways of inserting styles, such as insertRule and document.adoptedStyleSheets, are not supported.

Although it would be possible to support such things, it would increase the bundle size and require global patching, which is a big cost for a niche feature.

This implementation also uses MutationObserver, which may have performance considerations if you have a lot of components and frequently-changing global styles.