perf: hoist regex patterns

[GalacticHypernova]

Description

Hoisting regex patterns from loops/hot code paths provides both better performance and better memory efficiency, both of which are especially invaluable for resource-constrained environments.

By reusing the hoisted pattern, the engine doesn't need to waste time on recompiling the pattern, thus performing better, and doesn't need to waste resources on local object creation and GC cycles, thus being more efficient.

The benchmark and memory profiling (of the benchmark) is taken from nuxt/nuxt#29620
Each part was ran separately to prevent any sort of inline cache from altering the results

const version = "1.0.0-1.0a"
console.time("inline")
for (let i=0;i<100000;i++){
  version.replace(/-\d+\.[0-9a-f]+/, '')
}
console.timeEnd("inline")

const SEMANTIC_VERSION_RE = /-\d+\.[0-9a-f]+/
console.time("external")
for (let i=0;i<100000;i++){
  version.replace(SEMANTIC_VERSION_RE, '')
}
console.timeEnd("external")

Results:

Browser:

Node:

It also shows a 50% decrease in memory usage in this simple benchmark alone, and has been tested using a memory profiler:

[GalacticHypernova]

@patak-dev Hey! Apologies for the mention, but I wanted to ask which areas you'd like me to leave as is? I see some possible changes in create-vite, rollup.config.ts, and other, "normal" files in packages, and wanted to make sure what is off limits, if anything.

[patak-dev]

This one looks good to me, thanks! If you see other similar changes, you can send other PRs to review them separatedly.

[GalacticHypernova]

Can I combine them all in here so it could be merged at once? I found many places that can benefit from it, just wanted to know if any parts are not to be altered before I accidentally alter them

[patak-dev]

Ya, that is ok too. Thanks!

[jaskp]

Nice 👍 I'm curious about how much it affects large builds. Peak memory usage reduction would be awesome