@osdlc/npm-binary 0.0.0-stage → 0.0.1-stage

package/CHANGELOG.md

@@ -0,0 +1,25 @@
+# @osdlc/npm-binary
+
+## History before the first public release
+
+These versions were never published. The first release of `@osdlc/npm-binary`
+on npm is 0.1.1, and the entry for it is added above this section when it is
+released.
+
+### [0.1.0] - 2026-10-06 (unpublished)
+
+#### Added
+
+- Ship a compiled binary through npm as one launcher package plus one
+  `os`/`cpu`-gated package per platform.
+- Platform helpers: `platformKey`, `platformPackageName`, `binaryExt`,
+  `binaryFileName`, `binaryPathInPackage`, `findPlatform`, `hostPlatform`,
+  `NPM_PLATFORMS`.
+- `platformManifest` and `launcherManifest` package.json builders, which keep
+  a product's template key order; `writeJson` and `copyExecutable`.
+- `renderLauncher`: a Node launcher shim that resolves the platform package,
+  runs the binary with inherited stdio, forwards signals to it and re-raises
+  the binary's signal or exits `128 + signal`.
+- `publishPackages`: platform packages first, the launcher last, skipping
+  versions already published.
+- `cargoTargetDir`: cargo's target directory from `cargo metadata`.

package/CONTRIBUTING.md

