eraspace 0.3.0 → 0.4.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.
- package/README.md +2 -0
- package/bin.js +664 -177
- package/package.json +1 -1
- package/sdk/src/client/client.ts +10 -6
- package/sdk/src/client/files.ts +2 -0
- package/sdk/src/client/index.ts +1 -0
- package/sdk/src/client/sub-key.ts +3 -0
- package/templates/chat/client/index.tsx +11 -3
package/README.md
CHANGED
|
@@ -25,6 +25,8 @@ sign in and claim it (`eraspace auth login`, then `eraspace claim`).
|
|
|
25
25
|
| `typecheck` | Typecheck `server/`, `client/` and `shared/` |
|
|
26
26
|
| `deploy` | Build the client, compile the server and deploy (`--delete-table <table>=<rows>` confirms deleting a removed table; `--shadow` first reruns the app's live queries on the new code and reports which results change or start throwing, and `--fail-on-query-errors` refuses the deploy if any would throw) |
|
|
27
27
|
| `dev` | Deploy, then redeploy whenever `server/`, `client/`, `shared/` or `.env.eraspace.server` change |
|
|
28
|
+
| `deploys [app]` | List the latest 50 kept versions, newest first, marking the one serving; older kept versions still roll back by number |
|
|
29
|
+
| `rollback [version]` | Deploy an earlier version's server code, client files and server env again as a new version; without a version, the one before the serving version. Takes `--delete-table`, `--shadow` and `--fail-on-query-errors` like `deploy` |
|
|
28
30
|
| `call <fn> '<json>'...` | Call a query, mutation or action, each argument a JSON value |
|
|
29
31
|
| `profile [app] --seconds <n>` | Sample the app's server CPU time and write a `.cpuprofile` (TypeScript positions) for Chrome DevTools, printing the top functions by self time (`--out <file>`) |
|
|
30
32
|
| `explain <fn> '<json>'...` | Run a query once and print the rows it scanned and kept, with an index for each scan it filtered in JavaScript (`--json` for the full report) |
|