Why browser.js is not platform specific?
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.5k
- Forks
- 52
- Avg merge
- 13h 37m
- Merged PRs (30d)
- 19
Description
I use @node.rs/crc32 as a dependency in Pixi.js AssetPack. The whole app crashes as in @node-rs/crc32 node package in browser.js there's
export * from '@node-rs/crc32-wasm32-wasi'
But any package manager installs platform specific binary. Even if I try to install @node-rs/crc32-wasm32-wasi by hand it crashes as it's not compatible.
I have Apple Arm64.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting the @node-rs/crc32 package's browser.js entry point and how its platform-specific packages are selected for Apple Arm64. Reproduce the crash through the Pixi.js AssetPack setup, then verify that the browser import resolves to a compatible package without breaking other platforms.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, rust, wasm
- Domain
- backend, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100