René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Design Meeting Notes, 8/30/2024","articleBody":"# Adding Compile-Caching Entry Points\n\n#59720\n\n* Node.js now supports V8 compilation caching.\n    * Recent PR to Node.js to add `module.enableCompilerCache()`.\n    * Previously were ways to do this with 3rd party packages on npm.\n* Node.js doesn't do this by default, but things like ts-node does on supported versions of Node.js.\n* What's the downside?\n    * You need to have `require` to make this work, awkward for ESM.\n    * This is being worked on.\n* tsc and tsserver start up about 2.3x faster.\n* For executables this is a no-brainer. We can actually use `import()` there too.\n* For libraries, questionable. So the PR doesn't do it.\n* The PR must introduce a new entry point for the library. Is this worth the perf improvement?\n    * Yes.\n    * Just add a comment telling people what's going on and it's fine.\n* Another risk - in development we recompile over and over, and that can pollute the cache.\n    * The files are pretty small - not a huge risk.\n    * We can add `hereby clear-node-cache`.\n* Not going to be immediate - Node-specific work would need to be back-ported in in Node.js 22; otherwise only noticeable in Node 23+.","author":{"url":"https://github.com/DanielRosenwasser","@type":"Person","name":"DanielRosenwasser"},"datePublished":"2024-08-30T18:26:19.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/59809/TypeScript/issues/59809"}