Skip to content

fix(ci): add missing @stackpanel/infra dep to apps/api#28

Draft
cooper (czxtm) wants to merge 1 commit intomainfrom
claude/debug-ci-deployment-44sGc
Draft

fix(ci): add missing @stackpanel/infra dep to apps/api#28
cooper (czxtm) wants to merge 1 commit intomainfrom
claude/debug-ci-deployment-44sGc

Conversation

@czxtm
Copy link
Copy Markdown
Contributor

Summary

  • apps/api/alchemy.run.ts:23 imports from @stackpanel/infra/lib/deploy, but the workspace dep was never declared in apps/api/package.json. CI's bunx alchemy deploy --stage production consequently failed with ResolveMessage: Cannot find module '@stackpanel/infra/lib/deploy' from '.../apps/api/alchemy.run.ts'.
  • apps/web and apps/docs (which use the same helper) both already declare "@stackpanel/infra": "workspace:*"apps/api was the outlier.
  • Added the dep + corresponding entry in bun.lock. After install, apps/api/node_modules/@stackpanel/infra symlinks to packages/infra, and bun --print 'require.resolve("@stackpanel/infra/lib/deploy")' from apps/api now resolves to packages/infra/src/lib/deploy.ts.

Test plan

  • CI re-runs the alchemy deploy --stage production step and the resolve error no longer appears
  • Spot-check that web/docs deploys still resolve @stackpanel/infra/lib/deploy (no lockfile drift)

https://claude.ai/code/session_01WGbZGB93xMgBpBmoUDk91w


Generated by Claude Code

apps/api/alchemy.run.ts imports from @stackpanel/infra/lib/deploy
but the workspace dep wasn't declared, so bunx alchemy deploy failed
with ResolveMessage when CI ran from a clean install.

https://claude.ai/code/session_01WGbZGB93xMgBpBmoUDk91w
@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 1, 2026

Preview deployed to pr-28https://pr-28.stackpanel.com

@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 1, 2026

Docs preview deployed to pr-28

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