rulake-wasm npm republish — sync to v2.3

Open Beginner friendly
#4 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
65/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
javascript, rust, wasm
Domain
build-system, release

Research direction

Start with node-wasm/Cargo.toml, package.json, and build.sh, then confirm the root rulake version and the iter 51 build fix. Update the package metadata, run the node-wasm build, and verify the published version with npm view rulake-wasm version; completion depends on the chosen alpha or stable target.

Written by the indexing model from the issue text.

Description

Root rulake bumped to 2.3.0-alpha.1 in iter 49 (ADR-157). rulake-wasm package.json is still 2.2.1.

Steps

  1. Bump node-wasm/Cargo.toml + package.json to 2.3.0-alpha.1 (or wait for v2.3 stable)
  2. cd node-wasm && ./build.sh (builds web/, nodejs/, pkg-bundler/ correctly per iter 51 fix)
  3. cd node-wasm && npm publish --access=public
  4. Verify: npm view rulake-wasm version
Dominant language
Rust
Stars
16
Forks
9
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ruvnet/RuLake

All issues in ruvnet/RuLake

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.