V3.1 release

[ngxson]

V3.1 release with WebGPU support and single-build

Summary by CodeRabbit

• New Features

  • WebGPU support now automatically enabled by default in v3.1 with GPU layer offloading for improved performance
  • Added configuration parameter to control GPU layer offloading behavior, allowing performance fine-tuning

• Documentation

  • Updated release documentation and README with WebGPU availability details and configuration examples

[coderabbitai]

📝 Walkthrough

Walkthrough

Version 3.1.0 release update with documentation of WebGPU support. WASM CDN asset mapping key refactored from 'wllama.wasm' to 'default'. Package version bumped, generator script and output regenerated. README and V3.1 guide clarify automatic WebGPU enablement with GPU layer control via n_gpu_layers parameter.

Changes

V3.1 Release

Layer / File(s)	Summary
Version Bump package.json	Package version updated from 3.0.0 to 3.1.0.
WASM Asset Configuration scripts/generate_wasm_from_cdn.js, src/wasm-from-cdn.ts	WASM CDN mapping key changed from 'wllama.wasm' to default; generated file updated with @wllama/wllama@3.1.0 version reference.
WebGPU Documentation README.md, guides/intro-v3.1.md	Features list now explicitly includes WebGPU support; WIP caveat removed. New WebGPU section documents automatic enabling in V3.1, default GPU-layer offloading, and manual control via n_gpu_layers in LoadModelParams with configuration example.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• ngxson/wllama#216: Related WASM asset key change from 'wllama.wasm' to 'default' in both generator and generated mapping files.

Poem

🐰 Version three-point-one takes flight,
WebGPU shines so bright!
WASM keys refined with grace,
GPU layers find their place.
Docs now dance, the tale complete—
A speedy release, quick and neat!

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'V3.1 release' is vague and generic, using only version number without specifying the main changes (WebGPU support and single-build).	Consider using a more descriptive title such as 'V3.1 release: add WebGPU support and single-build approach' to clearly convey the primary changes.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch xsn/readme_wgpu

---

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

[coderabbitai]

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@README.md`:
- Around line 68-70: The README’s WebGPU section claims automatic enabling in
V3.1 but omits browser/flag limitations; add a one-line caveat after the
sentence about automatic enabling noting that WebGPU depends on browser/OS
support and may require enabling experimental flags (e.g., Chrome://flags or
Safari Technology Preview) or GPU drivers, and that behavior can vary by
platform; reference the existing WebGPU paragraph and the parameters mentioned
(n_gpu_layers, LoadModelParams) so readers see the note in context.

In `@scripts/generate_wasm_from_cdn.js`:
- Around line 12-14: WasmFromCDN currently only exports a default key which
breaks consumers expecting the previous 'wllama.wasm' property; update the
generated object (WasmFromCDN) to include both keys — keep the existing
'wllama.wasm' entry mapped to the CDN URL and also provide a 'default' entry
(both pointing to the same template URL using ${version}) so older consumers and
new imports remain compatible.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 7dc712b9-29f6-42e1-8285-5fbdf3c7e4cd

📥 Commits

Reviewing files that changed from the base of the PR and between f3d904c and 36b6503.

📒 Files selected for processing (5)

• README.md
• guides/intro-v3.1.md
• package.json
• scripts/generate_wasm_from_cdn.js
• src/wasm-from-cdn.ts