flyspace-cli 0.1.50 → 0.1.51
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/chunk-R5RECXRP.js +34480 -0
- package/dist/cli.js +12096 -36531
- package/dist/index.js +1 -1
- package/package.json +1 -1
- package/system.capabilities.md +2 -0
- package/dist/chunk-NR5FHLR2.js +0 -9427
package/dist/index.js
CHANGED
|
@@ -3,7 +3,7 @@ import { createRequire as __flyspaceCreateRequire } from 'node:module';
|
|
|
3
3
|
const require = __flyspaceCreateRequire(import.meta.url);
|
|
4
4
|
import {
|
|
5
5
|
startServer
|
|
6
|
-
} from "./chunk-
|
|
6
|
+
} from "./chunk-R5RECXRP.js";
|
|
7
7
|
import "./chunk-HTFQL66T.js";
|
|
8
8
|
export {
|
|
9
9
|
startServer
|
package/package.json
CHANGED
package/system.capabilities.md
CHANGED
|
@@ -51,6 +51,8 @@ If you need to start a server or watcher:
|
|
|
51
51
|
|
|
52
52
|
Never run a foreground watcher / dev server / `tail -f` directly — even if the user asks "run the server" or "start dev mode", you must background it.
|
|
53
53
|
|
|
54
|
+
If a command is killed before it finishes (`Exit code 137`, or a tool timeout), do not stop and report it as unverified. Re-run it in the background with a completion callback (see below), with fewer parallel workers or in smaller pieces if it ran out of memory, and carry on once the result comes back.
|
|
55
|
+
|
|
54
56
|
### Notify on completion (push, not empty promises)
|
|
55
57
|
|
|
56
58
|
Some background tasks DO finish on their own: a build, a deploy, a test suite, a long script, waiting on a file to appear. For these, NEVER say "I'll let you know when it's done" and then end your turn — you run headless, so once your turn ends there is no future "you" to follow up. That promise is a lie.
|