Skip to content

docs: separate a missing Android build from a missing compiler - #379

Merged
rmyndharis merged 1 commit into
mainfrom
docs/npm-prebuilt-binaries
Aug 24, 2026
Merged

rmyndharis merged 1 commit into
mainfrom
docs/npm-prebuilt-binaries

Conversation

@rmyndharis

Copy link
Copy Markdown
Owner

The guide covered only packages that fail for want of a compiler. A package whose installer picks a prebuilt binary by platform name fails differently: it names a platform it does not recognise, and "use a pure JS alternative" is not the answer.

Reported in #375, where npm install stopped at workerd, whose installer carries a fixed list of platform keys with no Android entry. Cloudflare publishes no Android build, so nothing on the device changes it.

  • A Known Limitations section for it, with the workaround that installs the rest of the tree.
  • A bullet under npm Install Fails pointing at it, beside the node-gyp one.
  • It also says Rollup and esbuild do publish Android builds and install normally, so the section is not read as covering every native package. Verified against both packages on the registry.

Docs only. No code paths touched.

The guide covered only packages that need node-gyp, so a package whose
installer picks a prebuilt binary by platform name had no entry: its
message names a platform rather than a compiler, and no pure JS
alternative is the answer. Names what still works, so the reader does not
read it as every native package.
@rmyndharis
rmyndharis merged commit a039e69 into main Aug 24, 2026
3 checks passed
@rmyndharis
rmyndharis deleted the docs/npm-prebuilt-binaries branch August 24, 2026 13:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant