Walkthrough

The wasm crate was relocated from wasm/lib/ to crates/wasm/. References were updated: workspace members in Cargo.toml, the CI clippy manifest path in .github/workflows/ci.yaml, and webpack aliases / WasmPackPlugin crateDirectory in the wasm demo and notebook webpack configs.

Changes

Sequence Diagram(s)

(omitted — changes are path updates and do not modify runtime control flow)

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

• Verify crates/wasm/Cargo.toml exists and is correct.
• Search repository for any remaining wasm/lib references (build scripts, docs, package.json).
• Run the wasm demo and notebook webpack builds to confirm aliasing and WasmPackPlugin paths resolve.

Possibly related PRs

• move derive-impl -> crates/derive-impl #6263 — similar workspace relocation of a crate into crates/* and corresponding Cargo.toml updates.
• Move vm/sre_engine -> crates/sre_engine #6265 — updates workspace crate paths from previous subdirectories to crates/* layout and adjusts related configs.

Suggested reviewers

• youknowone

Poem

🐰 I hopped the paths and nudged the maps,

Crates moved home with tidy wraps.
CI and demo chase the trail,
Small changes, forward sail.
A carrot cheer for every commit! 🥕

Pre-merge checks and finishing touches

Learnt from: reactive-firewall
Repo: RustPython/RustPython PR: 6176
File: .github/workflows/Check_Tests.yml:133-141
Timestamp: 2025-09-28T22:22:55.921Z
Learning: In the RustPython project's CI-5974-Test-RustPython-Integration action, the override-rustpython-path input is marked as required but has runtime fallback logic that defaults to RUSTPYTHONPATH environment variable or "Lib" if neither is provided, making explicit specification unnecessary in most cases.

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

_{Comment @coderabbitai help to get the list of available commands and usage tips.}