5 ms·
It looks like the team has already considered this in one regard > There is already a precedent for something that Node.js support, that can be upgraded sepera
by madeofpalk 2y ago
It looks like the team has already considered this in one regard
> There is already a precedent for something that Node.js support, that can be upgraded seperately, its NPM.
Node bundles a version of npm that can upgraded separately, we could do the same with our TypeScript transpiler.
> We could create a package that we bundle but that can also be downloaded from NPM, keep a stable version in core, but if TypeScript releases new features that we don't support or breaking changes, or users want to use the new shiny experimental feature, they can upgrade it separately.
This ensures that users are not locked, but also provides support for a TypeScript version for the whole 3 years of the lifetime of Node.js release.
https://github.com/nodejs/loaders/issues/217 https://github.com/nodejs/loaders/issues/217
- SomeCallMeTim 2y agoAs long as Node understands to use the project-specific version of TypeScript (i.e., the one in node_modules or the PNP equivalent), that should be fine. But it would be a step backward to need to globally upgrade TypeScript (as you do with npm), since some older projects will not be compatible with newer versions of TypeScript. Ask me how I know. ;)
- silverwind 2y ago> As long as Node understands to use the project-specific version of TypeScript It won't, but in such a scenario, typescript would only be a type checker, wich is a entirely different endeavor than running typescript.
- madeofpalk 2y agoI think Node’s strategy here is to not let perfect be the enemy of useful for some people.
- nilsbunger 2y agoAt first I thought that's not a big deal, I could manage that with `nvm`. But I think you're right, you really want it to pick up the project-specific typescript so that you're using ONE version of typescript for type checking, execution, and more.