@uns-kit/cli 2.0.77 → 2.0.78
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/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@uns-kit/cli",
|
|
3
|
-
"version": "2.0.
|
|
3
|
+
"version": "2.0.78",
|
|
4
4
|
"description": "Command line scaffolding tool for UNS applications",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"license": "MIT",
|
|
@@ -26,14 +26,14 @@
|
|
|
26
26
|
],
|
|
27
27
|
"dependencies": {
|
|
28
28
|
"azure-devops-node-api": "^15.1.1",
|
|
29
|
-
"@uns-kit/core": "2.0.
|
|
29
|
+
"@uns-kit/core": "2.0.78"
|
|
30
30
|
},
|
|
31
31
|
"unsKitPackages": {
|
|
32
|
-
"@uns-kit/core": "2.0.
|
|
33
|
-
"@uns-kit/api": "2.0.
|
|
34
|
-
"@uns-kit/cron": "2.0.
|
|
35
|
-
"@uns-kit/database": "2.0.
|
|
36
|
-
"@uns-kit/assistant-workflow": "2.0.
|
|
32
|
+
"@uns-kit/core": "2.0.78",
|
|
33
|
+
"@uns-kit/api": "2.0.78",
|
|
34
|
+
"@uns-kit/cron": "2.0.78",
|
|
35
|
+
"@uns-kit/database": "2.0.78",
|
|
36
|
+
"@uns-kit/assistant-workflow": "2.0.78"
|
|
37
37
|
},
|
|
38
38
|
"scripts": {
|
|
39
39
|
"build": "tsc -p tsconfig.build.json",
|
|
@@ -20,6 +20,17 @@ pnpm run sync-uns-metadata -- --controller-url http://localhost:3200 --token <me
|
|
|
20
20
|
|
|
21
21
|
Update `config.json` with your broker, UNS URLs, and credentials. The generated file contains sensible defaults for local development. If you use a service token, add `uns.token` and pass it to `UnsClient`.
|
|
22
22
|
|
|
23
|
+
For standalone local development, `pnpm run dev` and `pnpm run start` load a
|
|
24
|
+
local `.env` file when it exists. The generated `.gitignore` excludes `.env`
|
|
25
|
+
and `.env.*` files so local secrets are not committed. Values already provided
|
|
26
|
+
in the process environment take precedence over values from `.env`, and a
|
|
27
|
+
missing `.env` file does not prevent the application from starting.
|
|
28
|
+
|
|
29
|
+
`@uns-kit/core` and `ConfigFile.loadConfig()` continue to read the environment
|
|
30
|
+
already prepared for the process; they do not load `.env` themselves. This
|
|
31
|
+
local entry-script behavior does not change production, PM2, controller, or
|
|
32
|
+
Infisical environment handling.
|
|
33
|
+
|
|
23
34
|
## Validity / Liveliness
|
|
24
35
|
|
|
25
36
|
UNS attributes can declare how the controller decides whether they are live or stale; in most apps this is primarily used to drive UI liveliness/activity indicators. In app-level modeling we use two modes only:
|
|
@@ -20,8 +20,8 @@
|
|
|
20
20
|
"clean": "rimraf dist tsconfig.tsbuildinfo",
|
|
21
21
|
"typecheck": "tsc --noEmit",
|
|
22
22
|
"build": "pnpm run clean && tsc -p tsconfig.json",
|
|
23
|
-
"dev": "tsx watch src/index.ts",
|
|
24
|
-
"start": "node dist/index.js",
|
|
23
|
+
"dev": "node --env-file-if-exists=.env ./node_modules/tsx/dist/cli.mjs watch src/index.ts",
|
|
24
|
+
"start": "node --env-file-if-exists=.env dist/index.js",
|
|
25
25
|
"lint": "eslint src --ext .ts",
|
|
26
26
|
"lint:fix": "eslint src --ext .ts --fix",
|
|
27
27
|
"format": "prettier --write .",
|