fix(build): exclude prober/ from root tsconfig (unblocks Railway deploy) - #80
Merged
Merged
Conversation
next build type-checks the whole repo; prober/src/index.ts imports bullmq, which lives only in the prober workspace's own node_modules, so the main crawlproof.com build failed with 'Cannot find module bullmq'. Exclude prober/ from the root tsconfig exactly like worker/ (both are separately-built sibling workspaces with their own tsconfig + deps). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
vu1nz Security Review0 finding(s) in PR #? No security issues found. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The crawlproof.com Railway deploy (
cd3f9470…) failed at build:next buildtype-checks the entire repo.prober/src/index.tsimportsbullmq, but that dependency lives only in the prober workspace's ownnode_modules(the prober is built/installed separately on the DO droplet), so the main app build can't resolve it.Fix
Add
proberto the roottsconfig.jsonexcludearray — exactly likeworkeralready is. Both are separately-built sibling workspaces with their owntsconfig.json+ deps; the Next.js build has no business type-checking them.npm run typecheckpasses. This unblocks the crawlproof.com production deploy.🤖 Generated with Claude Code