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

@sigx/lynx-runtime-main

v0.2.7

Published

Main Thread (Lepus) entry and ops applier for SignalX Lynx renderer

Readme

@sigx/lynx-runtime-main

Main-thread (Lepus) runtime for SignalX on Lynx. Receives the op stream from @sigx/lynx-runtime, mutates the native render tree via Lynx PAPI, and runs 'main thread'-marked worklets at the host's display refresh rate.

Application code rarely imports from this package directly. The build pipeline (@sigx/lynx-plugin) wires it into the main-thread bundle automatically.

Responsibilities

  • entry-main.ts — installs globalThis.processData, renderPage, updatePage, sigxPatchUpdate, sigxRunOnMT, and runOnBackground. This is the file the build plugin lists as the first import in the MT bundle so the Lynx runtime finds the global hooks it expects.
  • ops-apply.ts — the applyOps loop that consumes the BG → MT op stream (CREATE, INSERT, SET_STYLE, SET_WORKLET_EVENT, INIT_MT_REF, REGISTER_AV_BRIDGE, ...) and translates them into PAPI calls (__CreatePage, __SetInlineStyles, __AddEvent, etc.).
  • MTElementWrapper — high-level wrapper your worklets drive via mainThreadRef.current.method(...) (setStyleProperties, getComputedStyleProperty, animate, invoke, query selectors).
  • Hybrid worklet dispatch — the slot machine in event-slots.ts plus the hybrid context in hybrid-worklet.ts lets a single MT slot carry both a worklet handler and a BG-side handler for the same event, dispatching to both.
  • AnimatedValue bridgeanimated-bridge-mt.ts diffs registered AVs against last-published snapshots and dispatches batched Lynx.Sigx.AvPublish events to BG once per __FlushElementTree boundary. The matching BG sink lives in @sigx/lynx-runtime.
  • useAnimatedStyle mapper registryanimated-style-mappers.ts ships built-in mappers (translateX, scale, opacity, ...) and exposes registerMapper(name, fn) so MT-side code can add custom ones.

Bootstrap order

Three modules must evaluate in this order on the MT thread:

  1. entry-main — sets globalThis.SystemInfo and the renderer hooks.
  2. @lynx-js/react/worklet-runtime — installs lynxWorkletImpl, registerWorkletInternal, runWorklet.
  3. install-hybrid-worklet — registers the hybrid dispatcher into the now-populated worklet map.

@sigx/lynx-plugin prepends side-effect imports for these three at the top of every file in the MT bundle, so the order is enforced regardless of which user file the Lynx runtime evaluates first.

License

MIT