build: support npm/yarn/pnpm + Changesets publishing#150
Merged
Conversation
Make the monorepo installable with any package manager and set up npm publishing for @learn6502/6502 via Changesets. - Drop the `workspace:` protocol: internal deps now use plain `^0.7.0` ranges. npm and classic yarn can't resolve `workspace:` (only berry/pnpm/gjsify can); plain ranges work with ALL of npm/yarn/pnpm/gjsify, which every PM symlinks to the local workspace. - Changesets: version-locked `fixed` group for all @learn6502/*; bumps the internal ^ranges automatically (no hand-sync footgun). `@learn6502/6502` is made public (the standalone, zero-dep core); common-ui/examples/learn flipped to `private` so only 6502 publishes. Adds @changesets/cli + changeset/changeset:version/changeset:publish scripts + .changeset/config.json. - 6502 publish-readiness: types/files/repository/publishConfig(access:public). - pnpm-workspace.yaml (pnpm ignores the package.json `workspaces` field) with nodeLinker: hoisted (the strict layout breaks the gjsify bundler's --globals auto node-builtin resolution). - Manual `Package Managers` CI workflow (workflow_dispatch + weekly cron, NOT per-PR) verifying npm/yarn/pnpm/gjsify each install + resolve the workspaces. - README: document install via npm/yarn/pnpm/gjsify (gjsify recommended) + a Releasing (Changesets) section. - Regenerate gjsify-lock.json (adds the @changesets/cli subtree; no existing dep bumped).
This was referenced Jun 22, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Install with any package manager + set up npm publishing (Changesets)
Makes the monorepo installable with npm, yarn, pnpm or gjsify, and sets up npm publishing for
@learn6502/6502via Changesets.Why / what
workspace:protocol → internal deps use plain^0.7.0ranges. npm and classic yarn can't resolveworkspace:(only berry/pnpm/gjsify can); plain ranges work with all of npm/yarn/pnpm/gjsify (each symlinks the dep to the local workspace).fixedgroup over@learn6502/*) bumps versions and rewrites the internal^ranges automatically — no hand-sync footgun.@learn6502/6502(the standalone, zero-dep core) is made public;common-ui/examples/learnflipped toprivateso only 6502 publishes. Adds@changesets/cli+changeset/changeset:version/changeset:publishscripts +.changeset/config.json.types/files/repository/publishConfig: { access: public }.pnpm-workspace.yaml(pnpm ignores theworkspacesfield) +.npmrcwithlink-workspace-packages=true(pnpm 10 won't link local workspaces for plain ranges otherwise) andnode-linker=hoisted(the strict layout breaks the gjsify bundler's--globals auto).Package Managersworkflow (workflow_dispatch+ weekly cron, never per-PR) verifying npm/yarn/pnpm/gjsify each install + resolve the workspaces.gjsify-lock.json(+ the@changesets/clisubtree; no existing dep bumped) andgjsify-sources.json(+52 tarballs, purely additive — so the offline Flatpak build still installs).Verified (real install + build, isolated worktrees)
workspace:^).npmrc)Unsupported URI schemeregression)(The
.npmrcpnpm keys are cosmetic-only for npm — "Unknown project config" warnings, install still exit 0 — and ignored by yarn/gjsify.)Note on publishing
This sets the repo publish-ready; the first
@learn6502/6502npm publish (scope + auth/OIDC) is a maintainer step. After that, the Changesets flow (changeset→changeset:version→changeset:publish) takes over.