dimforge / dimforge/rapier

npm version number desynced?

Open
#997 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Rust
Stars
5.7k
Forks
387
Avg merge
4d 23h
Merged PRs (30d)
6

Description

Hi!

I'm not sure if this is on purpose or not, but now that you moved the typescript build into this repo and cut a new release I was surprised that the latest npm package version was 0.20.0 instead of 0.35.2 like the rust crate.

Is the wasm build now the same version as the rust crate, or are they actually still offset?

Also the JavaScript user guide https://rapier.rs/docs/user_guides/javascript/getting_started_js still says 0.17?

Contributor guide

Open the contributing guide

Research direction

Start with the JavaScript getting-started guide at https://rapier.rs/docs/user_guides/javascript/getting_started_js and compare its stated 0.17 version with the npm 0.20.0 package and Rust crate 0.35.2 mentioned in the issue. Confirm the intended version relationship for the TypeScript/WASM build; done means the release versions and guide are consistent or the offset is explicitly documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, rust, typescript, wasm
Domain
build-system, documentation, release
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.