You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+21Lines changed: 21 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -145,6 +145,27 @@ The health score is calculated based on several factors, including:
145
145
- Unused variables in your `.env` or `.env.example` file.
146
146
- Framework specific warning for SvelteKit or Next.js (depending on detected framework).
147
147
148
+
## Expiration date warnings
149
+
150
+
By default, `dotenv-diff` will detect environment variables with expiration dates and warn you if they are expired or about to expire.
151
+
To specify an expiration date for an environment variable, add a comment in the following format on the same line this an example of a .env.example file:
152
+
153
+
```bash
154
+
# @expire YYYY-MM-DD
155
+
API_TOKEN=
156
+
```
157
+
158
+
When you run `dotenv-diff`, it will check the expiration dates and display warnings for any variables that are expired or will expire soon.
159
+
160
+
## Inconsistent naming pattern warnings
161
+
162
+
By default `dotenv-diff` will detect environment variables that have inconsistent naming patterns, fx `APIKEY` & `API_KEY` will give you are warning to only use the `API_KEY`
163
+
To disable this behavior, use the `--no-inconsistent-naming-warnings` flags respectively, or set it to false in the config file:
164
+
165
+
```bash
166
+
"inconsistentNamingWarnings": false
167
+
```
168
+
148
169
## Show unused variables
149
170
150
171
As default, `dotenv-diff` will list variables that are defined in `.env` but never used in your codebase.
0 commit comments