@stacksjs/env 0.72.39 → 0.72.41
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/dist/plaintext.d.ts +1 -1
- package/package.json +3 -3
package/dist/plaintext.d.ts
CHANGED
|
@@ -16,7 +16,7 @@
|
|
|
16
16
|
*
|
|
17
17
|
* That rule sounds right and is unusable. `.env.production` at the time of
|
|
18
18
|
* writing holds 26 non-empty plaintext values, nearly all of them things like
|
|
19
|
-
* `APP_NAME=Stacks`, `DB_HOST=127.0.0.1` and `MAIL_HOST=
|
|
19
|
+
* `APP_NAME=Stacks`, `DB_HOST=127.0.0.1` and `MAIL_HOST=127.0.0.1`. Failing on
|
|
20
20
|
* those trains people to pass `--force`, which is worse than not checking.
|
|
21
21
|
*
|
|
22
22
|
* So the question asked here is narrower and answerable: **does this key look
|
package/package.json
CHANGED
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
"name": "@stacksjs/env",
|
|
3
3
|
"type": "module",
|
|
4
4
|
"sideEffects": false,
|
|
5
|
-
"version": "0.72.
|
|
5
|
+
"version": "0.72.41",
|
|
6
6
|
"description": "Stacks env helper methods.",
|
|
7
7
|
"author": "Chris Breuer",
|
|
8
8
|
"contributors": [
|
|
@@ -55,10 +55,10 @@
|
|
|
55
55
|
"prepublishOnly": "bun run build"
|
|
56
56
|
},
|
|
57
57
|
"dependencies": {
|
|
58
|
-
"@stacksjs/path": "0.72.
|
|
58
|
+
"@stacksjs/path": "0.72.41"
|
|
59
59
|
},
|
|
60
60
|
"devDependencies": {
|
|
61
61
|
"better-dx": "^0.2.24",
|
|
62
|
-
"@stacksjs/validation": "0.72.
|
|
62
|
+
"@stacksjs/validation": "0.72.41"
|
|
63
63
|
}
|
|
64
64
|
}
|