Does @parcel/rust require an on client-side build?

[ThomasZeman]

Hi folks,

I am implicitly using @parcel/rust/browser.js (via @parcel/utils via @parcel/runtime-service-worker and probably in a browser environment) which fails to build/run with the following error:

  >  9 |   input = input ?? new URL('parcel_node_bindings.wasm', import.meta.url);
  >    |                            ^^^^^^^^^^^^^^^^^^^^^^^^^^^
    10 |   const {instance} = await WebAssembly.instantiateStreaming(fetch(input), {
    11 |     env: {

@parcel/resolver-default: Cannot load file './parcel_node_bindings.wasm' in './node_modules/@parcel/rust'.

This is a major headscratcher for me because this file is missing in the npm package ( https://www.npmjs.com/package/@parcel/rust?activeTab=code ) has never been part of it so this would have never worked. It seems to get generated in the package by calling wasm:build-release but that requires cargo/rust.

Does anyone know how this works?