René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Design Meeting Notes, 1/11/2023","articleBody":"# Incorrectly Formatted Packages in `--moduleResolution bundler/node16`\r\n\r\nhttps://github.com/microsoft/TypeScript/pull/51973\r\n\r\n* Test to see what breaks if `node` is redirected to `bundler`.\r\n* Previously `types` would have been resolved.\r\n    * Now the `exports.import` condition is resolved as per Node 16 rules.\r\n* Now providing a better error message when we can detect this. You'd get the same error in `node16`.\r\n    * The messages are still bad because we provide an absolute path to the file instead of a relative path.\r\n    * Presumably we did this because the relative path isn't the correct thing when printing paths in the command line.\r\n* Aside: would be good to do the same tests for redirecting `node16`/`nodenext`\r\n\r\n# LKG versus `node_modules`\r\n\r\n* ESLint relies on `node_modules`, our builds rely on LKG builds in `lib`.\r\n* Would be nice if they could agree with each other!\r\n* Would also be nice to get rid of `lib` and use npm for boostrapping.\r\n    * But then people can't clone TypeScript and just run from `lib`.\r\n    * But we could just do that on `release` branches anyway.\r\n* Not great to snapshot 40MB of JS on every LKG!\r\n    * Git doesn't store that as a diff!\r\n    * Cloning takes a while these days\r\n        * Though there are ways to make this easier: https://github.blog/2020-12-21-get-up-to-speed-with-partial-clone-and-shallow-clone/\r\n* So switch to nightlies on npm instead of building from `lib`?\r\n    * Have to always `npm ci` on `git pull`\r\n    * Technically true today, but it's rare that that even makes a difference. So you can get away with it.\r\n    * But it would also be rare for us too. How often do we update LKG?\r\n    * EXCEPT you still need to when you're bisecting!\r\n        * Ugh - annoying. But might be worth it long term.\r\n* Edge case - ESLint looks at the current package `typescript/` instead of the `typescript/node_modules/typescript`.\r\n    * Follow up on if this is true.\r\n* So\r\n    * Switch to using npm and `node_modules`\r\n    * Delete `lib`\r\n    * `lib` gets `.gitignore`'d\r\n    * We force-add `lib` on `release-X.Y` branches and commit it.\r\n    * `lib` gets published on npm.\r\n    * When we need to take advantage of a new feature sooner than the same day, we can publish an insiders or early nightly instead.","author":{"url":"https://github.com/DanielRosenwasser","@type":"Person","name":"DanielRosenwasser"},"datePublished":"2023-01-11T22:48:21.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/52199/TypeScript/issues/52199"}