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

@lynx-js/react-refresh-webpack-plugin-canary

v0.4.6-canary-20261029-0ef126ae

Published

A webpack plugin to hot refresh for Lynx.

Readme

A webpack plugin to hot refresh for Lynx

Main Thread Functions

Rspeedy's ReactLynx HMR integration updates Main Thread Functions and their shared dependencies before refreshing the corresponding background components. This also refreshes existing event bindings when a dependency changes without changing the function's worklet ID. No additional application API is required. Application updates include already loaded async chunks and the first worklet added to a background-only module within an async scope.

Each thread loads its own versioned update bundle through Native fetchBundle and loadScript. The shared HMR loader reads a manifest section and the sections for the requested update chunks. Background sections retain the existing SDK runtime wrapper and app scope; normal lazy loading keeps its existing loader. Background bundles do not carry worklet implementations for cross-thread HMR; the compiler supplies their definitions to the main-thread bundle. A failed update on either thread, or a missing main-thread completion, triggers a full page reload. Coordinated updates allow up to ten seconds for main-thread completion, then up to ten seconds for background application. Pending updates from the old page are discarded. Compatible component updates preserve useState; memoized values, including useMainThreadRef, follow the existing Fast Refresh reset behavior.

This integration applies to application HMR and uses the host's existing Native loading and DevTool reload capabilities. It does not add standalone lazy-bundle HMR or change production bundles.

If the host lacks main-thread fetchBundle or loadScript, the coordinator disables main-thread updates and retains the existing background HMR path. Background Native loading also requires the SDK to initialize the app wrapper: hosts without these APIs or that initialization capability retain the original background loader. The manifest probes initialization before update code runs. Actual Native load or application failures still trigger a reload. These fallbacks do not add Main Thread Function HMR to hosts without main-thread loading.