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
Edge case - ESLint looks at the current package typescript/ instead of the typescript/node_modules/typescript.
Just to clarify, this was only observed when I was testing "type": "module" with export maps on our own package, since it's a self import at that point, but then I couldn't repro it live in the meeting, so... IDK
Incorrectly Formatted Packages in
--moduleResolution bundler/node16#51973
nodeis redirected tobundler.typeswould have been resolved.exports.importcondition is resolved as per Node 16 rules.node16.node16/nodenextLKG versus
node_modulesnode_modules, our builds rely on LKG builds inlib.liband use npm for boostrapping.lib.releasebranches anyway.lib?npm ciongit pulltypescript/instead of thetypescript/node_modules/typescript.node_modulesliblibgets.gitignore'dlibonrelease-X.Ybranches and commit it.libgets published on npm.