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/lynxtron-builder

v0.0.31

Published

`lynxtron-builder` packages applications with the production runtime by default. The installed `lynxtron` CLI uses the DevTool-enabled runtime by default, so the normal development and packaging commands do not require different npm versions.

Readme

Lynxtron Builder

lynxtron-builder packages applications with the production runtime by default. The installed lynxtron CLI uses the DevTool-enabled runtime by default, so the normal development and packaging commands do not require different npm versions.

Building the npm package

Publish with npm. Both npm pack and npm publish run prepack to install, patch, and verify the toolchain under vendor/. The published package includes this prepared toolchain, so npm, pnpm, and Yarn consumers do not need an install script to apply patches. When developing from source, run npm run prepack in this package before invoking the builder.

Runtime selection

To package a DevTool-enabled application, add this package-specific section to electron-builder.yml:

lynxtron:
  runtimeVariant: devtool

The builder consumes this section before invoking electron-builder. Valid variants are release and devtool.

You can also override the variant for one command:

lynxtron-builder --lynxtron-runtime=devtool --mac

Selection precedence is command line, LYNXTRON_RUNTIME_VARIANT, electron-builder.yml, then the release default. An explicitly configured electronDownload remains authoritative.

AutoLink native packages

pluginLynxtron() stages matching native packages under .lynxtron/native. The builder includes that directory in the final app and keeps it outside ASAR so native addons and adjacent runtime files remain loadable.

Every lynx.lib.json target must use literal package-relative artifact paths and standard os (darwin, win32, linux) and arch (arm64, x64, ia32) names. Variables, globs, and aliases are rejected. The builder selects the packaging target from the original staged manifest; it does not expand or rewrite that manifest.

For macOS targets, Frameworks and nested applications declared by the selected platforms.lynxtron.targets record are copied into Contents/Frameworks with their symbolic links preserved. Nested applications use appBundles and are included before electron-builder signs the outer application. For Windows targets, declared files stay under app.asar.unpacked, including the selected .node addon, DLLs, resource packs, and locales.

Runtime distribution

Default builds fetch the exact Release runtime platform package from the configured npm registry, extract it into the npm cache, and pass the directory to electron-builder as electronDist. DevTool builds use the matching DevTool package. Cross-platform targets and macOS universal slices fetch their own target archives independently.

Project/user .npmrc registry, scoped registry, authentication and proxy settings apply. Existing explicit electronDist or electronDownload configuration takes priority. MAS has no published npm runtime and requires an explicit runtime source.