TypeScript 4.7 is now out, bringing ✅ Support for ES modules in Node.js ✅ Improved inference and narrowing ✅ More powerful conditional types ✅ Go to Source Definition ✅ Smarter Organize Imports and more! Try it out today! devblogs.microsoft.com/typescript/ann…
@typescript Amazing release! The long-awaited package.json exports field and ECMAScript support in Node.js are finally here! I’m so happy, keep it up.
@typescript > Note that the "types" condition should always come first in "exports". Could anyone explain why the order of fields in an object is important? I understand that in JS fields inside the object are presented in the order of inserting, but why? 🤔
@typescript @atcb @atcb the smarter organise imports are good but it’s annoying you can’t have the removing unused imports without the reordering. It’s like 2 features glued together. Any chance of decoupling them? github.com/microsoft/Type…
@typescript That's great! So now, for ESM support, can anyone tell me how to get rid of "An import path cannot end with a .ts extention" error in VSCode?
@typescript “We have to write import "./foo.js" instead of import "./foo” But why? This can be and should be covered by tcs.
