@willbooster/wb 22.1.4 → 22.1.5

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 +107 -32
  2. package/dist/index.js +49 -46
  3. package/package.json +2 -2
package/README.md CHANGED
@@ -12,38 +12,100 @@
12
12
  wb <command>
13
13
 
14
14
  Commands:
15
- wb buildIfNeeded Build code if changes are detected
16
- wb kill-port <ports..> Kill the processes listening on the given TCP
17
- ports
18
- wb kill-port-if-non-ci Kill the process on the PORT environment
19
- variable (or the auto-selection preferred port)
20
- if non-CI.
21
- wb lint [files...] Lint code
22
- wb maintenance <action> Start or stop a lightweight maintenance page
23
- server.
24
- Example: wb maintenance start
25
- wb open-cli <target> Open a URL or file in its default application
26
- wb optimizeForDockerBuild Optimize configuration when building a Docker
27
- image
28
- wb prisma Run database commands [aliases: db]
29
- wb retry [command] [args...] Retry the given command until it succeeds
30
- wb setup Setup development environment. Environment
31
- variables are not loaded.
32
- wb setup-private-packages Materialize private git and registry
33
- dependencies for Docker builds (installed
34
- registry packages satisfying an exact version
35
- or semver range are reused; dist-tag
36
- specifiers and missing packages are
37
- downloaded)
38
- wb start [args..] Start app
39
- wb test [targets...] Test project. If you pass no arguments, it will
40
- run all tests.
41
- wb test-on-ci Test project on CI with no options.
42
- wb typecheck Run type checking. Environment variables are not
43
- loaded.
44
- wb tc Run type checking. Environment variables are not
45
- loaded.
46
- wb wait-on <resource> Wait for an HTTP(S) URL or TCP port
15
+ wb verify Verify project code
16
+ wb buildIfNeeded Build code if changes are detected
17
+ wb check-env Verify that every fnox-declared environment
18
+ variable and secret resolves for the current
19
+ WB_ENV. Prefix scripts that write to remote
20
+ environments with this command to fail fast on
21
+ missing secrets.
22
+ wb concurrently <commands...> Run commands concurrently
23
+ wb deploy Deploy a Cloudflare Workers app (vinext or
24
+ plain Worker) to the WB_ENV environment:
25
+ validate secrets, build, apply remote D1
26
+ migrations, then deploy code and secrets
27
+ atomically.
28
+ wb dotenv [args..] Load environment variables from fnox and run a
29
+ command.
30
+ wb gen-code Generate code for the current project
31
+ wb gen-dev-vars [path] Generate a .dev.vars file for `wrangler dev`
32
+ from the environment variables loaded from fnox
33
+ (plus WB_ENV and NEXT_PUBLIC_WB_ENV).
34
+ wb gen-docker-env [path] Generate a .docker.env file to bake into a
35
+ Docker image, containing only the non-secret
36
+ (plaintext default) values of fnox.toml for the
37
+ selected WB_ENV. Secrets are never written;
38
+ inject them at runtime from the deployment
39
+ platform. The file is shell-sourceable dotenv
40
+ (for a build-time `set -a && . ./.docker.env`
41
+ and dotenv parsers), not for `docker
42
+ --env-file`, which keeps quotes literally;
43
+ runtime entrypoints must apply baked values
44
+ only to keys the platform did not already set.
45
+ wb kill-port <ports..> Kill the processes listening on the given TCP
46
+ ports
47
+ wb kill-port-if-non-ci Kill the process on the PORT environment
48
+ variable (or the auto-selection preferred port)
49
+ if non-CI.
50
+ wb lint [files...] Lint code
51
+ wb maintenance <action> Start or stop a lightweight maintenance page
52
+ server. Example: wb maintenance start
53
+ wb open-cli <target> Open a URL or file in its default application
54
+ wb optimizeForDockerBuild Optimize configuration when building a Docker
55
+ image
56
+ wb prisma Run database commands. Use '--' to stop wb
57
+ option parsing and forward the remaining
58
+ arguments to Prisma. Drizzle projects use
59
+ drizzle-kit. Example: wb prisma migrate-dev --
60
+ --name init [aliases: db]
61
+ wb railway-env Sync the environment variables declared for the
62
+ current WB_ENV (resolved from fnox) to the
63
+ Railway service, keeping fnox the single source
64
+ of truth. Railway-managed keys (RAILWAY_*,
65
+ NIXPACKS_*, CI) are never pushed.
66
+ wb release [args..] Run semantic-release (or
67
+ multi-semantic-release) so that repositories
68
+ using Bun isolated installs can publish to npm:
69
+ reinstall with the hoisted linker (npm cannot
70
+ walk Bun's isolated node_modules layout),
71
+ rewrite `workspace:` ranges npm cannot parse,
72
+ run the release, then restore the modified
73
+ files. Extra arguments (e.g. `--debug`, after
74
+ `--`) are forwarded to the release command.
75
+ wb retry [command] [args...] Retry the given command until it succeeds
76
+ wb run [args..] Load environment variables and run a script
77
+ with the project runtime.
78
+ wb setup Setup development environment. Environment
79
+ variables are not loaded.
80
+ wb setup-private-packages Materialize private dependencies for Docker
81
+ builds: copy git dependencies, reuse installed
82
+ @willbooster-private/* registry packages whose
83
+ exact-version or semver-range specifier the
84
+ installed copy satisfies, and download the rest
85
+ (auth via .npmrc / ~/.npmrc locally, or
86
+ VERDACCIO_TOKEN on CI; dist-tag specifiers such
87
+ as `latest` always download). The Dockerfile
88
+ must COPY the generated directories (e.g. `COPY
89
+ @willbooster/ @willbooster/` and `COPY
90
+ @willbooster-private/ @willbooster-private/`)
91
+ so the in-image install resolves the rewritten
92
+ file: paths.
93
+ wb start [args..] Start app. Use '--' to stop wb option parsing
94
+ and forward the remaining arguments to the
95
+ underlying app command. Example: wb start --
96
+ --host 0.0.0.0
97
+ wb test [targets...] Test project. If you pass no arguments, it will
98
+ run all tests. Use '--' to stop wb option
99
+ parsing and forward the remaining flags to
100
+ Playwright. Example: wb test -- --grep
101
+ 'uploaded image asset'
102
+ wb test-on-ci Test project on CI with no options.
103
+ wb tree-kill <pid> [signal] Kill the given process and all descendants
104
+ wb typecheck Run type checking. Environment variables are
105
+ not loaded.
106
+ wb tc Run type checking. Environment variables are
107
+ not loaded.
108
+ wb wait-on <resource> Wait for an HTTP(S) URL or TCP port
47
109
 
48
110
  Options:
49
111
  --cascade-env Environment (fnox profile / mise env) to load
@@ -53,9 +115,22 @@ Options:
53
115
  Preferred over `auto-cascade-env`. [boolean]
54
116
  --auto-cascade-env Same with --cascade-env=<WB_ENV || NODE_ENV ||
55
117
  "development">. [boolean] [default: true]
118
+ --quiet-env Suppress environment variable loading information.
119
+ [boolean]
56
120
  -v, --verbose Whether to show verbose information [boolean]
57
121
  -w, --working-dir A working directory [string]
58
122
  -d, --dry-run, --dry Whether to skip actual command execution [boolean]
59
123
  --version Show version number [boolean]
60
124
  --help Show help [boolean]
61
125
  ```
126
+
127
+ ## Verification
128
+
129
+ `wb verify` and `wb verify --full` are intended for coding agents. The log path is printed at startup.
130
+ Successful runs print the completed steps and their durations. Failures print the
131
+ failed step name, exit code, and its last 100 lines (at most 16 KiB), followed by
132
+ the full log path. Truncated output is marked; read the log for earlier details.
133
+
134
+ Output is saved as it arrives, before display filtering,
135
+ to `.wb/verify.log` or `.wb/verify-full.log` in the verified project. Each command
136
+ overwrites its previous log; `--dry-run` leaves logs untouched.