chore: use @next/swc for transpiling files

[SukkaW]

Bug

• Related issues linked using fixes #number
• Integration tests added
• Errors have helpful link attached, see contributing.md

Feature

• Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR.
• Related issues linked using fixes #number
• Integration tests added
• Documentation added
• Telemetry added. In case of a feature if it's used or not.
• Errors have helpful link attached, see contributing.md

Documentation / Examples

• Make sure the linting passes by running pnpm lint
• The examples guidelines are followed from our contributing doc

[SukkaW]

@ijjk

Here is my attempt to use @next/swc for precompiling. Here are the problems I currently encounter and my thoughts:

• packages/next/build/swc/index.js can not be re-used:
  • It is written in ES Module format, which has to be pre-compiled before use
  • It is dependent on the pre-compiled version of @napi-rs/triple
  • We don't need swc load error telemetry
  • We need to load "@next/swc-[platform]" directly from node_modules,
    skipping @next/swc/natives/next-swc.[platform].node
• @next/swc has a very primitive gSP and gSSP check, which can cause pre-compile to fail:
  • This can be fixed easily though.
    https://github.com/vercel/next.js/blob/46710101695a9f78482b6e03f161eb11361b9a26/packages/next/build/webpack/loaders/next-serverless-loader/page-handler.ts#L73-L75

• @next/swc-* is published alongside Next.js. If there is a bug in @next/swc causing pre-compiled files to corrupt, and we accidentally release a defected version of Next.js, we can not fix pre-compiled files with the latest @next/swc-* without publishing another new version of Next.js.
  • If we still use @swc/core, we can update @swc/core separately, without bumping the version of @next/swc-*
• When @vercel/ncc switches to swc-loader, it will also require @swc/core to be installed as a devDependency anyway.