Skip to content

Migrate typescript boilerplate from npm to pnpm#2

Merged
rsauget merged 2 commits into
mainfrom
claude/project-purpose-gddshn
Jul 5, 2026
Merged

Migrate typescript boilerplate from npm to pnpm#2
rsauget merged 2 commits into
mainfrom
claude/project-purpose-gddshn

Conversation

@rsauget

@rsauget rsauget commented Jul 5, 2026

Copy link
Copy Markdown
Owner

Summary

  • Move typescript/ from npm to pnpm, as a self-contained pnpm project — no repo-wide workspace. This repo hosts boilerplates for multiple languages, not a monorepo, so a root pnpm-workspace.yaml/package.json doesn't make sense here.
  • typescript/package.json now pins packageManager: pnpm@11.10.0
  • Replace typescript/package-lock.json with typescript/pnpm-lock.yaml
  • Update .github/workflows/typescript.yml to install/run via pnpm (pnpm/action-setup@v6, actions/setup-node pnpm cache, pnpm install --frozen-lockfile), scoped to typescript/

Test plan

  • pnpm install from a clean state inside typescript/
  • pnpm run lint / pnpm run typecheck / pnpm run build (+ run compiled dist/index.js)
  • pnpm test
  • pnpm run dev (native node --watch src/index.ts)

claude added 2 commits July 5, 2026 19:48
Sets up a pnpm workspace (single package for now) so future
boilerplates can be added to the same monorepo without re-plumbing
tooling, and so a shared dependency catalog can be introduced later
without more structural change. CI updated to install/run via pnpm.
This repo hosts boilerplates for multiple languages, not a single
monorepo, so a root pnpm-workspace.yaml doesn't make sense. Move the
packageManager pin and lockfile into typescript/ so it stays a
self-contained pnpm project; CI updated accordingly.
@rsauget rsauget merged commit d29df07 into main Jul 5, 2026
1 check passed
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.

2 participants