troubleshooting-guide

Import errors in Wasp often stem from forgetting to restart the Wasp server after changes. Verify your file paths match Wasp's module structure, ensure all dependencies are installed, and restart the development server to rebuild type definitions and module resolution.

Auth errors in Wasp typically involve misconfigured authentication setup, missing environment variables, or stale type definitions. Use the diagnostic steps to verify your auth configuration matches Wasp's requirements, check environment files, and clear build artifacts before restarting.

Database problems in Wasp include connection failures, schema conflicts, and migration errors. Follow the systematic diagnostic approach to identify whether the issue is a connection configuration problem, a stale database state, or a schema mismatch, then apply the targeted fix.

Build failures and stale types occur when the Wasp compiler hasn't regenerated type definitions after code changes. The troubleshooting guide provides a quick-reference checklist to clear caches, restart the development server, and verify your code structure matches Wasp's expectations.

Yes, this troubleshooting guide covers performance concerns alongside import errors, auth problems, and database conflicts. It offers procedural sections and diagnostic workflows to identify bottlenecks and apply repeatable solutions across Wasp development scenarios.