WebAssembly with Reference Types cannot be parsed #15566

CryZe · 2022-03-20T19:40:36Z

Reopened #13559

Bug report

WebAssembly modules with enabled Reference Types cannot be loaded. The webpack version I tested this with is 5.38.1

For a minimal reproduction I created this repository: https://github.com/Tarnadas/webpack-5-wasm-reftypes

The error message is the following:

ERROR in ./pkg/webpack_5_wasm_reftypes_bg.wasm
Module parse failed: Internal failure: parseVec could not cast the value
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
Error: Internal failure: parseVec could not cast the value
    at new CompileError (/home/marior/projects/webpack-5-wasm-reftypes/node_modules/@webassemblyjs/helper-api-error/lib/index.js:40:109)
    at parseVec (/home/marior/projects/webpack-5-wasm-reftypes/node_modules/@webassemblyjs/wasm-parser/lib/decoder.js:328:15)
    at parseTypeSection (/home/marior/projects/webpack-5-wasm-reftypes/node_modules/@webassemblyjs/wasm-parser/lib/decoder.js:360:22)
    at parseSection (/home/marior/projects/webpack-5-wasm-reftypes/node_modules/@webassemblyjs/wasm-parser/lib/decoder.js:1363:24)
    at Object.decode (/home/marior/projects/webpack-5-wasm-reftypes/node_modules/@webassemblyjs/wasm-parser/lib/decoder.js:1712:25)
    at decode (/home/marior/projects/webpack-5-wasm-reftypes/node_modules/@webassemblyjs/wasm-parser/lib/index.js:248:21)
    at WebAssemblyParser.parse (/home/marior/projects/webpack-5-wasm-reftypes/node_modules/webpack/lib/wasm-async/AsyncWebAssemblyParser.js:48:19)
    at /home/marior/projects/webpack-5-wasm-reftypes/node_modules/webpack/lib/NormalModule.js:1018:26
    at processResult (/home/marior/projects/webpack-5-wasm-reftypes/node_modules/webpack/lib/NormalModule.js:745:11)
    at /home/marior/projects/webpack-5-wasm-reftypes/node_modules/webpack/lib/NormalModule.js:809:5
 @ ./pkg/webpack_5_wasm_reftypes.js 1:0-58 4:0-21
 @ ./src/index.js 1:0-16

webpack 5.38.1 compiled with 1 error in 572 ms
error Command failed with exit code 1.

I used Rust with wasm-bindgen, which provides a cli option to enable reference types. Instead of directly using wasm-bindgen, I’ve been using wasm-pack, but since it’s unmaintained, you will need my fork to pass the cli option down to wasm-bindgen. You can see my PR for wasm-pack here: rustwasm/wasm-pack#888

By looking at the error message, it seems to be a problem with the wasm parser library. I checked its repository and couldn’t find any mentions about reference types unfortunately, so I’m not sure how to proceed with this.

The text was updated successfully, but these errors were encountered:

vankop · 2022-03-21T08:36:07Z

I think parser does not support them.. (@webassemblyjs/wasm-parser) . Right now there is no workaround for this.

enomado · 2022-03-24T14:44:21Z

Why webpack try to parse it? can we just use file-loader?

vankop · 2022-03-24T15:45:17Z

Why webpack try to parse it?

There are some exports optimization.. so webpack parsing wasm.

can we just use file-loader?

yes, sure. also in webpack@5 there is asset type.

sokra · 2022-04-07T11:11:21Z

@xtuc

webpack-bot · 2022-07-07T13:31:57Z

This issue had no activity for at least three months.

It's subject to automatic issue closing if there is no activity in the next 15 days.

CryZe · 2022-07-07T13:37:04Z

ping

webpack-bot · 2022-10-22T07:11:57Z

Issue was closed because of inactivity.

If you think this is still a valid issue, please file a new issue with additional information.

CryZe · 2022-10-22T10:55:07Z

Last time you at least gave a warning, and it's marked as completed?? This has to be the worst bot ever.

CryZe · 2023-02-06T00:54:40Z

Ok dude

alexander-akait · 2023-06-02T16:49:11Z

@xtuc Friendly ping

alexander-akait · 2024-11-06T20:12:10Z

The same - #18940

xtuc · 2024-11-06T21:07:17Z

Thanks for checking @alexander-akait . I'm having a look.

xtuc · 2024-11-06T21:57:51Z

I published 1.14.1. Could you please try again @alexander-akait ?

Sorry I had some issues with my publish setup.

mateuszJS · 2024-11-06T23:30:14Z

@xtuc Works for me!

    "@webassemblyjs/ast": "^1.14.1",
    "@webassemblyjs/wasm-edit": "^1.14.1",
    "@webassemblyjs/wasm-parser": "^1.14.1",

