nimblybase 0.1.3 → 0.1.4

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 (3) hide show
  1. package/README.md +16 -1
  2. package/dist/index.js +7506 -1716
  3. package/package.json +1 -1
package/README.md CHANGED
@@ -4,7 +4,7 @@ The NimblyBase command line. Projects, keys and backends from a terminal.
4
4
 
5
5
  ```bash
6
6
  npx nimblybase login
7
- npx nimblybase create "My App"
7
+ npx nimblybase init "My App" --recipe static-d1
8
8
  npx nimblybase describe
9
9
  npx nimblybase keys create "local dev"
10
10
  ```
@@ -37,6 +37,21 @@ value prompts without echoing it.
37
37
  In CI, set `NIMBLYBASE_TOKEN` instead. It takes precedence over anything
38
38
  stored and is never written to disk.
39
39
 
40
+ ## Requirements before creating
41
+
42
+ For a new empty application, choose `--recipe static-d1` explicitly when a static
43
+ frontend, light database and Worker functions fit. For existing code, run
44
+ `nimbly assess` first and resolve unsupported or unclear requirements. `init` and
45
+ `create` inspect locally, save a matching plan, then submit it for admission.
46
+ Source files and credential values stay on your machine. Selected facts are not
47
+ build, health or spending-limit proof.
48
+
49
+ A pending request is stored in `.nimblybase.bootstrap.json` before creation.
50
+ Retry the same command after a lost response. Do not delete this file or issue a
51
+ new plan to bypass an unresolved request. Changing the target, workspace or
52
+ inspected requirements stops that retry. Use `init --project <slug>` to reconnect
53
+ to an existing application's project without creating resources.
54
+
40
55
  ## Linking a directory
41
56
 
42
57
  ```bash