next.js: NextJS 14 forced to use swc and cannot switch to babel anymore.

Link to the code that reproduces this issue

https://github.com/BanDroid/next-swc-android-issue

To Reproduce

  1. create-next-app in termux.
  2. run dev.
  3. create .babelrc/babel.config.js and use presets “next/babel”.

Current vs. Expected behavior

SWC does support Android arm64, but somehow swc in nextjs cannot support it, i always switch to babel for workaround, but now i cant switch to use babel.

Verify canary release

  • I verified that the issue exists in the latest Next.js canary release

Provide environment information

Operating System:
  Platform: android
  Arch: arm64
  Version: #1 SMP PREEMPT Fri Jul 29 23:55:04 CST 2022
Binaries:
  Node: 18.16.1
  npm: 9.5.1
  Yarn: 1.22.19
  pnpm: 8.8.0
Relevant Packages:
  next: 14.0.0
  eslint-config-next: 14.0.0
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.2.2
Next.js Config:
  output: N/A

Which area(s) are affected? (Select all that apply)

CLI (create-next-app), Operating System (Windows, MacOS, Linux), Package manager (npm, pnpm, Yarn), SWC minifier (swcMinify: true), SWC transpilation

Additional context

fyi, i use termux to code. last version i tested fine was next 13.4

About this issue

  • Original URL
  • State: closed
  • Created 8 months ago
  • Reactions: 3
  • Comments: 30 (6 by maintainers)

Most upvoted comments

We’ve reintroduced WASM fallback for SWC (and enabled it by default in web containers).

@jridgewell fix confirmed. 🚀 🎉

retracted… it was a fluke 😢 sorry for the false confirmation

@jridgewell fix confirmed. 🚀 🎉