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

@roku-sdk/compat

v2.19.1

Published

Shims that stand in for SceneGraph nodes older Roku OS firmware lacks

Readme

@roku-sdk/compat

Shims for SceneGraph nodes that the SDK renders but firmware does not report as supported.

The package is a side-effect import. rk build and rk dev inject it ahead of the app entry, so apps do not import it themselves. Set app.compat: false in roku-config.ts to leave it out.

What it does

Each shim registers a tag alias with registerTagAlias from @roku-sdk/solid. When the tag is created, the alias asks hasFeature("tween") from @roku-sdk/runtime/has-feature whether the firmware has the real node. If it does, the real node is created. If not, the shim is created instead.

| Tag | Native node | Firmware feature | Shim | | --------- | ----------- | -------------------------- | -------------- | | <tween> | Tween | roku.hasFeature("tween") | RsgTweenShim |

hasFeature returns false when roku or roku.hasFeature is absent, including Jest. The firmware feature set starts empty; until firmware adds "tween", devices use the shim regardless of their OS version.

When app.compat: false, the Roku build injects only the native-or-refusal registration, not the shim XML or BrightScript. Importing @roku-sdk/rsg-ts alone performs no registration; only the Roku build injects these entries.

In a Roku build without shims, creating a gated tag when its feature is not reported throws an error naming the missing firmware feature and this package. That is deliberate: a SceneGraph node type the firmware does not have fails silently and leaves an empty screen.

Retiring a shim

Removing a shim drops support for every firmware that does not report its native feature, so it is a breaking change:

  • Remove shims only in a major SDK release, and state which firmware features that release requires.
  • Batch removals into one release rather than shipping one breaking release per shim.
  • Remove the shim's directory here and its entry in refuse-gated-tags.ts once all supported firmware reports the feature. @roku-sdk/solid does not change.

An app that must keep running on older firmware can stay on the last @roku-sdk/compat release that has the shim it needs.