Skip to content

refactor: separate lockfile I/O from runtime public API#509

Closed
FL4TLiN3 wants to merge 1 commit intomainfrom
refactor/separate-lockfile-io-from-runtime
Closed

refactor: separate lockfile I/O from runtime public API#509
FL4TLiN3 wants to merge 1 commit intomainfrom
refactor/separate-lockfile-io-from-runtime

Conversation

@FL4TLiN3
Copy link
Contributor

Summary

  • Remove Node.js-specific findLockfile/loadLockfile from @perstack/runtime to prepare for isomorphic builds (Make @perstack/runtime isomorphic (browser-compatible) #504 Phase 1)
  • Move lockfile I/O functions to @perstack/tui (Node.js-only package) as packages/tui/src/lockfile.ts
  • Inline lockfile resolution in apps/runtime/bin/cli.ts (already Node.js-only via #!/usr/bin/env node)
  • Relocate corresponding tests alongside the moved code

Test plan

  • pnpm typecheck — 21/21 packages pass
  • pnpm test — 101 test files, 1094 tests pass
  • pnpm build — 21/21 packages build
  • pnpm format-and-lint — no new issues

🤖 Generated with Claude Code

Remove Node.js-specific lockfile I/O (findLockfile, loadLockfile) from
@perstack/runtime to make it isomorphic-ready. Lockfile search/read
logic moved to @perstack/tui (Node.js-only) and inlined in bin/cli.ts.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@FL4TLiN3
Copy link
Contributor Author

Superseded by broader refactor: removing CLI from runtime + lockfile separation

@FL4TLiN3 FL4TLiN3 closed this Feb 15, 2026
@FL4TLiN3 FL4TLiN3 deleted the refactor/separate-lockfile-io-from-runtime branch February 25, 2026 13:36
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