You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm seeing this error and it is confusing. My root tsconfig.json extends @tsconfig/svelte/tsconfig.json, latest version 5.0.8 which is pretty simple:
{
"$schema": "https://www.schemastore.org/tsconfig",
"_version": "5.0.0",
"compilerOptions": {
"module": "esnext",
"moduleResolution": "bundler",
"target": "es2017",
/**Svelte Preprocess cannot figure out whether you have a value or a type, so tell TypeScriptto enforce using `import type` instead of `import` for Types.*/"verbatimModuleSyntax": true,
/**To have warnings/errors of the Svelte compiler at the correct position,enable source maps by default.*/"sourceMap": true,
"strict": true,
"esModuleInterop": true,
"skipLibCheck": true
}
}
but note that it is "bundler" is not "node10" so that's why I'm confused.
packages/common/tsconfig.json(3,3): error TS5107: Option 'moduleResolution=node10' is deprecated and will stop functioning in TypeScript 7.0. Specify compilerOption '"ignoreDeprecations": "6.0"' to silence this error.
when trying to upgrade typescript from 5.9.3 to 6.0.2.
We didn't ask for node10.
I don't have time to try to create a small repro case right now but I wanted to share that Daniel McDonald (@dan-mcdonald) 's problem is not unique.
David de Kloet (@dskloetc) For modern Typescript, you need use node16/nodenext/bundler for moduleResolution, node just an alias for node10, it has deprecated in Typescript 6.0.
In old versions of TypeScript, baseUrl was required in order to use paths. This is no longer the case, and in many projects you can simply remove baseUrl (especially if it's .).
Seeing inconsistent behavior with the baseUrl deprecation warning in TS 6+ in monorepo setups (pnpm + Next.js 16).
Even with:
"ignoreDeprecations": "6.0"
the warning still appears when baseUrl is inherited via extends, especially with moduleResolution: bundler/node16.
Concern:
baseUrl still works at compile/runtime level
diagnostics are inconsistent across config composition
suppression via ignoreDeprecations is not reliable in extended configs
This feels like a partially rolled-out diagnostic deprecation without a clear, enforceable migration path for workspace-scale projects.
Is this intended as an early signal for TS 7, or is the migration strategy still evolving for monorepo use cases?
The closest you can get is to use node16 or bundler, resolvePackageJsonImports and resolvePackageJsonExports, and ensure your own code is using "type": "commonjs" or no "type" at all.
node10 has no concept of the difference between runtime ESM and runtime CJS code, basically assuming that all code in the universe is CJS and that export default foo means ~exports.__esModule = true; exports.default = foo.
bundler has an understanding of what files are ESM and CJS but assumes it will all interop nicely. It also respects package.json "exports" and "imports" by default, and even when it knows a file is ESM, it supports directory modules and extension searching, like Node.js’s CJS resolution algorithm.
node16 treats ESM like ESM and CJS like CJS, according to how Node.js 16 identifies and treats ESM and CJS.
There is of course a maintenance cost to being able to model the modules support of an infinite range of Node.js versions within a single version of TypeScript. We think dropping node10 from our list of algorithms we continue to maintain at this point is reasonably conservative, but it shouldn't impact your ability to support users with old Node.js. You probably test your code against old Node.js versions. You can also test your types against old versions of TypeScript.
In latest node, all code in the universe is CJS (or, is ESM), because they're basically indistinguishable.
Testing against multiple versions of TS is prohibitively hard; TS 6 doesn't even work with the syntax in @types/node below like v8.
I'll go with bundler but considering that https://npmjs.com/resolve@next already models every single possible permutation of node's resolution algorithms, and the work is done for you, i think the maintenance cost is pretty close to zero.
xr0master no, it's just not supported. even if it was actually dead (no usage), equivalent browsers are still VERY MUCH in use, and these browsers should be delivered type-checked code too.
Activity
jakebailey commentedon Oct 31, 2025
Dinesh0729 commentedon Oct 31, 2025
Update the tsconfig for eventual TS 6.0 changes.
Update the tsconfig for eventual TS 6.0 changes. (#585)
sujansince2003 commentedon Nov 10, 2025
change module resolution to bundler and it will be resolved.also some packages might give some errors make sure to resolve those.
"moduleResolution": "node10",to"moduleResolution": "bundler",chore: add oxlint, rust (and go) based linter for integration-tests
chore: add oxlint, rust (and go) based linter for integration-tests
chore: add oxlint, rust (and go) based linter for integration-tests
chore: add oxlint, rust (and go) based linter for integration-tests (#…
build: ensure tsconfig is compatible with upcoming typescript changes
tsconfig: Remove baseUrl
tsconfig: Remove baseUrl
Specify rootDir to address 6.0 compatibility
Specify rootDir to address 6.0 compatibility
chore(repo): typescript compilation updates
chore(deps): update dependency typescript to v6 (#367)
dan-mcdonald commentedon Mar 25, 2026
Option 'moduleResolution=node10' is deprecated
I'm seeing this error and it is confusing. My root tsconfig.json extends @tsconfig/svelte/tsconfig.json, latest version 5.0.8 which is pretty simple:
{ "$schema": "https://www.schemastore.org/tsconfig", "_version": "5.0.0", "compilerOptions": { "module": "esnext", "moduleResolution": "bundler", "target": "es2017", /** Svelte Preprocess cannot figure out whether you have a value or a type, so tell TypeScript to enforce using `import type` instead of `import` for Types. */ "verbatimModuleSyntax": true, /** To have warnings/errors of the Svelte compiler at the correct position, enable source maps by default. */ "sourceMap": true, "strict": true, "esModuleInterop": true, "skipLibCheck": true } }but note that it is "bundler" is not "node10" so that's why I'm confused.
RyanCavanaugh commentedon Mar 25, 2026
Daniel McDonald (@dan-mcdonald) please log a new issue with a complete repro. Thanks!
fix: [issue](https://github.com/microsoft/TypeScript/issues/62508#iss…
fix: get rid of deprecated baseUrl param (can just remove it)
dskloetc commentedon Mar 30, 2026
My issue is similar to Daniel McDonald (@dan-mcdonald)'s. I have
but it gives
when trying to upgrade typescript from 5.9.3 to 6.0.2.
We didn't ask for
node10.I don't have time to try to create a small repro case right now but I wanted to share that Daniel McDonald (@dan-mcdonald) 's problem is not unique.
cscnk52 commentedon Mar 30, 2026
David de Kloet (@dskloetc) For modern Typescript, you need use
node16/nodenext/bundlerformoduleResolution,nodejust an alias fornode10, it has deprecated in Typescript 6.0.See docs for more information.
dskloetc commentedon Mar 30, 2026
Cason Kervis (@cscnk52) thanks for the information. That's very helpful!
It would have been useful if the error message had said that though :).
remove deprecated compilerOptions.baseUrl
remove deprecated compilerOptions.baseUrl
Bump typescript from 5.9.3 to 6.0.2 (#446)
Match behaviour change
chore: remove deprecated tsconfig props
chore: prep tsconfig files for TypeScript 6 compatibility
chore: prep tsconfig files for TypeScript 6 compatibility (#905)
fix: remove baseUrl
fix(deps): update dependency typescript to v6 (#424)
fix: Remove compiler option baseUrl from tsconfig
fix(none): rm deprecated `baseUrl` in ts config
fix(tsconfig.app.json): removed deprecated baseUrl
fix(tsconfig.app.json): removed deprecated baseUrl
Quitamos baseURL, https://github.com/microsoft/TypeScript/issues/62508
Kimxons commentedon Apr 11, 2026
This works okay.
chore: ts migration
chore(deps): update dependency typescript to v6 (#3363)
chore(deps): update dependency typescript to v6 (#3363)
chore(deps): update dependency typescript to v6 (#3363)
chore(deps): update dependency typescript to v6 (#3363)
chore(deps): update dependency typescript to v6 (#3363)
chore(deps): update dependency typescript to v6 (#3363)
chore(deps): update dependency typescript to v6 (#3363)
chore(deps): update dependency typescript to v6 (#3363)
chore(deps): update dependency typescript to v6 (#3363)
chore(deps): update dependency typescript to v6 (#3363)
chore(deps): update dependency typescript to v6 (#3363)
chore(deps): update dependency typescript to v6 (#3363)
chore(deps): update dependency typescript to v6 (#3363)
chore(deps): update dependency typescript to v6 (#3363)
chore(deps): update dependency typescript to v6 (#3363)
chore(deps): update dependency typescript to v6 (#3363)
chore(deps): update dependency typescript to v6 (#3363)
chore(deps): update dependency typescript to v6 (#3363)
chore(deps): update dependency typescript to v6 (#3363)
chore(deps): update dependency typescript to v6 (#3363)
chore(deps): update dependency typescript to v6 (#3363)
fix(ts): adapt to TypeScript 6 stricter module resolution
chore(deps-dev): bump typescript from 5.9.3 to 6.0.3 (#297)
fix(frontend): VSCodeでのJest関連のエラーが表示されている問題に対応。
fix(frontend): テスト実行時に失敗する問題に対応
Remove `baseUrl` option
linnbenton commentedon Apr 28, 2026
Seeing inconsistent behavior with the baseUrl deprecation warning in TS 6+ in monorepo setups (pnpm + Next.js 16).
Even with:
"ignoreDeprecations": "6.0"
the warning still appears when baseUrl is inherited via extends, especially with moduleResolution: bundler/node16.
Concern:
baseUrl still works at compile/runtime level
diagnostics are inconsistent across config composition
suppression via ignoreDeprecations is not reliable in extended configs
This feels like a partially rolled-out diagnostic deprecation without a clear, enforceable migration path for workspace-scale projects.
Is this intended as an early signal for TS 7, or is the migration strategy still evolving for monorepo use cases?
fix: remove deprecated baseUrl from tsconfig files
Upgrade `typescript` to version 6.0.3
build(deps): bump `@arcgis` deps (#14403)
非推奨のオプションを削除。
Update typescript to version 6
build: migrate tsconfig to TS6
sahin52 commentedon Jun 18, 2026
This is not mentioned, but the default value of "strict" has become
true#63087
#62333
sahin52 commentedon Jun 18, 2026
Also various other changes can be found in the milestone: https://github.com/microsoft/TypeScript/milestone/218?closed=1
ljharb commentedon Jul 2, 2026
I still want node10 semantics (i don't care what the defaults are). How can I keep them in TS 7+?
jakebailey commentedon Jul 2, 2026
You cannot, except to switch to
bundler.ljharb commentedon Jul 2, 2026
Jake Bailey (@jakebailey) what's the difference between bundler and node10?
and why remove it? people who want to support old nodes can't use types anymore?
andrewbranch commentedon Jul 3, 2026
The closest you can get is to use
node16orbundler,resolvePackageJsonImportsandresolvePackageJsonExports, and ensure your own code is using"type": "commonjs"or no"type"at all.node10has no concept of the difference between runtime ESM and runtime CJS code, basically assuming that all code in the universe is CJS and thatexport default foomeans ~exports.__esModule = true; exports.default = foo.bundlerhas an understanding of what files are ESM and CJS but assumes it will all interop nicely. It also respects package.json"exports"and"imports"by default, and even when it knows a file is ESM, it supports directory modules and extension searching, like Node.js’s CJS resolution algorithm.node16treats ESM like ESM and CJS like CJS, according to how Node.js 16 identifies and treats ESM and CJS.There is of course a maintenance cost to being able to model the modules support of an infinite range of Node.js versions within a single version of TypeScript. We think dropping
node10from our list of algorithms we continue to maintain at this point is reasonably conservative, but it shouldn't impact your ability to support users with old Node.js. You probably test your code against old Node.js versions. You can also test your types against old versions of TypeScript.ljharb commentedon Jul 3, 2026
In latest node, all code in the universe is CJS (or, is ESM), because they're basically indistinguishable.
Testing against multiple versions of TS is prohibitively hard; TS 6 doesn't even work with the syntax in @types/node below like v8.
I'll go with
bundlerbut considering that https://npmjs.com/resolve@nextalready models every single possible permutation of node's resolution algorithms, and the work is done for you, i think the maintenance cost is pretty close to zero.xr0master commentedon Jul 20, 2026
Jordan Harband (@ljharb) the node 10 is dead, officially dead a long time ago. It is better for you to update your code than to ask libraries to support legacy versions. IMHO
https://nodejs.org/en/about/previous-releases
ljharb commentedon Sep 30, 2026
xr0master no, it's just not supported. even if it was actually dead (no usage), equivalent browsers are still VERY MUCH in use, and these browsers should be delivered type-checked code too.