Migrate codex-flows to Node pnpm and VitePlus #1

Closed
matamune wants to merge 2 commits from migration/node-pnpm-viteplus into main
Owner

Summary

  • migrates the monorepo from Bun to Node 24 LTS + pnpm + VitePlus
  • replaces runner = "bun" / defineBunFlow with the Node flow runner and helpers, with no compatibility path
  • replaces Bun runtime APIs with Node APIs, including node:sqlite, Node HTTP, Node child processes, and smol-toml
  • updates CI, docs, bundled flows, gateway packaging, and package-on-demand commands to vp / pnpm
  • aligns package versions to 0.132.1 and documents the Codex-line versioning policy in RELEASE.md

Verification

  • pnpm install --frozen-lockfile
  • pnpm run check:types
  • pnpm run test
  • pnpm run build
  • pnpm run release:check
  • git diff --check
  • targeted Bun/vpx/bunx cruft search

Notes

This is intentionally a breaking migration. The branch removes Bun lock/config/type dependencies and does not preserve runner = "bun" or defineBunFlow aliases.

## Summary - migrates the monorepo from Bun to Node 24 LTS + pnpm + VitePlus - replaces `runner = "bun"` / `defineBunFlow` with the Node flow runner and helpers, with no compatibility path - replaces Bun runtime APIs with Node APIs, including `node:sqlite`, Node HTTP, Node child processes, and `smol-toml` - updates CI, docs, bundled flows, gateway packaging, and package-on-demand commands to `vp` / `pnpm` - aligns package versions to `0.132.1` and documents the Codex-line versioning policy in `RELEASE.md` ## Verification - `pnpm install --frozen-lockfile` - `pnpm run check:types` - `pnpm run test` - `pnpm run build` - `pnpm run release:check` - `git diff --check` - targeted Bun/vpx/bunx cruft search ## Notes This is intentionally a breaking migration. The branch removes Bun lock/config/type dependencies and does not preserve `runner = "bun"` or `defineBunFlow` aliases.
matamune added 4 commits 2026-05-20 20:49:07 +00:00
Author
Owner

Closing in favor of #2. This PR developed stale Forgejo metadata and showed a missing-fork-information warning even though the Git branch still existed. #2 uses the same head commit with healthy PR metadata.

Closing in favor of #2. This PR developed stale Forgejo metadata and showed a missing-fork-information warning even though the Git branch still existed. #2 uses the same head commit with healthy PR metadata.
matamune closed this pull request 2026-05-20 21:26:50 +00:00

Pull request closed

Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: peezy-tech/codex-toys#1
No description provided.