@@ -0,0 +1,61 @@
+# Contributing
+
+Thanks for your interest in `@osdlc/npm-binary`.
+
+## Issues
+
+Report bugs and ask for features in the
+[issue tracker](https://github.com/osdlc/osdlc/issues). For a bug, include the
+library version, your Node and npm (or pnpm, Yarn, Bun) versions, your
+operating system and CPU, and a minimal example: the product names you pass
+and the package.json or launcher output you got. Report security problems privately. See
+[SECURITY.md](./SECURITY.md).
+
+## Pull requests
+
+This package lives in [osdlc/osdlc](https://github.com/osdlc/osdlc) under
+`packages/ts/npm-binary`. Open pull requests there. They are reviewed and
+merged there.
+
+## Running the tests
+
+The repository is a pnpm workspace. Install from the repository root, then
+work in the package directory. The tests run on Vitest under Node 22 or
+later. Build first: the workspace packages and the examples resolve each other
+through `dist/`.
+
+```sh
+pnpm install
+cd packages/ts/npm-binary
+pnpm run build
+pnpm test
+```
+
+`pnpm run smoke` runs `tests/smoke.mjs`, a short check of the built package
+under Node. It is not published. `examples/readme.test.ts` installs the
+README's packages in a temporary `node_modules` and runs the launcher with
+Node, so a launcher change is tested end to end on Linux and macOS.
+`pnpm run coverage` reports test coverage.
+
+Other checks:
+
+```sh
+pnpm run typecheck
+pnpm run lint
+pnpm run format:check
+```
+
+## Code style
+
+- TypeScript, ES modules, and explicit `.ts` import paths.
+- Prettier formats the code and oxlint checks it. Run `pnpm run format` and
+  `pnpm run lint` before you commit.
+- Add a test for each behaviour change or bug fix.
+- A new export gets TSDoc and a use in `examples/`, which imports the package
+  by name. A test fails if an export has no example.
+- An experimental export carries `@experimental` and is listed in the
+  README's Stability section. A test checks that the two agree.
+- For a change users can see, add a changeset: run `pnpm changeset` at the
+  repository root. Start a breaking change's summary with `**Breaking:**`.
+  Do not edit `CHANGELOG.md` or `version` by hand; the release writes them.
+  See [packages/README.md](https://github.com/osdlc/osdlc/blob/main/packages/README.md).

package/LICENSE-APACHE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 Sizer LLC
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/LICENSE-MIT

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 SK Sizer
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -1,3 +1,234 @@
-# Temporary Holding Version
+# @osdlc/npm-binary
 
-This version is a temporary placeholder for this package. An operational version to replace this has been submitted for review and is awaiting a staged release.
+Ship a compiled binary through npm the way esbuild and Biome do: one launcher
+package that users install, plus one package per platform. Each platform
+package is gated by `os` and `cpu`, and the launcher lists them all as
+`optionalDependencies`, so npm downloads only the one that matches the host.
+`npx your-tool` and `npm install -g your-tool` then run a native executable,
+with no install script and no download from anywhere but the registry.
+
+## Why
+
+A tool written in Rust, Go, Zig or compiled with `bun build --compile` has
+one executable per platform. Getting it onto a JavaScript developer's machine
+through npm takes the same handful of pieces every time: the platform names,
+two `package.json` shapes, a small Node script that finds and runs the right
+executable, and a publish order that keeps the launcher from pointing at
+packages that do not exist yet. Each piece has edge cases (Windows `.exe`,
+Yarn Plug'n'Play, Ctrl-C delivered twice, a launcher re-raising its child's
+signal). This library holds those pieces, so your release script keeps only
+its build step and its names.
+
+It is for the author of a CLI who already builds the executables, in CI or
+locally, and wants npm as one more channel.
+
+Do not use it when:
+
+- your binary is a Node-API addon (`.node`) loaded with `require`. Use
+  [`@napi-rs/cli`](https://www.npmjs.com/package/@napi-rs/cli), which builds
+  platform packages for addons.
+- you want one tool to own the whole release (versions, tags, every
+  registry). A release orchestrator such as
+  [putitoutthere](https://www.npmjs.com/package/putitoutthere) or
+  [dist](https://github.com/axodotdev/cargo-dist) does that; this library is
+  the npm layout only, called from a script you own.
+- you would rather download the executable from a release page at install
+  time (`binary-install` and similar). That needs install scripts, which many
+  CI setups disable with `--ignore-scripts`; this layout does not.
+
+## Install
+
+```sh
+npm install --save-dev @osdlc/npm-binary
+```
+
+ESM only, Node 22 or later, with types. The launcher it writes is plain
+CommonJS with no dependencies and runs on Node 18 or later on the user's
+machine.
+
+## Use
+
+Your release script builds the binaries, then writes one directory per
+package and publishes them. This writes every package for a tool named
+`tool`, with a stand-in for each platform's build:
+
+```ts
+import { mkdirSync, mkdtempSync, rmSync, writeFileSync } from 'node:fs'
+import { tmpdir } from 'node:os'
+import { join } from 'node:path'
+
+import {
+  type BinaryProduct,
+  binaryPathInPackage,
+  copyExecutable,
+  launcherManifest,
+  NPM_PLATFORMS,
+  platformKey,
+  platformManifest,
+  renderLauncher,
+  writeJson,
+} from '@osdlc/npm-binary'
+
+const product: BinaryProduct = {
+  binary: 'tool', // the command on PATH
+  launcher: '@acme/tool', // the package users install
+  scope: '@acme', // platform packages are @acme/tool-<os>-<cpu>
+  platformPrefix: 'tool',
+  binaryDir: 'bin', // where the binary sits inside a platform package
+}
+const version = '1.0.0'
+const out = mkdtempSync(join(tmpdir(), 'tool-npm-'))
+const built = join(out, 'stand-in') // your build output for each platform
+writeFileSync(built, '#!/bin/sh\necho hello\n')
+
+const platformDirs = NPM_PLATFORMS.map((platform) => {
+  const dir = join(out, platformKey(platform))
+  mkdirSync(join(dir, 'bin'), { recursive: true })
+  writeJson(
+    join(dir, 'package.json'),
+    platformManifest(product, platform, {
+      version,
+      description: `The tool binary for ${platformKey(platform)}.`,
+      // Platform packages are scoped, and npm publishes a new scoped package
+      // as private unless publishConfig.access says public.
+      template: { license: 'MIT', publishConfig: { access: 'public' } },
+    }),
+  )
+  copyExecutable(built, join(dir, binaryPathInPackage(product, platform)))
+  return dir
+})
+
+const launcherDir = join(out, 'tool')
+mkdirSync(join(launcherDir, 'bin'), { recursive: true })
+writeJson(
+  join(launcherDir, 'package.json'),
+  launcherManifest(product, NPM_PLATFORMS, {
+    version,
+    description: 'The tool CLI.',
+    launcherPath: 'bin/tool.js',
+  }),
+)
+writeFileSync(join(launcherDir, 'bin', 'tool.js'), renderLauncher(product, NPM_PLATFORMS))
+
+// Then, logged in to npm:
+// await publishPackages({ platformDirs, launcherDir })
+console.log(`${platformDirs.length} platform packages and the launcher in ${out}`)
+rmSync(out, { recursive: true, force: true })
+```
+
+[`examples/readme.test.ts`](examples/readme.test.ts) installs those packages
+the way npm lays them out and runs the launcher.
+
+## Guide
+
+- [Getting started](docs/guide/getting-started.md): publish a CLI for five
+  platforms, step by step, with the `package.json` files it writes.
+- [How the launcher works](docs/guide/how-the-launcher-works.md): what runs on
+  the user's machine, signals and exit codes.
+- [Troubleshooting](docs/guide/troubleshooting.md): the errors users can hit,
+  their causes and fixes.
+
+## How the launcher behaves
+
+`renderLauncher` returns the launcher script. On the user's machine it finds
+the platform package npm installed for that host, runs its binary with the
+same arguments and the terminal, passes signals through, and exits with the
+binary's exit code. A host with no build, or a missing platform package, gets
+an error that names the cause. Every name is written into the script as a
+JavaScript string literal, so quotes and backslashes in names are safe.
+
+[How the launcher works](docs/guide/how-the-launcher-works.md) has the
+details: the lookup, when Ctrl-C is and is not forwarded, and the exit codes.
+
+## API
+
+Names and platforms:
+
+- `BinaryProduct`: the names one product ships under (`binary`, `launcher`,
+  `scope`, `platformPrefix`, `binaryDir`).
+- `NpmPlatform`: an `os` and a `cpu`, as `process.platform` and
+  `process.arch` name them. Any value Node reports is accepted; `darwin`,
+  `linux`, `win32`, `arm64` and `x64` are named for completion.
+- `NPM_PLATFORMS`: the default list, in publish order: `darwin-arm64`,
+  `darwin-x64`, `linux-x64`, `linux-arm64`, `win32-x64`.
+- `platformKey(platform)`: `darwin-arm64`.
+- `platformPackageName(product, platform)`: `@acme/tool-darwin-arm64`.
+- `binaryExt(platform)`: `.exe` on Windows, empty elsewhere.
+- `binaryFileName(product, platform)`: `tool` or `tool.exe`.
+- `binaryPathInPackage(product, platform)`: `bin/tool`, or `tool` when
+  `binaryDir` is `''`.
+- `findPlatform(platforms, key)`: the entry for a key; throws, naming the
+  known keys, for any other.
+- `hostPlatform(platforms)`: the entry for the machine this runs on.
+
+Package shapes:
+
+- `platformManifest(product, platform, options)`: a platform package's
+  `package.json`, with `os`, `cpu`, `preferUnplugged: true` (so Yarn PnP keeps
+  the binary a real file) and `files` defaulting to the binary (a
+  template's `files` gets the binary added).
+- `launcherManifest(product, platforms, options)`: the launcher's
+  `package.json`, with `bin`, every platform package in
+  `optionalDependencies` at the same version, `files` defaulting to the
+  launcher and `README.md` (a template's `files` gets the launcher added),
+  and `engines.node` defaulting to `>=18`. A launcher template with
+  `"type": "module"` is refused: the launcher is CommonJS.
+- `PlatformManifestOptions` and `LauncherManifestOptions`: `version`,
+  `description`, the launcher's `launcherPath`, and an optional `template`
+  with fields to carry (`license`, `author`, `publishConfig`, ...). Template
+  fields keep their position, and the fields the library sets that the
+  template does not name are appended, so your template controls the key
+  order and the bytes written. `name`, `version` and `description` always
+  come from the arguments; naming them in the template only fixes their
+  position.
+- `Manifest`: a `package.json` as a plain object.
+- `writeJson(path, value)`: two-space JSON with a final newline.
+- `copyExecutable(src, dest)`: copies a file and sets mode `0o755`.
+
+The launcher:
+
+- `renderLauncher(product, platforms, options?)`: the launcher script's
+  source, described above. `LauncherOptions` has `debugEnv`.
+
+Publishing and cargo:
+
+- `publishPackages(options)`: `npm publish` in each platform directory, then
+  the launcher's, with the npm on `PATH` and its login. It asks the registry
+  first and skips every `name@version` already published, so a half-finished
+  run is safe to run again. `PublishOptions` has `platformDirs`,
+  `launcherDir`, `dryRun`, and `viewRunner` and `publishRunner` to replace the
+  `npm` it runs (for tests). It returns a `PublishResult`: the `published` and
+  `skipped` packages as `name@version`.
+- `cargoTargetDir(options)`: cargo's target directory, from
+  `cargo metadata --no-deps`, for a release script that builds with cargo.
+  `CargoTargetDirOptions` has `cwd`, an optional `manifestPath` for a crate
+  outside the workspace at `cwd`, and a `runner` for tests.
+
+## Platforms
+
+The library runs anywhere Node 22 runs. The launcher it writes runs on every
+platform in the list you pass. What it does not do:
+
+- tell glibc from musl. It sets no `libc` field, so one `linux-x64` package
+  installs on glibc and musl (Alpine) hosts alike, and a glibc build fails on
+  Alpine. Ship a static (musl) Linux build.
+- fall back to an emulated build. On Windows on Arm, `process.arch` is `arm64`,
+  so the launcher reports no build unless your list has `win32-arm64`, even
+  though an x64 build would run under emulation.
+- forward SIGHUP on Windows. Node raises it there when the console window
+  closes, and the binary gets that close event itself.
+- forward SIGINT on Windows. The binary gets the console's Ctrl-C itself,
+  and Node's `kill` on Windows is a hard kill rather than a signal.
+
+The tests run on Linux and macOS. The launcher's Windows paths (`.exe`, no
+SIGHUP, no SIGINT forwarding, a signal that cannot be re-raised) are covered
+by unit tests, not by a Windows run.
+
+## Stability
+
+Every export is stable within the 0.x line: a breaking change bumps the minor
+version and is listed in the CHANGELOG. No export is experimental.
+
+## Licence
+
+`MIT OR Apache-2.0`, at your option. See [LICENSE-MIT](./LICENSE-MIT) and [LICENSE-APACHE](./LICENSE-APACHE).

package/SECURITY.md

@@ -0,0 +1,23 @@
+# Security policy
+
+## Reporting a vulnerability
+
+Please report vulnerabilities privately. Do not open a public issue.
+
+Use GitHub private vulnerability reporting on the repository: open the
+[Security tab](https://github.com/osdlc/osdlc/security) and choose
+"Report a vulnerability".
+
+Include the version, a short description, and steps to reproduce. A minimal
+code sample helps.
+
+## Supported versions
+
+Only the latest `0.x` release gets security fixes. The library is pre-1.0, so
+older `0.x` releases are not patched. Upgrade to the latest release.
+
+## What to expect
+
+This is a small project. We aim to reply within a week. We will tell you
+whether we accept the report and keep you updated until a fix is released.
+We will credit you in the release notes if you want that.

package/dist/cargo.d.ts

@@ -0,0 +1,19 @@
+/**
+ * Where cargo writes build output, asked of cargo rather than derived from a
+ * path: workspace membership decides it.
+ */
+import { type CommandRunner } from '@osdlc/command-seam';
+/** Options for {@link cargoTargetDir}. */
+export interface CargoTargetDirOptions {
+    /** The directory cargo runs in. */
+    cwd: string;
+    /** A crate outside the workspace at `cwd` has its own target dir. */
+    manifestPath?: string;
+    /** Runs `cargo`. Defaults to spawning it; a test passes a fake. */
+    runner?: CommandRunner;
+}
+/**
+ * Cargo's target directory, from `cargo metadata --no-deps`. Throws when cargo
+ * fails, or when its output has no `target_directory`.
+ */
+export declare function cargoTargetDir({ cwd, manifestPath, runner, }: CargoTargetDirOptions): string;

package/dist/cargo.js

@@ -0,0 +1,20 @@
+/**
+ * Where cargo writes build output, asked of cargo rather than derived from a
+ * path: workspace membership decides it.
+ */
+import { runChecked, spawnRunner } from '@osdlc/command-seam';
+/**
+ * Cargo's target directory, from `cargo metadata --no-deps`. Throws when cargo
+ * fails, or when its output has no `target_directory`.
+ */
+export function cargoTargetDir({ cwd, manifestPath, runner = spawnRunner('cargo'), }) {
+    const argv = ['metadata', '--no-deps', '--format-version', '1'];
+    if (manifestPath !== undefined)
+        argv.push('--manifest-path', manifestPath);
+    const { stdout } = runChecked(runner, argv, { cwd });
+    const dir = JSON.parse(stdout).target_directory;
+    if (typeof dir !== 'string' || dir === '') {
+        throw new Error('cargo metadata printed no target_directory');
+    }
+    return dir;
+}

package/dist/index.d.ts

@@ -0,0 +1,5 @@
+export * from './cargo.ts';
+export * from './launcher.ts';
+export * from './manifest.ts';
+export * from './platform.ts';
+export * from './publish.ts';

package/dist/index.js

@@ -0,0 +1,5 @@
+export * from "./cargo.js";
+export * from "./launcher.js";
+export * from "./manifest.js";
+export * from "./platform.js";
+export * from "./publish.js";

package/dist/launcher-template.cjs

@@ -0,0 +1,106 @@
+#!/usr/bin/env node
+// Runs the native binary from the platform package npm installed alongside
+// this one. Generated by @osdlc/npm-binary, which replaces each quoted
+// placeholder below with a string literal.
+//
+// It runs on the consumer's machine before any compiled binary is available,
+// so it stays CommonJS and dependency-free.
+'use strict'
+
+const { spawn } = require('node:child_process')
+const fs = require('node:fs')
+const os = require('node:os')
+const path = require('node:path')
+
+const PLATFORM_PACKAGES = JSON.parse('{{platformPackages}}')
+const BINARY = '{{binary}}'
+const LAUNCHER = '{{launcher}}'
+const DEBUG_ENV = '{{debugEnv}}'
+
+function binaryPath() {
+  const key = `${process.platform}-${process.arch}`
+  const target = PLATFORM_PACKAGES[key]
+  if (!target) {
+    throw new Error(
+      `${BINARY} has no build for ${key}. Supported: ${Object.keys(PLATFORM_PACKAGES).join(', ')}.`,
+    )
+  }
+  const { package: pkg, binary: file } = target
+  let bin
+  try {
+    // Through package.json: always resolvable, never blocked by an "exports" map.
+    bin = path.join(path.dirname(require.resolve(`${pkg}/package.json`)), file)
+  } catch {
+    throw new Error(
+      `${BINARY}: the platform package ${pkg} is not installed. ` +
+        `It is an optional dependency of ${LAUNCHER}, so it is skipped when optional dependencies are ` +
+        'turned off (--omit=optional, --no-optional) or when the lockfile was made on another platform. ' +
+        `Reinstall without those, or add ${pkg} directly.`,
+    )
+  }
+  if (!fs.existsSync(bin)) {
+    throw new Error(
+      `${BINARY}: ${pkg} is installed but its binary ${bin} is missing; try reinstalling.`,
+    )
+  }
+  return { bin, pkg }
+}
+
+let bin, pkg
+try {
+  ;({ bin, pkg } = binaryPath())
+} catch (error) {
+  process.stderr.write(`${error.message}\n`)
+  process.exit(1)
+}
+
+if (DEBUG_ENV && process.env[DEBUG_ENV]) {
+  process.stderr.write(
+    `${BINARY} launcher: platform=${process.platform}-${process.arch} package=${pkg} binary=${bin}\n`,
+  )
+}
+
+// Inherited stdio, so the binary owns the terminal. In a terminal, Ctrl-C already
+// reaches the child through its process group, so SIGINT is forwarded only when
+// no standard stream is a terminal; forwarding it too would read as a second
+// Ctrl-C. On Windows the child gets the console's Ctrl-C itself and kill() is a
+// hard kill, so SIGINT is never forwarded there. SIGTERM and SIGHUP (not on
+// Windows) are always forwarded.
+//
+// The handlers go in before the spawn: the child starts running inside spawn(),
+// and a signal that arrived before them would end the launcher and orphan it.
+// A handler runs on a later tick, after spawn() has returned and set `child`.
+const forwardSigint =
+  process.platform !== 'win32' &&
+  ![process.stdin, process.stdout, process.stderr].some((stream) => stream.isTTY === true)
+const signals = ['SIGINT', 'SIGTERM', ...(process.platform === 'win32' ? [] : ['SIGHUP'])]
+let child
+for (const signal of signals) {
+  process.on(signal, () => {
+    if (signal === 'SIGINT' && !forwardSigint) return
+    try {
+      child.kill(signal)
+    } catch {
+      // Child already gone; its exit handler finishes up.
+    }
+  })
+}
+child = spawn(bin, process.argv.slice(2), { stdio: 'inherit' })
+child.on('error', (error) => {
+  process.stderr.write(`${BINARY}: could not run ${bin}: ${error.message}\n`)
+  process.exit(1)
+})
+child.on('exit', (code, signal) => {
+  if (signal) {
+    // Restore default handling so the re-raise ends this process like the child.
+    process.removeAllListeners(signal)
+    try {
+      process.kill(process.pid, signal)
+    } catch {
+      // Not raisable here (Windows); fall through to the exit code.
+    }
+    // A signal Node ignores (SIGPIPE) leaves us running: exit the shell way.
+    process.exit(128 + (os.constants.signals[signal] ?? 0))
+  }
+  process.exit(code ?? 1)
+})

package/dist/launcher.d.ts

@@ -0,0 +1,24 @@
+import { type BinaryProduct, type NpmPlatform } from './platform.ts';
+/** Options for {@link renderLauncher}. */
+export interface LauncherOptions {
+    /**
+     * The name of an environment variable. When it is set to a non-empty value,
+     * the launcher prints the platform, package and binary it resolved to stderr.
+     * Empty (the default) turns the debug line off.
+     */
+    debugEnv?: string;
+}
+/**
+ * The launcher script's source: a dependency-free CommonJS file for the
+ * launcher package's `bin`. On the user's machine it finds the platform package
+ * npm installed for the host, runs its binary with inherited stdio, passes
+ * signals through and exits with the binary's code (or `128 + signal`).
+ *
+ * Every value is written into the script as a JavaScript string literal, so a
+ * name with quotes or backslashes is safe.
+ *
+ * @param product - The names the product ships under.
+ * @param platforms - The platforms the launcher knows. A host outside this list
+ *   gets an error that names the supported ones.
+ */
+export declare function renderLauncher(product: BinaryProduct, platforms: readonly NpmPlatform[], { debugEnv }?: LauncherOptions): string;

package/dist/launcher.js

@@ -0,0 +1,44 @@
+/**
+ * Render the Node launcher shim from `launcher-template.cjs`.
+ */
+import { readFileSync } from 'node:fs';
+import { fileURLToPath } from 'node:url';
+import { binaryPathInPackage, platformKey, platformPackageName, } from "./platform.js";
+const TEMPLATE = fileURLToPath(new URL('./launcher-template.cjs', import.meta.url));
+/**
+ * The launcher script's source: a dependency-free CommonJS file for the
+ * launcher package's `bin`. On the user's machine it finds the platform package
+ * npm installed for the host, runs its binary with inherited stdio, passes
+ * signals through and exits with the binary's code (or `128 + signal`).
+ *
+ * Every value is written into the script as a JavaScript string literal, so a
+ * name with quotes or backslashes is safe.
+ *
+ * @param product - The names the product ships under.
+ * @param platforms - The platforms the launcher knows. A host outside this list
+ *   gets an error that names the supported ones.
+ */
+export function renderLauncher(product, platforms, { debugEnv = '' } = {}) {
+    const values = {
+        platformPackages: JSON.stringify(launcherTable(product, platforms)),
+        binary: product.binary,
+        launcher: product.launcher,
+        debugEnv,
+    };
+    // The template holds each placeholder as a quoted string, `'{{name}}'`, so it
+    // stays valid JavaScript. The whole quoted token becomes a JSON string
+    // literal, which is also a valid JavaScript string literal.
+    return readFileSync(TEMPLATE, 'utf8').replace(/'\{\{(\w+)\}\}'/g, (_, key) => {
+        const value = values[key];
+        if (value === undefined)
+            throw new Error(`launcher template has an unknown placeholder: ${key}`);
+        return JSON.stringify(value);
+    });
+}
+/** The launcher's lookup table: platform key to package and binary path. */
+function launcherTable(product, platforms) {
+    return Object.fromEntries(platforms.map((p) => [
+        platformKey(p),
+        { package: platformPackageName(product, p), binary: binaryPathInPackage(product, p) },
+    ]));
+}

package/dist/manifest.d.ts

@@ -0,0 +1,45 @@
+import { type BinaryProduct, type NpmPlatform } from './platform.ts';
+/** A package.json as a plain object. */
+export type Manifest = Record<string, unknown>;
+/** Options for {@link platformManifest}. */
+export interface PlatformManifestOptions {
+    version: string;
+    description: string;
+    /**
+     * Fields to carry, such as `license`, `author` or `publishConfig`. Each keeps
+     * its position. `name`, `version` and `description` here only fix their
+     * position: their values come from the arguments. The template is copied,
+     * so the result shares no objects with it.
+     */
+    template?: Manifest;
+}
+/**
+ * One platform package's package.json: gated by `os` and `cpu`, so npm
+ * installs it only on a matching host. `files` defaults to the binary alone;
+ * a template's `files` gets the binary added when it lacks it.
+ * `preferUnplugged` keeps the binary a real file under Yarn PnP, so the
+ * launcher can run it.
+ */
+export declare function platformManifest(product: BinaryProduct, platform: NpmPlatform, { version, description, template }: PlatformManifestOptions): Manifest;
+/** Options for {@link launcherManifest}. */
+export interface LauncherManifestOptions {
+    version: string;
+    description: string;
+    /** The launcher script's path inside the package, e.g. `bin/launcher.js`. */
+    launcherPath: string;
+    /** As {@link PlatformManifestOptions.template}. */
+    template?: Manifest;
+}
+/**
+ * The launcher package's package.json. Lists every platform package as an
+ * optional dependency at the same version, built or not. `files` defaults to
+ * the launcher and the README; a template's `files` gets the launcher added
+ * when it lacks it. `engines.node` defaults to `>=18`. The launcher is
+ * CommonJS, so a template with `"type": "module"` is refused unless
+ * `launcherPath` ends in `.cjs`.
+ */
+export declare function launcherManifest(product: BinaryProduct, platforms: readonly NpmPlatform[], { version, description, launcherPath, template }: LauncherManifestOptions): Manifest;
+/** Writes `value` as JSON with two-space indent and a final newline, as npm does. */
+export declare function writeJson(path: string, value: unknown): void;
+/** Copies a binary into a package and marks it executable (mode `0o755`). */
+export declare function copyExecutable(src: string, dest: string): void;

package/dist/manifest.js

@@ -0,0 +1,74 @@
+/**
+ * The package.json of a platform package and of the launcher.
+ *
+ * `template` fields keep the position they have in the template. Fields this
+ * module sets that the template does not name are appended, so a product
+ * controls key order (and with it the bytes written) through its template.
+ */
+import { chmodSync, copyFileSync, writeFileSync } from 'node:fs';
+import { binaryPathInPackage, platformPackageName, } from "./platform.js";
+/**
+ * One platform package's package.json: gated by `os` and `cpu`, so npm
+ * installs it only on a matching host. `files` defaults to the binary alone;
+ * a template's `files` gets the binary added when it lacks it.
+ * `preferUnplugged` keeps the binary a real file under Yarn PnP, so the
+ * launcher can run it.
+ */
+export function platformManifest(product, platform, { version, description, template = {} }) {
+    const m = withIdentity(platformPackageName(product, platform), version, description, template);
+    m.os = [platform.os];
+    m.cpu = [platform.cpu];
+    m.files = withFile(m.files, binaryPathInPackage(product, platform), []);
+    m.preferUnplugged = true;
+    return m;
+}
+/**
+ * The launcher package's package.json. Lists every platform package as an
+ * optional dependency at the same version, built or not. `files` defaults to
+ * the launcher and the README; a template's `files` gets the launcher added
+ * when it lacks it. `engines.node` defaults to `>=18`. The launcher is
+ * CommonJS, so a template with `"type": "module"` is refused unless
+ * `launcherPath` ends in `.cjs`.
+ */
+export function launcherManifest(product, platforms, { version, description, launcherPath, template = {} }) {
+    if (template.type === 'module' && !launcherPath.endsWith('.cjs')) {
+        throw new Error('launcherManifest: the template sets "type": "module", but the launcher is CommonJS; leave "type" out of the launcher template or give launcherPath a .cjs extension');
+    }
+    const m = withIdentity(product.launcher, version, description, template);
+    m.bin = { [product.binary]: launcherPath };
+    m.files = withFile(m.files, launcherPath, ['README.md']);
+    m.optionalDependencies = Object.fromEntries(platforms.map((p) => [platformPackageName(product, p), version]));
+    m.engines ??= { node: '>=18' };
+    return m;
+}
+/**
+ * The template's fields in order, with `name`, `version` and `description`
+ * set from the arguments. An identity field the template names keeps the
+ * template's position; one it does not name goes first.
+ */
+function withIdentity(name, version, description, template) {
+    const identity = { name, version, description };
+    const first = Object.fromEntries(Object.entries(identity).filter(([key]) => !Object.hasOwn(template, key)));
+    return Object.assign(first, structuredClone(template), identity);
+}
+/**
+ * The `files` list with `file` in it: the template's list, plus `file` when no
+ * entry names it or a directory that holds it; or `file` and `rest` when the
+ * template has no list.
+ */
+function withFile(files, file, rest) {
+    if (!Array.isArray(files))
+        return [file, ...rest];
+    const covers = (entry) => typeof entry === 'string' &&
+        (entry === file || file.startsWith(`${entry.replace(/\/+$/, '')}/`));
+    return files.some(covers) ? files : [...files, file];
+}
+/** Writes `value` as JSON with two-space indent and a final newline, as npm does. */
+export function writeJson(path, value) {
+    writeFileSync(path, `${JSON.stringify(value, null, 2)}\n`);
+}
+/** Copies a binary into a package and marks it executable (mode `0o755`). */
+export function copyExecutable(src, dest) {
+    copyFileSync(src, dest);
+    chmodSync(dest, 0o755);
+}

package/dist/platform.d.ts

@@ -0,0 +1,58 @@
+/**
+ * The platforms a binary ships for, and the names derived from them.
+ */
+/**
+ * A platform as npm sees it: an `os` from `process.platform` and a `cpu` from
+ * `process.arch`. The common values are named for completion; any other value
+ * Node reports, such as `freebsd` or `ia32`, is accepted too.
+ */
+export interface NpmPlatform {
+    readonly os: 'darwin' | 'linux' | 'win32' | (string & {});
+    readonly cpu: 'arm64' | 'x64' | (string & {});
+}
+/**
+ * The default platform list, in publish and listing order: macOS on Apple
+ * silicon and Intel, Linux on x64 and arm64, and Windows on x64. Linux
+ * packages carry no `libc` gate, so one Linux build serves glibc and musl
+ * hosts alike: ship a static (musl) build. A product that ships for fewer or
+ * more passes its own list.
+ */
+export declare const NPM_PLATFORMS: readonly NpmPlatform[];
+/** The names one product ships under. */
+export interface BinaryProduct {
+    /** The executable name, on the user's PATH and inside each platform package. */
+    readonly binary: string;
+    /** The launcher package users install. */
+    readonly launcher: string;
+    /** The npm scope platform packages are published under, such as `@acme`. */
+    readonly scope: string;
+    /**
+     * Platform packages are `<scope>/<platformPrefix>-<os>-<cpu>`, such as
+     * `@acme/tool-linux-x64`. With `''` they are `<scope>/<os>-<cpu>`, the way
+     * esbuild names them (`@esbuild/linux-x64`).
+     */
+    readonly platformPrefix: string;
+    /** Directory inside a platform package that holds the binary; `''` is the package root. */
+    readonly binaryDir: string;
+}
+/** `darwin-arm64`: the key a platform goes by in directories and in the launcher. */
+export declare function platformKey(p: NpmPlatform): string;
+/**
+ * `<scope>/<platformPrefix>-<os>-<cpu>`, e.g. `@acme/tool-linux-x64`, or
+ * `<scope>/<os>-<cpu>` when `platformPrefix` is `''`. Throws when `scope` is
+ * not an npm scope.
+ */
+export declare function platformPackageName(product: BinaryProduct, p: NpmPlatform): string;
+/** The executable's extension, with its dot: `.exe` on Windows, empty elsewhere. */
+export declare function binaryExt(p: Pick<NpmPlatform, 'os'>): string;
+/** The executable's file name on that platform: `tool`, or `tool.exe` on Windows. */
+export declare function binaryFileName(product: BinaryProduct, p: Pick<NpmPlatform, 'os'>): string;
+/** The binary's path inside its platform package, `/`-separated. */
+export declare function binaryPathInPackage(product: BinaryProduct, p: Pick<NpmPlatform, 'os'>): string;
+/** The entry in `platforms` whose key is `key`. Throws, naming the known keys, when none is. */
+export declare function findPlatform<P extends NpmPlatform>(platforms: readonly P[], key: string): P;
+/**
+ * The entry for the machine this runs on, from `process.platform` and
+ * `process.arch`. Throws when the host is not in `platforms`.
+ */
+export declare function hostPlatform<P extends NpmPlatform>(platforms: readonly P[]): P;

package/dist/platform.js

@@ -0,0 +1,61 @@
+/**
+ * The platforms a binary ships for, and the names derived from them.
+ */
+/**
+ * The default platform list, in publish and listing order: macOS on Apple
+ * silicon and Intel, Linux on x64 and arm64, and Windows on x64. Linux
+ * packages carry no `libc` gate, so one Linux build serves glibc and musl
+ * hosts alike: ship a static (musl) build. A product that ships for fewer or
+ * more passes its own list.
+ */
+export const NPM_PLATFORMS = [
+    { os: 'darwin', cpu: 'arm64' },
+    { os: 'darwin', cpu: 'x64' },
+    { os: 'linux', cpu: 'x64' },
+    { os: 'linux', cpu: 'arm64' },
+    { os: 'win32', cpu: 'x64' },
+];
+/** `darwin-arm64`: the key a platform goes by in directories and in the launcher. */
+export function platformKey(p) {
+    return `${p.os}-${p.cpu}`;
+}
+/**
+ * `<scope>/<platformPrefix>-<os>-<cpu>`, e.g. `@acme/tool-linux-x64`, or
+ * `<scope>/<os>-<cpu>` when `platformPrefix` is `''`. Throws when `scope` is
+ * not an npm scope.
+ */
+export function platformPackageName(product, p) {
+    if (!/^@[^/@\s]+$/.test(product.scope)) {
+        throw new Error(`scope must be an npm scope such as "@acme", got ${JSON.stringify(product.scope)}`);
+    }
+    const prefix = product.platformPrefix === '' ? '' : `${product.platformPrefix}-`;
+    return `${product.scope}/${prefix}${platformKey(p)}`;
+}
+/** The executable's extension, with its dot: `.exe` on Windows, empty elsewhere. */
+export function binaryExt(p) {
+    return p.os === 'win32' ? '.exe' : '';
+}
+/** The executable's file name on that platform: `tool`, or `tool.exe` on Windows. */
+export function binaryFileName(product, p) {
+    return `${product.binary}${binaryExt(p)}`;
+}
+/** The binary's path inside its platform package, `/`-separated. */
+export function binaryPathInPackage(product, p) {
+    const file = binaryFileName(product, p);
+    return product.binaryDir === '' ? file : `${product.binaryDir}/${file}`;
+}
+/** The entry in `platforms` whose key is `key`. Throws, naming the known keys, when none is. */
+export function findPlatform(platforms, key) {
+    const found = platforms.find((p) => platformKey(p) === key);
+    if (!found) {
+        throw new Error(`unknown platform "${key}"; known: ${platforms.map(platformKey).join(', ')}`);
+    }
+    return found;
+}
+/**
+ * The entry for the machine this runs on, from `process.platform` and
+ * `process.arch`. Throws when the host is not in `platforms`.
+ */
+export function hostPlatform(platforms) {
+    return findPlatform(platforms, `${process.platform}-${process.arch}`);
+}

package/dist/publish.d.ts

@@ -0,0 +1,36 @@
+import { type AsyncCommandRunner, type StreamRunner } from '@osdlc/command-seam';
+/** What {@link publishPackages} did, as `name@version` in publish order. */
+export interface PublishResult {
+    /** Published by this run (or, with `dryRun`, that would be). */
+    published: string[];
+    /** Already on the registry, so not published again. */
+    skipped: string[];
+}
+/** Options for {@link publishPackages}. */
+export interface PublishOptions {
+    /** The platform package directories, each with its package.json. */
+    platformDirs: readonly string[];
+    /** The launcher package directory. Published last. */
+    launcherDir: string;
+    /** Runs `npm publish --dry-run` instead. */
+    dryRun?: boolean;
+    /** Runs `npm view`. Defaults to the `npm` on `PATH`; a test passes a fake. */
+    viewRunner?: AsyncCommandRunner;
+    /**
+     * Runs `npm publish` with npm's output shown live. Defaults to the `npm` on
+     * `PATH`; a test passes a fake.
+     */
+    publishRunner?: StreamRunner;
+}
+/**
+ * Publishes each package with `npm publish` from its directory, the platform
+ * packages in order and the launcher last. It first asks the registry
+ * (`npm view <name>@<version> version`, on the package's
+ * `publishConfig.registry` when it sets one) for every package at once, and
+ * skips the ones already there. Throws before publishing anything when a
+ * lookup fails for any reason but "not found" (E404), and on the first failed
+ * publish. npm uses its own login and each package's `publishConfig`, so set
+ * `publishConfig.tag` to publish a prerelease under a tag other than `latest`.
+ * Returns which packages were published and which were skipped.
+ */
+export declare function publishPackages({ platformDirs, launcherDir, dryRun, viewRunner, publishRunner, }: PublishOptions): Promise<PublishResult>;

package/dist/publish.js

@@ -0,0 +1,51 @@
+/**
+ * Publish a product's packages: platform packages first, the launcher last, so
+ * its optional dependencies already exist on the registry when it lands.
+ * A version the registry already has is skipped, so a half-finished run is
+ * safe to re-run.
+ */
+import { readFileSync } from 'node:fs';
+import { join } from 'node:path';
+import { spawnRunnerAsync, streamRunner, } from '@osdlc/command-seam';
+/**
+ * Publishes each package with `npm publish` from its directory, the platform
+ * packages in order and the launcher last. It first asks the registry
+ * (`npm view <name>@<version> version`, on the package's
+ * `publishConfig.registry` when it sets one) for every package at once, and
+ * skips the ones already there. Throws before publishing anything when a
+ * lookup fails for any reason but "not found" (E404), and on the first failed
+ * publish. npm uses its own login and each package's `publishConfig`, so set
+ * `publishConfig.tag` to publish a prerelease under a tag other than `latest`.
+ * Returns which packages were published and which were skipped.
+ */
+export async function publishPackages({ platformDirs, launcherDir, dryRun = false, viewRunner = spawnRunnerAsync('npm'), publishRunner = streamRunner('npm'), }) {
+    const packages = await Promise.all([...platformDirs, launcherDir].map(async (dir) => {
+        const { name, version, publishConfig } = JSON.parse(readFileSync(join(dir, 'package.json'), 'utf8'));
+        // `npm publish` reads publishConfig.registry; `npm view` does not, so ask the same registry.
+        const registry = publishConfig?.registry;
+        const viewArgv = ['view', `${name}@${version}`, 'version'];
+        if (registry !== undefined)
+            viewArgv.push('--registry', registry);
+        const view = await viewRunner.run(viewArgv, { cwd: dir });
+        // E404 means this version (or the whole package) is not there. Any other
+        // failure, such as no network or no login, leaves it unknown, so stop.
+        if (view.exitCode !== 0 && !view.stderr.includes('E404')) {
+            throw new Error(`npm ${viewArgv.join(' ')} failed in ${dir}: ${view.stderr.trim()}`);
+        }
+        const published = view.exitCode === 0 && view.stdout.trim() === version;
+        return { dir, name, version, published };
+    }));
+    const argv = ['publish', ...(dryRun ? ['--dry-run'] : [])];
+    const result = { published: [], skipped: [] };
+    for (const { dir, name, version, published } of packages) {
+        if (published) {
+            result.skipped.push(`${name}@${version}`);
+            continue;
+        }
+        const run = publishRunner.run(argv, { cwd: dir });
+        if (run.exitCode !== 0)
+            throw new Error(`npm ${argv.join(' ')} failed in ${dir}`);
+        result.published.push(`${name}@${version}`);
+    }
+    return result;
+}

package/package.json

@@ -1,6 +1,73 @@
 {
   "name": "@osdlc/npm-binary",
-  "version": "0.0.0-stage",
-  "stub": true,
-  "description": "Temporary package placeholder for staged publishing"
+  "version": "0.0.1-stage",
+  "description": "Ship a compiled binary through npm: one launcher package plus one os/cpu-gated package per platform, selected through optionalDependencies. Platform names, the two package.json shapes, a dependency-free Node launcher shim, platform-first publishing and the cargo target-dir lookup.",
+  "license": "MIT OR Apache-2.0",
+  "author": "sksizer",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/osdlc/osdlc.git",
+    "directory": "packages/ts/npm-binary"
+  },
+  "homepage": "https://github.com/osdlc/osdlc/tree/main/packages/ts/npm-binary#readme",
+  "bugs": "https://github.com/osdlc/osdlc/issues",
+  "keywords": [
+    "npm",
+    "binary",
+    "native",
+    "optionalDependencies",
+    "platform-packages",
+    "launcher",
+    "cli",
+    "cargo",
+    "rust",
+    "distribution"
+  ],
+  "publishConfig": {
+    "access": "public"
+  },
+  "type": "module",
+  "sideEffects": false,
+  "engines": {
+    "node": ">=22"
+  },
+  "exports": {
+    ".": {
+      "types": "./dist/index.d.ts",
+      "default": "./dist/index.js"
+    }
+  },
+  "files": [
+    "dist/",
+    "README.md",
+    "CHANGELOG.md",
+    "LICENSE-MIT",
+    "LICENSE-APACHE",
+    "SECURITY.md",
+    "CONTRIBUTING.md"
+  ],
+  "dependencies": {
+    "@osdlc/command-seam": "^0.14.0"
+  },
+  "devDependencies": {
+    "@types/node": "^26.1.0",
+    "@vitest/coverage-v8": "^5.0.5",
+    "oxlint": "^1.65.0",
+    "prettier": "3.9.6",
+    "typescript": "~6.0.3",
+    "vitest": "^5.0.5",
+    "@osdlc/tsconfig": "^0.4.1",
+    "@osdlc/prettier-config": "^0.3.1"
+  },
+  "scripts": {
+    "build": "tsc -p tsconfig.build.json && node -e \"require('node:fs').copyFileSync('src/launcher-template.cjs', 'dist/launcher-template.cjs')\"",
+    "clean": "node -e \"require('node:fs').rmSync('dist', { recursive: true, force: true })\"",
+    "test": "vitest run",
+    "coverage": "vitest run --coverage",
+    "smoke": "node tests/smoke.mjs",
+    "format": "prettier --write .",
+    "format:check": "prettier --check .",
+    "lint": "oxlint .",
+    "typecheck": "tsc --noEmit && tsc -p tsconfig.build.json --noEmit"
+  }
 }