new-log-viewer: Upgrade to TypeScript 5.6.2; Update module resolution to "Bundler" in tsconfig.json to support new TypeScript. #67
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.
References
new-log-viewer series: #45 #46 #48 #51 #52 #53 #54 #55 #56 #59 #60 #61 #62 #63 #66
It was found that after removing
package-lock.json
and re-runningnpm i
, now npm resolves TypeScript's version to a newer one which has a different module resolution behaviour with"moduleResolution": "NodeNext"
intsconfig.json
.Imports from sources without file extensions no longer work. e.g.,
Release 5.6 Changelog:
https://devblogs.microsoft.com/typescript/announcing-typescript-5-6/#respecting-file-extensions-and-package.json-from-within-node_modules14
Docs:
https://www.typescriptlang.org/tsconfig/#moduleResolution
Discussions:
microsoft/TypeScript#51714
Description
package.json
.tsconfig.json
.Validation performed