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-styleable

v0.2.0

Published

A proof-of-concept implementation of open-styleable shadow-roots, using a combination of:

Downloads

10

Readme

open-styleable

A proof-of-concept implementation of open-styleable shadow-roots, using a combination of:

  • A build-time HTML transform for declarative shadow DOM
  • A client-side script that overrides attachShadow

Demo

View the hosted examples:

Edit the code live:

Open in StackBlitz

Usage

(See standalone setup instructions below if you're trying to use this in your own project) 👀

The access for open styles is controlled at the shadow-root level. Every shadow-root needs to explicitly opt-in using one of the following ways.

For declarative shadow DOM (DSD):

  • Add the adopthoststyles attribute to the DSD template. This shadow-root will now automatically inherit all styles from the host context (i.e. the document or a parent shadow-root).

    <template shadowrootmode="open" adopthoststyles>…</template>
  • Alternatively, if you only want to adopt styles from the document and not from the parent shadow-root, then you can use adoptpagestyles.

    <template shadowrootmode="open" adoptpagestyles>…</template>

For client-rendered shadow-roots, use the adoptPageStyles and adoptHostStyles options when calling attachShadow.

  • Use adoptHostStyles to adopt all styles from the host context.
    this.attachShadow({
    	mode: "open",
    	adoptHostStyles: true,
    });
  • Use adoptPageStyles to adopt all styles from the page/document only.
    this.attachShadow({
    	mode: "open",
    	adoptPageStyles: true,
    });

[!IMPORTANT] There are some known limitations/caveats that you should be aware of.

Standalone setup

To use this "polyfill" in your own project:

  1. Install open-styleable from npm (or use import maps).
    npm add open-styleable
  2. Hook up the HTML transform into your templating system (see .eleventy.js for an example). This should ideally be executed after all bundling steps.
    import { transformHtml } from "open-styleable";
    // assuming `htmlContent` is the original page content
    htmlContent = transformHtml(htmlContent);
  3. Include the /client script in your <head> before any custom elements are registered.
    <script>
    	import "open-styleable/client";
    </script>
    or from a CDN:
    <script src="https://esm.sh/open-styleable/client"></script>

[!NOTE] You do not always need to use both the build-time transform and the client-side script. They are completely independent and do different things.


Development

This demo is built with 11ty. All test pages go in the pages/ directory.

Open in GitHub Codespaces

To run it locally, clone the repo and follow these steps:

  1. Install dependencies.

    npm install
  2. Start the dev server.

    npm run dev
  3. Open up localhost:1174 in your browser.