Snippets are missing in wasm_bindgen output

[rharink]

Hi, I'm generating wasm bindings via rust_wasm_bindgen for a web target.

Everything compiles as expected, the .js and .d.ts files are generated, but the snippets directory is missing from the output. The snippets are required by the generatged .jsfile.

When I manually execute the wasm-bindgen-cli command (extracted via bazel build --subcommands) and I change the --out-dir I see the snippets being generated.

How can I copy these to the final output dir, is this a bug? Or am I missing something?

[tomjakubowski]

I encountered this issue when upgrading from rules_rust 0.27 to 0.44.

On 0.27, our rust_wasm_bindgen() rule was outputting a snippets directory:

prospective/prospective-main › bazel cquery --output files //crates/client/unoptimized:prospective_client 2>/dev/null
bazel-out/darwin_arm64-fastbuild/bin/crates/client/unoptimized/prospective_client/prospective_client_bg.wasm
bazel-out/darwin_arm64-fastbuild/bin/crates/client/unoptimized/prospective_client/prospective_client.js
bazel-out/darwin_arm64-fastbuild/bin/crates/client/unoptimized/prospective_client/snippets
bazel-out/darwin_arm64-fastbuild/bin/crates/client/unoptimized/prospective_client/prospective_client.d.ts

On 0.44, it is not:

prospective/prospective › bazel cquery --output files //crates/client/unoptimized:prospective_client 2>/dev/null
bazel-out/darwin_arm64-fastbuild/bin/crates/client/unoptimized/prospective_client.js
bazel-out/darwin_arm64-fastbuild/bin/crates/client/unoptimized/prospective_client.d.ts
bazel-out/darwin_arm64-fastbuild/bin/crates/client/unoptimized/prospective_client_bg.wasm

while the generated .js is still referencing them:

prospective/prospective › head -n 1 bazel-out/darwin_arm64-fastbuild/bin/crates/client/unoptimized/prospective_client.js
import { ClipboardItem } from './snippets/perspective-a2bb7cf7e9a6eee6/inline0.js';

rule:

rust_wasm_bindgen(
    name = "prospective_client",
    tags = ["manual"],
    target = "web",
    wasm_file = "//crates/client:prospective_client_rlib",
)

[tomjakubowski]

Hid my previous comment - we had some patches to work around this issue which I had disabled as part of the upgrade.