https://github.com/mateuszJS/rust-webpack-v5-template/tree/webpack-v5-migration
Thank you for great work 👍

stephanemagnenat · 2024-11-07T09:37:41Z

@xtuc works for me as well! Thank you very much!

seeing if this fixes supposed to fix webpack/webpack#15566, appears not to

ivnsch · 2024-12-22T06:23:02Z

I'm still getting the error "Module parse failed: Internal failure: parseVec could not cast the value"

https://github.com/ivnsch/molsimnext

the only way to fix it is still the workaround

[profile.release]
strip = true

alexander-akait · 2024-12-25T15:27:56Z

@ivnsch what version do you use?

Based on webpack/webpack#15566 (comment)

ivnsch · 2025-01-04T06:14:34Z

@ivnsch what version do you use?

Version of webpack? It's a newly created nextjs project (npx create-next-app@latest). The webpack version is hidden for some reason, nowhere to be seen in the lock file, npm explain webpack, npx webpack --version etc. It might be 5.96.1 (it's confirmed that it's using webpack, because the webpack section in next.config.ts is executed).

I also tried specifying these dependencies as per post above:

    "@webassemblyjs/ast": "^1.14.1",
    "@webassemblyjs/wasm-edit": "^1.14.1",
    "@webassemblyjs/wasm-parser": "^1.14.1",

it seems like nextjs is not updating their webpack. So for the time being, doing this will fix the issue webpack/webpack#15566

Webpack was running into webpack/webpack#15566 with the latest @nimiq/core version, but an update fixed it.

j2ghz · 2025-02-03T15:47:14Z

