@evnx/cli 0.3.0 → 0.3.1

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 +47 -2
  2. package/package.json +6 -6
package/README.md CHANGED
@@ -27,6 +27,12 @@ Accidentally committing secrets to version control is one of the most common and
27
27
  curl -sSL https://raw.githubusercontent.com/urwithajit9/evnx/main/scripts/install.sh | bash
28
28
  ```
29
29
 
30
+ ### Homebrew (macOS and Linux)
31
+
32
+ ```bash
33
+ brew install urwithajit9/evnx/evnx
34
+ ```
35
+
30
36
  ### npm
31
37
 
32
38
  ```bash
@@ -34,13 +40,52 @@ npm install -g @evnx/cli
34
40
  ```
35
41
 
36
42
  ### pipx (recommended for Python environments)
43
+ ```bash
44
+ pipx install evnx
45
+ ```
46
+
47
+ pipx installs CLI tools into isolated environments and wires them to your
48
+ system PATH automatically. It is the correct tool for installing Python-
49
+ distributed CLI binaries like evnx.
50
+
51
+ **Don't have pipx?**
52
+
53
+ **macOS**
54
+ ```bash
55
+ brew install pipx
56
+ pipx ensurepath
57
+ ```
37
58
 
59
+ **Ubuntu / Debian (Python 3.11+)**
38
60
  ```bash
61
+ sudo apt install pipx
62
+ pipx ensurepath
63
+ ```
64
+ On older Ubuntu (20.04 and below) where `pipx` is not in apt:
65
+ ```bash
66
+ pip install --user pipx
67
+ python -m pipx ensurepath
68
+ ```
69
+ Note: `pip install evnx` will fail on Ubuntu 22.04+ with an "externally managed
70
+ environment" error (PEP 668). This is intentional — Ubuntu protects the system
71
+ Python. Use pipx instead.
72
+
73
+ **Windows**
74
+ ```powershell
75
+ python -m pip install --user pipx
76
+ python -m pipx ensurepath
77
+ ```
78
+ After running `ensurepath`, close and reopen your terminal (a full logout/login
79
+ may be required for PATH changes to take effect), then:
80
+ ```powershell
39
81
  pipx install evnx
40
82
  ```
41
83
 
42
- > `pip install evnx` also works but places the binary inside the active virtualenv's `bin/` directory.
43
- > Use `pipx` to make `evnx` available system-wide without managing a virtualenv manually.
84
+ After installing pipx on any platform, restart your terminal and run:
85
+ ```bash
86
+ pipx install evnx
87
+ evnx --version
88
+ ```
44
89
 
45
90
  ### Cargo
46
91
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@evnx/cli",
3
- "version": "0.3.0",
3
+ "version": "0.3.1",
4
4
  "description": "CLI tool for managing .env files — validation, secret scanning, format conversion",
5
5
  "keywords": ["dotenv", "env", "secrets", "cli", "security", "devtools", "environment"],
6
6
  "author": "Ajit Kumar <support@evnx.dev>",
@@ -20,11 +20,11 @@
20
20
  "postinstall": "node install.js"
21
21
  },
22
22
  "optionalDependencies": {
23
- "@evnx/evnx-linux-x64": "0.3.0",
24
- "@evnx/evnx-linux-arm64": "0.3.0",
25
- "@evnx/evnx-darwin-x64": "0.3.0",
26
- "@evnx/evnx-darwin-arm64": "0.3.0",
27
- "@evnx/evnx-win32-x64": "0.3.0"
23
+ "@evnx/evnx-linux-x64": "0.3.1",
24
+ "@evnx/evnx-linux-arm64": "0.3.1",
25
+ "@evnx/evnx-darwin-x64": "0.3.1",
26
+ "@evnx/evnx-darwin-arm64": "0.3.1",
27
+ "@evnx/evnx-win32-x64": "0.3.1"
28
28
  },
29
29
  "engines": {
30
30
  "node": ">=14"