envprism 0.3.0-dev.25-5067c65 → 0.3.0-dev.28-187487b
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.
- package/README.md +9 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -10,7 +10,7 @@
|
|
|
10
10
|
[](https://bun.sh/)
|
|
11
11
|
[](LICENSE)
|
|
12
12
|
|
|
13
|
-
|
|
14
14
|
|
|
15
15
|
</div>
|
|
16
16
|
|
|
@@ -22,6 +22,14 @@ bunx envprism
|
|
|
22
22
|
|
|
23
23
|
That's it. Point `envprism` at a directory containing `.env*` files and it opens a side-by-side matrix view: rows are variable keys, columns are files. Differences light up, missing keys are obvious, and you can edit cells in place — comments, blank lines, and key order survive the round trip.
|
|
24
24
|
|
|
25
|
+
## 🤔 Why
|
|
26
|
+
|
|
27
|
+
Most projects accumulate a fistful of env files — `.env`, `.env.example`, `.env.staging`, `.env.production` — and no good way to see them together. You `diff` two at a time, miss the third, and ship a deploy where `REDIS_URL` was set everywhere except staging. The example file rots because nobody updates it when they add a key. Secrets get pasted into screenshots.
|
|
28
|
+
|
|
29
|
+
envprism treats the whole set as one thing. Every file becomes a column, every variable a row, and the gaps jump out at a glance: this key is missing here, that value drifts there, this one is still a `CHANGEME` placeholder. Edit a cell and the write-back is byte-exact — comments, blank lines, key order, and quoting all survive. Secret values stay masked, so the view is safe to share.
|
|
30
|
+
|
|
31
|
+
One set of variables, refracted into many environment views.
|
|
32
|
+
|
|
25
33
|
> [!IMPORTANT]
|
|
26
34
|
> `envprism` runs on **[Bun](https://bun.sh/)** 1.3+. The TUI is powered by [opentui](https://opentui.com/), which links to a native Zig core via `bun:ffi`. Node has no equivalent built-in FFI, so `npx envprism` will not work — install Bun first.
|
|
27
35
|
|
package/package.json
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"$schema": "https://www.schemastore.org/package.json",
|
|
3
3
|
"name": "envprism",
|
|
4
|
-
"version": "0.3.0-dev.
|
|
4
|
+
"version": "0.3.0-dev.28-187487b",
|
|
5
5
|
"description": "TUI-based env file manager — refract one set of variables into many environment views.",
|
|
6
6
|
"keywords": [
|
|
7
7
|
"bun",
|