Apart from the @webassemblyjs/* dependencies also check your webpack version. I was on 5.96.1 (latest nextjs), whereas 5.97.0 seems to have the fix:

[WASM] Don't crash WebAssembly with Reference Types (sync and async)
[WASM] Fixed wasm loading for sync and async webassembly

My problem before applying the fix above:

Module parse failed: Internal failure: parseVec could not cast the value
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
Error: Internal failure: parseVec could not cast the value

from my pnpm lockfile:

packages:
  '@webassemblyjs/ast@1.14.1':
    resolution: {integrity: sha512-nuBEDgQfm1ccRp/8bCQrx1frohyufl4JlbMMZ4P1wpeOfDhF6FQkxZJ1b/e+PLwr6X1Nhw6OLme5usuBWYBvuQ==}

  '@webassemblyjs/wasm-edit@1.14.1':
    resolution: {integrity: sha512-RNJUIQH/J8iA/1NzlE4N7KtyZNHi3w7at7hDjvRNm5rcUXa00z1vRz3glZoULfJ5mpvYhLybmVcwcjGrC1pRrQ==}

  '@webassemblyjs/wasm-parser@1.14.1':
    resolution: {integrity: sha512-JLBl+KZ0R5qB7mCnud/yyX08jWFw5MsoalJ1pQ4EdFlgj9VdXKGuENGsiCIjegI1W7p91rUlcB/LB5yRJKNTcQ==}

snapshots:
  webpack@5.96.1:
    dependencies:
      '@types/eslint-scope': 3.7.7
      '@types/estree': 1.0.6
      '@webassemblyjs/ast': 1.14.1
      '@webassemblyjs/wasm-edit': 1.14.1
      '@webassemblyjs/wasm-parser': 1.14.1

Resolves webpack/webpack#15566

Problem: when using rustc > 1.82 and webpack < 5.97.0 the wasm file generated by wasm-bindgen can't be loaded by webpack. This is tracked by an issue [1] in the wasm-bindgen repo and an issue [2] in the webpack repo. This meant that the packaging tests were failing. Solution: upgrade the packaging tests to use webpack 5.99.0. This does mean that people using older versions of webpack will need to upgrade, but it's a patch version upgrade so shouldn't be too disruptive. [1]: rustwasm/wasm-bindgen#4211 [2]: webpack/webpack#15566

vankop added webpack-5 wasm wasm related issues labels Mar 21, 2022

webpack-bot added the inactive label Jul 7, 2022

webpack-bot removed the inactive label Jul 7, 2022

webpack-bot added the inactive label Oct 7, 2022

webpack-bot closed this as completed Oct 22, 2022

alexander-akait reopened this Oct 22, 2022

webpack-bot removed the inactive label Oct 22, 2022

webpack-bot added the inactive label Jan 21, 2023

webpack-bot closed this as completed Feb 6, 2023

alexander-akait reopened this Feb 15, 2023

webpack-bot removed the inactive label Feb 15, 2023

webpack-bot added the inactive label May 18, 2023

webpack-bot closed this as completed Jun 2, 2023

alexander-akait reopened this Jun 2, 2023

webpack-bot removed the inactive label Jun 2, 2023

webpack-bot added the inactive label Sep 2, 2023

webpack-bot closed this as completed Sep 17, 2023

alexander-akait reopened this Dec 19, 2023

webpack-bot removed the inactive label Dec 19, 2023

alexander-akait mentioned this issue Nov 6, 2024

fix: wasm #18940

Merged

alexander-akait closed this as completed in #18940 Nov 7, 2024

daxpedda mentioned this issue Nov 7, 2024

Revert bundler target specific default transformations rustwasm/wasm-bindgen#4253

Merged

mattheson mentioned this issue Nov 15, 2024

add support for .at() in list proxies automerge/automerge#984

Merged

elldritch mentioned this issue Nov 29, 2024

fix: cargo update for Rust 1.80.0 rbtying/shengji#456

Closed

amylase mentioned this issue Dec 8, 2024

make buildable with the latest wasm-bindgen amylase/ffxiv-crafter-rust#30

Open

scsmithr mentioned this issue Dec 9, 2024

wasm-bindgen upgrades and rust reference types GlareDB/glaredb#3350

Closed

davidar added a commit to compute-toys/wgpu-compute-toy that referenced this issue Dec 17, 2024

Workaround for webpack/webpack#15566

64eda6e

ivnsch added a commit to ivnsch/molsimnext that referenced this issue Dec 22, 2024

update deps

2fa7b70

seeing if this fixes supposed to fix webpack/webpack#15566, appears not to

njbrown mentioned this issue Dec 24, 2024

Bump webpack dependency to 5.97.1 to resolve compilation errors on .wasm files with Reference Types enabled. vercel/next.js#74265

Closed

amatveiakin added a commit to amatveiakin/bughouse-chess that referenced this issue Dec 31, 2024

Workaround WebPack parser bug

b68bd0e

Based on webpack/webpack#15566 (comment)

khanghugo added a commit to khanghugo/gchimp that referenced this issue Jan 9, 2025

fix gchimp-web static site compile

e523760

it seems like nextjs is not updating their webpack. So for the time being, doing this will fix the issue webpack/webpack#15566

sisou added a commit to nimiq/wallet that referenced this issue Jan 13, 2025

Update @nimiq/core to v2.0.6 and update Webpack to support it

b04784b

Webpack was running into webpack/webpack#15566 with the latest @nimiq/core version, but an update fixed it.

denis-sh mentioned this issue Feb 16, 2025

webpack fails to parse WASM file generated by Rust 1.82+ rustwasm/rust-webpack-template#191

Open

MikkelPaulson added a commit to initiative-sh/initiative.sh that referenced this issue Apr 5, 2025

upgrade Webpack from 5.94 to 5.98

b0d0642

Resolves webpack/webpack#15566

MikkelPaulson added a commit to initiative-sh/initiative.sh that referenced this issue Apr 6, 2025

upgrade Webpack from 5.94 to 5.98

e7c28ae

Resolves webpack/webpack#15566

MikkelPaulson mentioned this issue Apr 6, 2025

Upgrade wasm-bindgen initiative-sh/initiative.sh#375

Merged

MikkelPaulson added a commit to initiative-sh/initiative.sh that referenced this issue Apr 6, 2025

upgrade Webpack from 5.94 to 5.98

547fe06

Resolves webpack/webpack#15566

alexjg mentioned this issue May 7, 2025

js: Update webpack packaging tests to webpack 5.99.0 automerge/automerge#1025

Merged

Uh oh!

WebAssembly with Reference Types cannot be parsed #15566

WebAssembly with Reference Types cannot be parsed #15566

Comments

CryZe commented Mar 20, 2022

Bug report

vankop commented Mar 21, 2022

Uh oh!

enomado commented Mar 24, 2022

Uh oh!

vankop commented Mar 24, 2022

Uh oh!

sokra commented Apr 7, 2022

Uh oh!

webpack-bot commented Jul 7, 2022

Uh oh!

CryZe commented Jul 7, 2022

Uh oh!

webpack-bot commented Oct 22, 2022

Uh oh!

CryZe commented Oct 22, 2022

Uh oh!

CryZe commented Feb 6, 2023

Uh oh!

alexander-akait commented Jun 2, 2023

Uh oh!

alexander-akait commented Nov 6, 2024

Uh oh!

xtuc commented Nov 6, 2024

Uh oh!

xtuc commented Nov 6, 2024

Uh oh!

mateuszJS commented Nov 6, 2024

Uh oh!

stephanemagnenat commented Nov 7, 2024

Uh oh!

ivnsch commented Dec 22, 2024

Uh oh!

alexander-akait commented Dec 25, 2024

Uh oh!

ivnsch commented Jan 4, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

j2ghz commented Feb 3, 2025

Uh oh!

ivnsch commented Jan 4, 2025 •

edited

Loading