Bump webpack dependency to 5.97.1 to resolve compilation errors on .wasm files with Reference Types enabled.

[njbrown]

Link to the code that reproduces this issue

https://github.com/njbrown/next-ferrostar

To Reproduce

1. Clone repo
2. run yarn to install deps
3. run yarn dev

Current vs. Expected behavior

Current Behavior:

Webpack is unable to parse .wasm embedded in the @stadiamaps/ferrostar package.

Expected Behavior:
A map should be displayed on the page.

Provide environment information

Operating System:
  Platform: linux
  Arch: x64
  Version: #115-Ubuntu SMP Mon Apr 15 09:52:04 UTC 2024
  Available memory (MB): 40069
  Available CPU cores: 8
Binaries:
  Node: 18.19.1
  npm: 10.2.4
  Yarn: 1.22.22
  pnpm: 9.0.6
Relevant Packages:
  next: 15.1.2 // Latest available version is detected (15.1.2).
  eslint-config-next: 15.1.2
  react: 19.1.0-canary-ef979d47-20241218
  react-dom: 19.1.0-canary-ef979d47-20241218
  typescript: 5.7.2
Next.js Config:
  output: N/A

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

Developer Experience, Webpack

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

next dev (local), next build (local), next start (local)

Additional context

This happens because of a bug in a dependency (@webassemblyjs/wasm-parser:1.12.1) in the current webpack version (webpack:5.96.1). This has since been fixed in webpack:5.97.1 because they have updated the dependency @webassemblyjs/wasm-parser:1.14.1 .

references:
webpack/webpack#15566 (comment)
webpack/webpack#15566 (comment)

[Jazzpirate]

seconded. This makes next.js impossible to use with wasm as e.g. produced by rust/wasm-pack etc.

[abchugh]

This is only blocker that is stopping us to use nextJS for our eLearning portal. Would highly appreciate if this gets fixed sson (seems to be a super easy fix).

[ashi009]

Q: How long will it take to make this one line change?
A: 2mo and counting

[r34son]

Q: How long will it take to make this one line change?
A: 2mo and counting

Open pr then

[ashi009]

@r34son yeah, I was going to.

Following this lovely dev guide, and run into pnpm/pnpm#9029. Now should I go fix their bugs?

[github-actions]

This closed issue has been automatically locked because it had no new activity for 2 weeks. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.