Simplified installation? More clear?

[TaggartMaher]

Is there anyone who can help me set this up?
I copied the exact configuration, can't figure this out.

  feature `edition2024` is required

  The package requires the Cargo feature called `edition2024`, but that feature is not stabilized in this version of Cargo (1.82.0-nightly (257b72b8a 2024-07-30)).

rust-toolchain.tml

[toolchain]
# If you change this, adjust the toolchain elsewhere accordingly.
channel = "nightly-2024-08-02"
components = ["rust-src"]
targets = ["wasm32-unknown-unknown"]
profile = "minimal"

I run build:wasm-mt

  "scripts": {
    "build:wasm-st": "wasm-pack build --target web",
    "build:wasm-mt": "cross-env RUSTFLAGS=\"-C target-feature=+atomics,+bulk-memory\" wasm-pack build --target web --out-dir pkg-parallel -- --features parallel -Z build-std=panic_abort,std",

[RReverser]

channel = "nightly-2024-08-02"

Try bumping to latest nightly. The provided version is more like a guidance as one we know works, but the general idea is you can set latest nightly, verify it works for your app, and then pin to whatever that version was.

[TaggartMaher]

Thanks,
I should mention. I did try this, I have tried a couple "random" nightly builds. All have same issue:

[wasm-validator error in module] unexpected false: shared memory requires threads [--enable-threads], on
memory
[wasm-validator error in module] unexpected false: nonzero segment flags require bulk memory [--enable-bulk-memory], on

These errors spit out (hundreds) when I run the webpack build, I'm running it from npm run as shown above.
I also tried placing these arguments into configs as instructed in the readme, and directly in a command without npm, same errors.

The final error at the end is this:

[...pkg-parallel/my-package/my_package]_bg.wasm-opt.wasm" "-O"
To disable `wasm-opt`, add `wasm-opt = false` to your package metadata in your `Cargo.toml`.

(run with channel = "nightly-2025-06-27" )

[RReverser]

That's odd, the RUSTFLAGS should enable features it's complaining about. Does building the demos / tests in this project (wasm-bindgen-rayon itself) work for you? It does on CI...

[TaggartMaher]

Yeah, that's why I was stuck. wasn't sure why it's' not getting these flags.

Okay, I built the demo, it successfully compiles. Couldn't run it in browser, I can get single thread (mandelbrow ST renders fine), multi thread isn't loading. maybe something silly wrong with my javascript?
npm run build
npx serve dist

Just has a "greyed out" button for the multi thread. the web assembly is there, Got this error in js console chrome
Uncaught TypeError: Failed to resolve module specifier "wasm-feature-detect". Relative references must start with either "/", "./", or "../".

not sure if it's relevant. But i assume that's something with the way im serving it, maybe the permission headers aren't setup right.
Either way, i copied these configurations from the demo into my project, and had those weird errors.