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 🙏

© 2026 – Pkg Stats / Ryan Hefner

oc-template-esm-compiler

v4.1.0

Published

Compiler for the ESM OC template

Readme

oc-template-esm-compiler - Compiler module

OC template to compile components of type oc-template-esm

The mount context

Components created with createComponent receive a context object as the third argument of mount(element, props, context):

type RendererContext = {
  // The shadow root the component renders inside, or `null` in the light DOM.
  shadowRoot?: ShadowRoot | null;
  // The <style> element the compiler injected for this component (and its id).
  styleElement?: HTMLStyleElement | null;
  styleId?: string;
};

The template resolves shadowRoot for you in both cases where a component ends up inside a shadow root:

  • when the component opts into an isolated shadow root itself via oc.files.template.shadowDOM, and
  • when the page embedding the component mounts it inside a shadow root it owns.

Detection uses the standard element.getRootNode() API, so closed and nested shadow roots are handled correctly and components never need to walk parentNode to find the root themselves.

What a component does with that information — where to inject its runtime styles, where to render portals/overlays so they stay within the shadow boundary — is up to the component and its rendering libraries. The template only tells it where it is; it deliberately doesn't reach into the component's styling or DOM.

import { createComponent } from 'oc-template-esm-compiler/renderer';
import { createRoot } from 'react-dom/client';
import App from './App';

export default createComponent(() => {
  let root;
  return {
    mount(element, props, { shadowRoot }) {
      root = createRoot(element);
      root.render(<App {...props} shadowRoot={shadowRoot} />);
    },
    unmount() {
      root?.unmount();
    }
  };
});

The same detection is exported as a standalone helper if you need it elsewhere:

import { getShadowRoot } from 'oc-template-esm-compiler/renderer';

const shadowRoot = getShadowRoot(element); // ShadowRoot | null