Replies: 1 comment 1 reply
-
|
I solved my problem. The issue was not with loading modules; they were all loading correctly, which I verified by debugging The mutation in question was not being loaded because it referenced an environment variable that was missing. This meant the code would compile via |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Is there a process for debugging why
blitz consoleisn't loading all modules?I've had this problem on multiple occasions and the cause is typically because of an issue that's also visible in
npm run buildornpm run dev. But today it's not and I've tried everything including blowing away the local database, removing the.blitzand.nextdirectories, and rebooting.Is there some way to run this in verbose mode? Launching
npm run consolein vscode debug does not show any issues.Beta Was this translation helpful? Give feedback.
All reactions