Closed as not planned
Description
Is there an existing issue for this?
- I have checked for existing issues https://github.com/getsentry/sentry-javascript/issues
- I have reviewed the documentation https://docs.sentry.io/
- I am using the latest SDK release https://github.com/getsentry/sentry-javascript/releases
How do you use Sentry?
Sentry Saas (sentry.io)
Which package are you using?
@sentry/nextjs
SDK Version
7.24.1
Framework Version
Nextjs v12.3.1
Link to Sentry event
No response
Steps to Reproduce
I'm using Rive for animations, and in order to not download their runtime (wasm) from the CDN, I use the following article methodology. The gist of it is the following webpack config in next.config
:
module.exports = {
webpack: (config, options) => {
config.module.rules.push({
test: /\.wasm$/,
use: ['url-loader'],
});
return config;
},
};
When I updated sentry to the latest version (7.24.1) next build
gives the following error:
web:build: Failed to compile.
web:build:
web:build: ./node_modules/@rive-app/canvas/rive.wasm
web:build: Module parse failed: Unexpected character '' (1:0)
web:build: The module seem to be a WebAssembly module, but module is not flagged as WebAssembly module for webpack.
web:build: BREAKING CHANGE: Since webpack 5 WebAssembly is not enabled by default and flagged as experimental feature.
web:build: You need to enable one of the WebAssembly experiments via 'experiments.asyncWebAssembly: true' (based on async modules) or 'experiments.syncWebAssembly: true' (like webpack 4, deprecated).
web:build: For files that transpile to WebAssembly, make sure to set the module type in the 'module.rules' section of the config (e. g. 'type: "webassembly/async"').
web:build: (Source code omitted for this binary file)
Since everything worked as expected with 7.16.0, I downgraded back and there was no build error. I am not able to further narrow down the version in which this error appears atm.
Expected Result
Sentry shouldn't mess with the rest of my build process, the url-loader for the Rive runtime shouldn't error in the build.
Actual Result
No build error.