env-drift-check 0.1.2 → 0.1.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +3 -3
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -7,7 +7,7 @@
7
7
 
8
8
  **env-drift-check** is the ultimate CLI tool for managing environment variables in Node.js projects. It ensures your local `.env` file is always in sync with `.env.example`, preventing runtime errors caused by missing keys. Perfect for teams and CI/CD pipelines.
9
9
 
10
- ![env-drift-check demo](./public/env-drift-check.png)
10
+ ![env-drift-check demo](https://github.com/shashi089/env-drift-check/raw/main/assets/env-drift-check.png)
11
11
 
12
12
  ## Why use this?
13
13
 
@@ -54,11 +54,11 @@ npx env-drift-check --interactive
54
54
  npx env-drift-check -i
55
55
  ```
56
56
 
57
- ![Interactive update](./public/env-drift-check-i-update.png)
57
+ ![Interactive update](https://github.com/shashi089/env-drift-check/raw/main/assets/env-drift-check-i-update.png)
58
58
 
59
59
  Once completed, your `.env` file is automatically updated!
60
60
 
61
- ![Interactive success](./public/env-drift-check-i-final.png)
61
+ ![Interactive success](https://github.com/shashi089/env-drift-check/raw/main/assets/env-drift-check-i-final.png)
62
62
 
63
63
  ### 3. CI/CD Mode (Strict)
64
64
  Ensure no broken code hits production. Use strict mode in your build pipeline to fail if environment variables are missing.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "env-drift-check",
3
- "version": "0.1.2",
3
+ "version": "0.1.3",
4
4
  "description": "Interactive environment variable checker and setup wizard. Sync .env files with validation (Email, URL, Regex) and prompts.",
5
5
  "keywords": [
6
6
  "env",