fix(misc): update @types/node to v20.19.9 to support fetch API #32092
+33
−33
Conversation
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
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
ndcunningham
force-pushed
the
fix/update-types-node-fetch-support
branch
from
b47b5ec to
9751941
Compare
|
View your CI Pipeline Execution ↗ for commit 812c6fe
☁️ Nx Cloud last updated this comment at |
![graphite-app[bot]](http://www.gproxx.com/https://avatars.githubusercontent.com/in/158384?s=60&v=4){kind=small}
packages/nx/src/plugins/js/lock-file/__fixtures__/pnpm-semver-range-specifier/pnpm-lock.yaml.ts
Outdated
Show resolved
Hide resolved
ndcunningham
force-pushed
the
fix/update-types-node-fetch-support
branch
from
9751941 to
d4c9f8e
Compare
|
Fixes #29714 too |
Coly010
approved these changes
Aug 18, 2025
- Update @types/node from 18.16.9 to 20.19.9 across all packages - Resolves "fetch is undefined" TypeScript errors in NestJS projects - Aligns with Nx's base Node.js 20.19.0 support requirement Fixes #31637
Co-authored-by: graphite-app[bot] <96075541+graphite-app[bot]@users.noreply.github.com>
leosvelperez
approved these changes
Aug 18, 2025
Coly010
force-pushed
the
fix/update-types-node-fetch-support
branch
from
7da119a to
812c6fe
Compare
✅ Deploy Preview for nx-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
FrozenPandaz
pushed a commit
that referenced
this pull request
Aug 22, 2025
## Current Behavior Nx currently installs an outdated `@types/node` version (18.16.9) which lacks TypeScript definitions for the native `fetch` API introduced in Node.js 18. This causes "fetch is undefined" TypeScript errors in NestJS projects and other Node.js applications when using webpack transformers or other build tools. ## Expected Behavior The `fetch` API should be properly typed in TypeScript without requiring additional type packages or workarounds. Users should be able to use the native fetch API in Node.js applications without TypeScript compilation errors. ## Related Issue(s) Fixes #31637 Fixes #29714 --------- Co-authored-by: graphite-app[bot] <96075541+graphite-app[bot]@users.noreply.github.com> Co-authored-by: Colum Ferry <cferry09@gmail.com> (cherry picked from commit 6ce1061)
|
This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Current Behavior
Nx currently installs an outdated
@types/nodeversion (18.16.9) which lacks TypeScript definitions for the nativefetchAPI introduced in Node.js 18. This causes "fetch is undefined" TypeScript errors in NestJS projects and other Node.js applications when using webpack transformers or other build tools.Expected Behavior
The
fetchAPI should be properly typed in TypeScript without requiring additional type packages or workarounds. Users should be able to use the native fetch API in Node.js applications without TypeScript compilation errors.Related Issue(s)
Fixes #31637
Fixes #29714