DEP-AI-07medium SeverityAI Hallucinations & Dependency Hygiene
DevDependencies Properly Separated from Production Dependencies
AI tools add build tooling, testing frameworks (jest, vitest), and types directly into dependencies instead of devDependencies.
1-Click Fix Prompt for Cursor & Claude Code
Review my codebase for "DevDependencies Properly Separated from Production Dependencies" (DEP-AI-07). Issue: AI tools add build tooling, testing frameworks (jest, vitest), and types directly into dependencies instead of devDependencies. Remediation required: Move build and test tools to devDependencies to keep production container images lean and secure. Please: 1. Locate any occurrences of this issue across my repository. 2. Refactor the code to follow production standards without breaking existing functionality. 3. Provide a clear command or step to test and verify the fix.
Why AI Assistants Write This Bug
AI tools add build tooling, testing frameworks (jest, vitest), and types directly into dependencies instead of devDependencies.
AI code generation prioritizes immediate syntax execution over production edge cases. When an assistant hits an undefined variable or strict type error, it frequently takes the path of least resistance rather than implementing standard pre-launch security patterns.
Code Comparison
Common AI Code PatternVulnerable
// Vulnerable AI-generated pattern for: DevDependencies Properly Separated from Production Dependencies
// Problematic pattern: AI tools add build tooling, testing frameworks (jest, vitest), and types directly into dependencies instead of devDependencies.Launch-Ready Fix
// Production-ready fix for: DevDependencies Properly Separated from Production Dependencies
// Recommended remediation: Move build and test tools to devDependencies to keep production container images lean and secure.Remediation & Verification Checklist
Remediation: Move build and test tools to devDependencies to keep production container images lean and secure.
- Search your codebase for pattern matching "DevDependencies Properly Separated from Production Dependencies".
- Apply the recommended remediation: Move build and test tools to devDependencies to keep production container images lean and secure.
- Run local build and test commands to ensure no regressions.
- Verify in your browser or with curl that the issue is resolved.
Audit All 108 Checks in One Click
Checking items one by one takes hours. Let us do it in 2 minutes.
With the Founder Pass ($15 one-time), we automatically scan your repository for this issue, plus all other 107 launch checks across secrets, Stripe webhooks, Supabase RLS, and security headers.