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

libass-webos-legacy

v1.0.0

Published

A lightweight ASS subtitle rendering pipeline for legacy LG webOS browsers, built around libass with event-driven caching and performance-focused scheduling.

Downloads

26

Readme

libass-webos-legacy

A lightweight ASS subtitle rendering pipeline for legacy LG webOS browsers, built around libass with event-driven caching and performance-focused scheduling.

Build

The project ships two targets because webOS spans two very different Chromium versions:

| Target | Chromium | webOS | Emscripten SDK | | ------ | -------- | ------ | ----------------- | | modern | 68 | 4 / 5+ | emsdk:4.0.13 | | legacy | 38 | 3 | emsdk:3.1.73 |

Each target needs a different Emscripten toolchain, so a separate Docker image is built for each. The Dockerfile accepts an EMSDK_VERSION build-arg to select the SDK without editing the file between builds.

build.sh

Everything (Docker image → WASM compile → webpack bundle) is driven by a single script:

./build.sh [modern|legacy|all] [full|quick]

Defaults: all full.

| Target | Effect | | -------- | -------------------------------------------------------------------------- | | modern | Modern target only. | | legacy | Legacy target only. | | all | Both, sequentially. |

| Mode | Effect | | ------- | --------------------------------------------------------------------------------------------- | | full | Rebuild the Docker image with --no-cache, then make clean-libs && make <target> + webpack.| | quick | Reuse the existing image (build it if missing), skip clean-libs, then make <target> + webpack. |

Examples:

./build.sh                    # both targets, from scratch
./build.sh all quick          # both targets, reuse existing images and C libs
./build.sh modern             # modern only, from scratch
./build.sh legacy quick       # legacy only, incremental

Artifacts:

  • build/js/{modern,legacy}/worker.{min,debug}.js — raw emcc output.
  • dist/{modern,legacy}/ — webpack bundles ready to publish.

Manual invocation

If you need to bypass the script, the underlying steps are:

# Modern (Chrome 68)
docker buildx build -t libass-webos-legacy \
    --build-arg EMSDK_VERSION=4.0.13 \
    --no-cache --network=host .
docker run --rm -v "$PWD:/work" libass-webos-legacy \
    bash -lc "make clean-libs && make modern"

# Legacy (Chrome 38)
docker buildx build -t libass-webos-legacy-old \
    --build-arg EMSDK_VERSION=3.1.73 \
    --no-cache --network=host .
docker run --rm -v "$PWD:/work" libass-webos-legacy-old \
    bash -lc "make clean-libs && make legacy"

# JS bundle
npm install
npm run webpack                # or webpack-modern / webpack-legacy

make clean-libs is needed before switching between targets because the two toolchains produce incompatible object files. Use make clean for a full reset (deletes both build/ and the emitted JS).

Layout

  • src/ — C++ bindings and JS runtime (libass.cpp, libass.js, worker.js, LRUCache.js).
  • lib/ — vendored C dependencies (libass, freetype, harfbuzz, fribidi, brotli).
  • webpack/{common,modern,legacy}/ — bundler configs, one config pair per target.
  • build/ — CMake output (owned by the Docker container).
  • dist/{modern,legacy}/ — final JS bundles produced by webpack.
  • docs/ — design documents.