Skip to content

docs: Node compatibility rewrite, version A (walkthrough)#3244

Draft
bartlomieju wants to merge 1 commit into
mainfrom
docs/node-rewrite-a-walkthrough
Draft

docs: Node compatibility rewrite, version A (walkthrough)#3244
bartlomieju wants to merge 1 commit into
mainfrom
docs/node-rewrite-a-walkthrough

Conversation

@bartlomieju

Copy link
Copy Markdown
Member

One of three competing ground-up rewrites of the Node compatibility page,
opened as drafts for side-by-side review; only one will merge. This version
threads a single "health report" script through the entire page: it picks up
an npm package, a node: built-in, and the process global, moves into
package.json and deno task, hits a legacy CommonJS helper, and ends with a
Node-API addon (duckdb). Every failure a reader would hit is triggered for
real and shown with Deno's actual error text and the fix: the bare-import
hint, the missing-deno-install error, require-is-not-defined, and the
ignored-build-scripts to --allow-scripts flow. All snippets were executed on
Deno 2.8 before being documented; the private-registries section, linked
anchors, and oldUrl redirects are unchanged from the fact-checked baseline
in #3241. Compare with version B (lookup) and version C (task recipes).

@bartlomieju

Copy link
Copy Markdown
Member Author

Siblings for comparison: version B is #3245, version C is #3246.

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