@next react-scripts(webpack.config.js) to resolve `.wasm` extension?

I was curious if there was any reason .wasm extension was left out from resolve.extensions list?

Webpack also default to include .wasm.

It’d be nice to start using/experimenting wasm from create-react-app!

[dlech]

From what I have seen in other discussions, it seems like the create-react-app philosophy is to ignore the fact that it uses webpack internally - in other words, webpack features should not be relied upon. However, webpack includes a match for .wasm in defaultRules which does not magically work for all .wasm files.

For example, when using a .wasm file created with Emscripten (https://github.com/webpack/webpack/issues/7352) in a create-react-app project, we get the error:

Failed to compile.

./src/sagas/mpy-cross.wasm
Module parse failed: magic header not detected
File was processed with these loaders:
* ./node_modules/file-loader/dist/cjs.js
You may need an additional loader to handle the result of these loaders.
Error: magic header not detected

So it would be nice if create-create-react app could disable this default rule in webpack so users can handle .wasm files however they like without webpack interfering.

As a workaround, I changed the file extension of the .wasm file to .emcwasm so that webpack just treated it like a normal binary file instead of trying to load it as a JavaScript module. (And had to configure the web server to serve .emcwasm files with the application/wasm MIME type.)

[alojzmilicevic]

Is there no way of making it work by overriding config in config-overrides?