chore: add env consistency check script #11
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This PR adds scripts/check-env.ts, a small helper that compares .env against .env.example. It parses both files, reports missing keys (present in .env.example but not in .env), and highlights any extra keys in .env.
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
| @@ -0,0 +1,108 @@ | |||
| ```ts | |||
There was a problem hiding this comment.
Bug: Markdown code fence accidentally included in TypeScript file
The file contains ```ts on line 1, which is markdown syntax for a code fence. This appears to have been accidentally included when copying code from a markdown document. The TypeScript file will fail to parse because ```ts is not valid TypeScript syntax.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds scripts/check-env.ts, a small helper that compares .env against .env.example. It parses both files, reports missing keys (present in .env.example but not in .env), and highlights any extra keys in .env.
Note
Adds
scripts/check-env.tsto compare.envwith.env.example, reporting missing and extra keys with a concise summary output.Written by Cursor Bugbot for commit 646614d. This will update automatically on new commits. Configure here.