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/external-bundle-rsbuild-plugin-canary

v0.1.1

Published

An rsbuild plugin for loading lynx external bundles.

Readme

Getting Started

npm install -D @lynx-js/external-bundle-rsbuild-plugin

If you want to use the built-in reactlynx preset, also install:

npm install -D @lynx-js/react-umd

Usage

// lynx.config.ts
import { pluginExternalBundle } from '@lynx-js/external-bundle-rsbuild-plugin'
import { pluginReactLynx } from '@lynx-js/react-rsbuild-plugin'

export default {
  plugins: [
    pluginReactLynx(),
    pluginExternalBundle({
      externalsPresets: {
        reactlynx: true,
      },
      externals: {
        'lodash-es': {
          bundlePath: 'lodash-es.lynx.bundle',
          background: { sectionPath: 'lodash-es' },
          mainThread: { sectionPath: 'lodash-es__main-thread' },
          async: false,
        },
        './components': {
          bundlePath: 'comp.lynx.bundle',
          background: { sectionPath: 'component' },
          mainThread: { sectionPath: 'component__main-thread' },
        },
      },
    }),
  ],
}

If your external bundle request key already matches the produced section names, you can use the shorthand string form:

pluginExternalBundle({
  externalsPresets: {
    reactlynx: true,
  },
  externals: {
    './App.js': 'comp.lynx.bundle',
  },
})

The shorthand expands to the same bundlePath plus default:

  • libraryName = './App.js'
  • background.sectionPath = './App.js'
  • mainThread.sectionPath = './App.js__main-thread'
  • async = true

If you need custom section names or a custom exported library name, use the full object form instead:

pluginExternalBundle({
  externalsPresets: {
    reactlynx: true,
  },
  externals: {
    './App.js': {
      libraryName: 'CompLib',
      bundlePath: 'comp.lynx.bundle',
      background: { sectionPath: 'CompLib' },
      mainThread: { sectionPath: 'CompLib__main-thread' },
      async: true,
    },
  },
})

bundlePath vs url

Prefer bundlePath for bundles that belong to the current project.

  • bundlePath
    • resolves through the runtime public path
    • lets the plugin serve local bundles in development
    • lets the plugin emit managed bundle assets during build
  • url
    • uses a fully resolved address directly
    • is better only when the bundle is hosted outside the current build output, such as on a CDN

For the built-in reactlynx preset, bundlePath is especially recommended because the plugin will automatically emit react.lynx.bundle by resolving @lynx-js/react-umd/dev or @lynx-js/react-umd/prod.

Building project-owned external bundles

By default, pluginExternalBundle reads project-owned external bundles from dist-external-bundle before emitting them into the final app output.

If you use that default directory, no extra config is needed:

pluginExternalBundle({
  externals: {
    './components': {
      bundlePath: 'comp.lynx.bundle',
      background: { sectionPath: 'component' },
      mainThread: { sectionPath: 'component__main-thread' },
    },
  },
})

Then:

  • development serves dist-external-bundle/comp.lynx.bundle
  • production emits that bundle into the app output

If your local external bundles live somewhere else, set externalBundleRoot explicitly.

ReactLynx preset

externalsPresets.reactlynx expands the standard ReactLynx module requests automatically, so you do not need to write the full externals map by hand.

If your app needs business-specific presets, define them next to externalsPresets:

pluginExternalBundle({
  externalsPresets: {
    lynxUi: true,
  },
  externalsPresetDefinitions: {
    lynxUi: {
      resolveExternals() {
        return {
          '@lynx-js/lynx-ui': {
            libraryName: ['LynxUI', 'UI'],
            bundlePath: 'lynx-ui.lynx.bundle',
            background: { sectionPath: 'LynxUI' },
            mainThread: { sectionPath: 'LynxUI__main-thread' },
            async: false,
          },
        }
      },
    },
  },
})

If you want to extend the built-in reactlynx preset instead of defining a completely separate one, use extends:

pluginExternalBundle({
  externalsPresets: {
    reactlynxPlus: true,
  },
  externalsPresetDefinitions: {
    reactlynxPlus: {
      extends: 'reactlynx',
      resolveExternals() {
        return {
          '@lynx-js/lynx-ui': {
            libraryName: ['LynxUI', 'UI'],
            bundlePath: 'lynx-ui.lynx.bundle',
            background: { sectionPath: 'LynxUI' },
            mainThread: { sectionPath: 'LynxUI__main-thread' },
            async: false,
          },
        }
      },
    },
  },
})

Use it together with @lynx-js/lynx-bundle-rslib-config when producing external bundles:

import { defineExternalBundleRslibConfig } from '@lynx-js/lynx-bundle-rslib-config'

export default defineExternalBundleRslibConfig({
  output: {
    externalsPresets: {
      reactlynx: true,
    },
  },
})

Documentation

Visit Lynx Website to view the full documentation.

Contributing

Contributions to Rspeedy are welcome and highly appreciated. However, before you jump right into it, we would like you to review our Contribution Guidelines to make sure you have a smooth experience contributing to this project.

License

Rspeedy is Apache-2.0 licensed.