-
-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Modify CheckEnv.js to notify dev if Vite keys are missing from .env file #1824
Comments
Reviewed PR #1822 dependency and it's looking great. Appreciate the clean up in the DbProvider. |
For existing developers, modifying the checkEnv.js file sounds like a great idea. It'd be nice to take into account those previous devs who aren't aware of this change too. For new developers, we can update the |
Updating Since checkEnv.js isn't mentioned in the README, I'll add some instructions for it there as well. |
@traycn @aqandrew I'm going to modify the ticket in a couple of different ways:
|
This ticket is now dedicated to modifying the CheckEnv.js file. Changes to .example.env will be done on this ticket's PR |
Moved to In Review since I've been re-requested on the PR. |
Overview
We need to modify our
check-env
script to notify the dev if they are using non-vite compatible environment variables so that we can ensure previous devs have migrated to Vite.Action Items
Resources
Info about relevant files
"start": "npm run check-env && npm run dev",
"node ./utils/checkEnv"
utils/checkEnv.js
Archived Info
Details
The text was updated successfully, but these errors were encountered: