groombook/app
Archived
13
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix API crash: add exports field and clean runtime image #44

Merged
ghost merged 1 commits from fix/api-docker-resolution into main 2026-03-18 03:13:47 +00:00
Conversation 0 Commits 1 Files Changed 4
+26
ghost commented 2026-03-18 03:08:13 +00:00 (Migrated from github.com)
Copy Link
Copy Source

Summary

  • Added exports field to @groombook/db and @groombook/types package.json for explicit ESM resolution
  • Added type: module to workspace packages for correct Node.js module handling
  • Added rm -rf cleanup in Dockerfile runner stage to ensure no TS source files in runtime image
  • Added .dockerignore to reduce build context size

Problem

API pods are in CrashLoopBackOff with ERR_UNKNOWN_FILE_EXTENSION: ".ts" — Node.js was resolving to TypeScript source files instead of compiled JS output due to missing exports field and stale Docker layer cache.

Test plan

  • pnpm typecheck passes for API, db, and types packages
  • pnpm --filter @groombook/api test passes (8/8 tests)
  • pnpm --filter @groombook/api build succeeds
  • CI builds Docker image and pushes to ghcr.io
  • API pods start successfully after image update

🤖 Generated with Claude Code

## Summary - Added `exports` field to `@groombook/db` and `@groombook/types` package.json for explicit ESM resolution - Added `type: module` to workspace packages for correct Node.js module handling - Added `rm -rf` cleanup in Dockerfile runner stage to ensure no TS source files in runtime image - Added `.dockerignore` to reduce build context size ## Problem API pods are in CrashLoopBackOff with `ERR_UNKNOWN_FILE_EXTENSION: ".ts"` — Node.js was resolving to TypeScript source files instead of compiled JS output due to missing `exports` field and stale Docker layer cache. ## Test plan - [x] `pnpm typecheck` passes for API, db, and types packages - [x] `pnpm --filter @groombook/api test` passes (8/8 tests) - [x] `pnpm --filter @groombook/api build` succeeds - [ ] CI builds Docker image and pushes to ghcr.io - [ ] API pods start successfully after image update 🤖 Generated with [Claude Code](https://claude.com/claude-code)
This repo is archived. You cannot comment on pull requests.
Reviewers
No Reviewers
Labels
Clear labels
bug
Something isn't working
 documentation
Improvements or additions to documentation
 duplicate
This issue or pull request already exists
 enhancement
New feature or request
 feature
New feature
 good first issue
Good for newcomers
 help wanted
Extra attention is needed
 invalid
This doesn't seem right
 question
Further information is requested
 wontfix
This will not be worked on
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
ai-review (AI Review) gb_barkley (Barkley Trimsworth) cpfarhood (Chris Farhood) ci (Continuous Integration [bot]) gb_flea (Flea Flicker) flux (Flux CD) admin (Gitea Admin) gb_lint (Lint Roller) renovate (Mend Renovate) gb_pawla (Pawla Abdul) gb_scrubs (Scrubs McBarkley) gb_shedward (Shedward Scissorhands) gb_dogfather (The Dogfather)
No Assignees
1 Participants
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: groombook/app#44
Delete Branch "fix/api-docker-resolution"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?