Repository navigation
docs(node): update minimum Node.js version to 20.19.0 - #19317
Merged
andreiborza merged 1 commit intoSep 22, 2026
Merged
andreiborza merged 1 commit into
andreiborza merged 1 commit into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
nicohrubec
force-pushed
the
nicolashrubec/sdk-1461-update-nodejs-minimum-version-in-docs
branch
2 times, most recently
from
September 10, 2026 13:29
154e3e0 to
46b6a33
Compare
JPeer264
approved these changes
Sep 11, 2026
6 tasks
JPeer264
approved these changes
Sep 11, 2026
JPeer264
added a commit
that referenced
this pull request
Sep 22, 2026
## DESCRIBE YOUR PR closes SDK-1494 (kept the version v18 ranges as they ill be removed here: #19317) Bring the Node install pages in line with the v11 install methods, and fix the ESM snippets that stop the app from starting. - Fix the extensionless `import "./instrument"` in the Express, Fastify, Hapi and Connect ESM tabs, in `install/esm-without-import.mdx` and in the NestJS ESM page. The config step creates `instrument.mjs`, and Node ESM does not probe extensions, so the app stopped with `ERR_MODULE_NOT_FOUND`. - Start the Koa ESM tab with `--import` instead. With the extension fixed the app starts, but `koa` is already loaded when `Sentry.init` runs, so every router and middleware span and every route name is lost. - Rewrite `install/late-initialization.mdx` around `node --import @sentry/node/import`. The page told readers to use `@sentry/node/preload`, which is no longer exported and fails with `ERR_PACKAGE_PATH_NOT_EXPORTED`. Drop `SENTRY_PRELOAD_INTEGRATIONS` with it, and show a CommonJS entry point next to the ESM one, since `--import` covers both. - Rework `install/index.mdx` around the three v11 methods: `--import` your instrument file, a bundler plugin with a top-level import, and `--import` the SDK with a later `Sentry.init()`. Say that `--import` covers CommonJS as well, and that `--require` is gone. - Rewrite `install/esm-without-import.mdx` around the bundler plugin and the deferred entry point, and say why a top-level import alone is not equivalent to `--import`. - Remove the `registerEsmLoaderHooks` troubleshooting from `install/esm.mdx`. The option was removed and the SDK no longer depends on `import-in-the-middle`. ## IS YOUR CHANGE URGENT? Help us prioritize incoming PRs by letting us know when the change needs to go live. Select exactly one option. For deadlines, replace `YYYY-MM-DD` with the due date. You can update this information later by editing the PR description. - [ ] Urgent deadline (GA date, etc.): YYYY-MM-DD - [ ] Other deadline: YYYY-MM-DD - [ ] No deadline: Not urgent, can wait up to 1 week+ ## SLA - Teamwork makes the dream work, so please add a reviewer to your PRs. - Please give the docs team up to 1 week to review your PR unless you've supplied a deadline. Thanks in advance for your help! ## PRE-MERGE CHECKLIST _Make sure you've checked the following before merging your changes:_ - [ ] Checked Vercel preview for correctness, including links - [ ] PR was reviewed and approved by any necessary SMEs (subject matter experts) - [ ] PR was reviewed and approved by a member of the [Sentry docs team](https://github.com/orgs/getsentry/teams/docs) ## LEGAL BOILERPLATE <!-- Sentry employees and contractors can delete or ignore this section. --> Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms. ## EXTRA RESOURCES - [Sentry Docs contributor guide](https://docs.sentry.io/contributing/) Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
andreiborza
marked this pull request as ready for review
September 22, 2026 13:17
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
andreiborza
force-pushed
the
nicolashrubec/sdk-1461-update-nodejs-minimum-version-in-docs
branch
from
September 22, 2026 13:34
46b6a33 to
cd1dde7
Compare
andreiborza
deleted the
nicolashrubec/sdk-1461-update-nodejs-minimum-version-in-docs
branch
September 22, 2026 13:37
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
DESCRIBE YOUR PR
Set the Node.js minimum to 20.19.0 for v11 across the docs: reword the prerequisites with the full supported range, drop the now-moot "only available for Node v18.19.0 onwards" ESM notes (the minimum already guarantees them), and bump the stale Node-18 minimums on the Nitro and Elysia guides.
IS YOUR CHANGE URGENT?
Help us prioritize incoming PRs by letting us know when the change needs to go live.
Select exactly one option. For deadlines, replace
YYYY-MM-DDwith the due date. You can update this information later by editing the PR description.SLA
Thanks in advance for your help!
PRE-MERGE CHECKLIST
Make sure you've checked the following before merging your changes:
🤖 Generated with Claude Code