Repository navigation
package.json diagnostics in --module nodenext #46861
Description
Activity
If you want
typesto be the first condition I suggest to update the 4.5 beta blog posts like https://devblogs.microsoft.com/typescript/announcing-typescript-4-5-beta/ which contain the, according to you, wrong order (typesis last in theexportsmap example)I think we fixed that for the RC/stable post, Daniel Rosenwasser (@DanielRosenwasser) is it worth going back to that?
Let's discuss this at an upcoming design meeting.
In #46334, it became clear that it’s very easy to mess up writing export maps that will work correctly with
--module nodenext. We would like to explore issuing diagnostics in package.json files in two scenarios (only innode12andnodenext):typescondition is not the first condition in an export mapdefaultcondition is not the last condition in an export mapVS Code currently doesn’t synchronize unsaved changes to package.json files to TS Server (same as tsconfig.json files), so sending errors to the editor can only be done after a manual save. After getting the diagnostics in tsc, we’ll have to evaluate whether the experience in the editor is acceptable, or if we need to start syncing live changes to TS Server.