I updated DeployDoctor: safer patches for “works locally, fails on Vercel”
I built DeployDoctor to catch repository mistakes that can break a Vercel deployment.
One thing I’ve spent more time on lately is deciding when a suggested fix is actually safe to offer.
For import casing, it now uses TypeScript’s syntax tree and only generates a patch when the target file is unambiguous. The patch is tied to the scanned commit and verified against the original files.
Missing or ambiguous targets need review.
Other recent additions:
• Public scan statistics showing common findings
• Ratings and a place to suggest improvements
• 21 troubleshooting guides
• A GitHub Action that puts findings into your PR workflow
The scanner uses static analysis and doesn’t execute your repository’s code. It can catch specific mistakes, but a green report isn’t a guarantee that your build will succeed.
There’s one free website scan per day, with paid passes for more scans and private repositories.
https://deploydoctor.nyttolabs.com
What’s the most frustrating “works locally” deployment failure you’ve run into?
Top comments (0)