Skip to content

feat: publish @minigraf/browser to npm, rename pkg/ and swift/ for naming consistency - #179

Merged
adityamukho merged 12 commits into
mainfrom
wasm-npm-publish
May 1, 2026
Merged

adityamukho merged 12 commits into
mainfrom
wasm-npm-publish

Conversation

@adityamukho

Copy link
Copy Markdown
Collaborator

Summary

  • Renames pkg/ → minigraf-wasm/ and swift/ → minigraf-swift/ for uniform minigraf-* top-level package folder naming (consistent with minigraf-node/ and minigraf-c/)
  • Deletes minigraf-wasm/.gitignore (was wasm-pack's default *); minigraf-wasm/ is now a committed source directory
  • Updates minigraf-wasm/package.json name to @minigraf/browser
  • Adds publish-npm job to wasm-release.yml — publishes @minigraf/browser to npm on every tagged release; GitHub Release tarball is retained for CDN/direct-download consumers
  • Updates all path references in CI workflows, Package.swift, examples/browser/, and living docs
  • Fixes shell injection in version-stamp step (uses env: + process.env.VERSION instead of interpolating tag into JS source)

Test plan

  • wasm-browser.yml CI passes on this PR (build + headless browser tests)
  • mobile.yml CI passes (Swift path references updated correctly)
  • No pkg/ or swift/ path references remain in CI workflows or living docs
  • After merge and tag: verify @minigraf/browser appears on npm

🤖 Generated with Claude Code

@adityamukho
adityamukho merged commit be69c96 into main May 1, 2026
35 checks passed
@adityamukho
adityamukho deleted the wasm-npm-publish branch May 1, 2026 12:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant