build: Build with Rolldown

[timfish]

Bonuses

• Rollup v2 no longer in our deps
• The full CI build is 33% faster
• Even with TypeScript still building declarations, the build step 2x faster

This PR:

• Migrates away from Rollup + plugins to Rolldown
• Removes a load of files that are no longer required
• Simplifies the build configurations
• Prebuild script writes the LIB_VERSION to a file so we don't have to replace it at build time
• Changes CI so that the packages are built once and artifacts are shared to the downstream jobs
  • This is required because Rolldown won't run on the ancient Node versions we test
  • It's much faster to copy the artifacts than to run the build in every job

[github-actions]

Semver Impact of This PR

🟢 Patch (bug fixes)

📋 Changelog Preview

This is how your changes will appear in the changelog.
Entries from this PR are highlighted with a left border (blockquote style).

---

New Features ✨

• Webpack no longer uses unplugin by timfish in #870

Bug Fixes 🐛

• (webpack) Deduplicate webpack deploys by chargome in #875

Internal Changes 🔧

• Build with Rolldown by timfish in #872

• Migrate to oxfmt by timfish in #880
• Build with Rolldown by timfish in #872
• Remove unplugin by timfish in #876
• Rollup/Vite no longer uses unplugin by timfish in #858
• Esbuild no longer uses unplugin by timfish in #871

---

_{🤖 This preview updates automatically when you update the PR.}

[JPeer264]

q: Are there any downsides to upgrade to v22 here? In the JS SDK we use v20, and I'm not sure if we can upgrade that easily (maybe we can)

[timfish]

I can't see any downside! We just have to be aware that every CI job that doesn't override the Node version will use this.

[JPeer264]

Also for the record. I'm fine with a RC of rolldown being in here. If there are no issues with it ofc - but I'm not a pro in rolldown either :)

[s1gr1d]

Looks good, I just want to mention this issue here as we could use those filters now: #749

[sentry]

Bug: The Rollup config for bundler-plugin-core doesn't mark Node.js built-in modules as external, which will cause them to be incorrectly bundled and lead to runtime errors.
_{Severity: HIGH}

Suggested Fix

Update the external array in packages/bundler-plugin-core/rollup.config.mjs to include Node.js built-in modules. Change external: Object.keys(packageJson.dependencies) to external: [...Object.keys(packageJson.dependencies), ...modulePackage.builtinModules]. This will correctly mark the built-ins as external, preventing them from being bundled.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: packages/bundler-plugin-core/rollup.config.mjs#L1

Potential issue: The `rollup.config.mjs` for `bundler-plugin-core` fails to list Node.js
built-in modules like `fs`, `os`, `path`, and `crypto` in its `external` configuration.
The package's source code uses these modules. Consequently, Rollup will attempt to
bundle these built-ins instead of treating them as external dependencies. This will lead
to runtime errors when the distributed bundle is consumed by other tools, as the
references to these Node.js modules will not be resolved correctly.

[timfish]

Total rubbish, Rolldown handles this with the node platform. Here is the build output:

[timfish]

I just want to mention this issue here as we could use those filters now: #749

I'm hoping to get more integration tests in place before I tackle this. We don't even test Rolldown yet!