Brooke Holmes

Both are for socket.io, why would you want to use both?

@sokra I believe you originally made the change for this in 445dba12b4e3fa063bb862aae1f4fefa8f4f466a, is it expected that the `webassemblyModuleFilename` will no longer pull from the real directory?

As per #29485, I'm actually not sure this is `wasm-pack`'s (or `wasm-bindgen`'s fault). I'm seeing this behaviour with just importing the vanilla `.wasm` file when building the Next.js application for...

I believe it is #22697 that's causing this conflict. On a production build with webpack 5 the output configuration is as follows: ``` { publicPath: '/_next/', path: '/Users/sam/Desktop/with-webassembly-app/.next/server/chunks', filename: '../[name].js',...

@gthb Lord forgive me, but I've created a workaround: ```js // next.config.js module.exports = { webpack(config, { isServer, dev }) { // Enable webassembly config.experiments = { asyncWebAssembly: true };...

The above workaround breaks when using `experiments.layers = true` because even though the module ID is named, a chunk hash is still appended to the output assets. The only way...

@icyJoseph is it breaking when you try and deploy it on Vercel? The snippet is working for me in Next 12 for both dev and prod build _locally_. However on...

@icyJoseph What happens if you remove the WasmPackPlugin? I don't think they're interoperable

@icyJoseph I filed this issue about a week ago (https://github.com/vercel/nft/issues/247) but I'm afraid I haven't yet the chance to work on a reproduction or PR for it (as I don't...

(p.s. you don't need the following by the way, I posted my patch hastily and forgot to remove this part from my own Next.js config:) ```js config.module.rules.push({ test: /\.svg$/, use:...