flypod 0.8.0 → 0.10.0
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/LICENSE +42 -15
- package/README.md +196 -77
- package/dist/bin/deploy.js +836 -337
- package/dist/{cli-g2wb2hxm.js → cli-198a0gkx.js} +1093 -1008
- package/dist/src/cli/commands.d.ts +19 -2
- package/dist/src/cli/errors.d.ts +68 -0
- package/dist/src/cli/receipt.d.ts +162 -0
- package/dist/src/cli.d.ts +16 -0
- package/dist/src/cli.js +6 -4
- package/dist/src/deploy-source.d.ts +26 -1
- package/dist/src/pack.d.ts +25 -0
- package/package.json +5 -6
|
@@ -1,3 +1,4 @@
|
|
|
1
|
+
import { type TailStyle } from "./receipt";
|
|
1
2
|
type FetchLike = typeof fetch;
|
|
2
3
|
export interface CommandIO {
|
|
3
4
|
/** Write a line to stdout (the scriptable surface). */
|
|
@@ -12,16 +13,30 @@ export interface CommandIO {
|
|
|
12
13
|
cwd?: string;
|
|
13
14
|
/** Open a URL in the default browser. Tests inject a no-op. */
|
|
14
15
|
openUrl?: (url: string) => Promise<void>;
|
|
16
|
+
/**
|
|
17
|
+
* How to paint the human-facing lines. Injected by the bin entrypoint so
|
|
18
|
+
* `update`/`rollback` accent their URL exactly as a first deploy does;
|
|
19
|
+
* omitted everywhere else, which renders plain text (and keeps the suite
|
|
20
|
+
* asserting on strings rather than on escape sequences).
|
|
21
|
+
*/
|
|
22
|
+
style?: TailStyle;
|
|
15
23
|
}
|
|
16
24
|
export declare function login(args: {
|
|
17
25
|
token?: string;
|
|
26
|
+
deviceCode?: string;
|
|
27
|
+
json?: boolean;
|
|
18
28
|
help?: boolean;
|
|
19
29
|
}, io: CommandIO): Promise<number>;
|
|
20
|
-
export declare function logout(
|
|
21
|
-
|
|
30
|
+
export declare function logout(args: {
|
|
31
|
+
json?: boolean;
|
|
32
|
+
}, io: CommandIO): Promise<number>;
|
|
33
|
+
export declare function list(args: {
|
|
34
|
+
json?: boolean;
|
|
35
|
+
}, io: CommandIO): Promise<number>;
|
|
22
36
|
export declare function claim(args: {
|
|
23
37
|
site_id?: string;
|
|
24
38
|
token?: string;
|
|
39
|
+
json?: boolean;
|
|
25
40
|
}, io: CommandIO): Promise<number>;
|
|
26
41
|
export declare function update(args: {
|
|
27
42
|
path?: string;
|
|
@@ -59,10 +74,12 @@ export declare function rollback(args: {
|
|
|
59
74
|
*/
|
|
60
75
|
export declare function token(args: {
|
|
61
76
|
site?: string;
|
|
77
|
+
json?: boolean;
|
|
62
78
|
help?: boolean;
|
|
63
79
|
}, io: CommandIO): Promise<number>;
|
|
64
80
|
export declare function forget(args: {
|
|
65
81
|
site?: string;
|
|
82
|
+
json?: boolean;
|
|
66
83
|
help?: boolean;
|
|
67
84
|
}, io: CommandIO): Promise<number>;
|
|
68
85
|
export {};
|
|
@@ -0,0 +1,68 @@
|
|
|
1
|
+
import type { CommandIO } from "./commands";
|
|
2
|
+
export type ErrorCode = "usage" | "unknown_command" | "unknown_flag" | "no_build_dir" | "no_files" | "no_site" | "no_token" | "not_signed_in" | "unauthorized" | "token_rejected" | "not_found" | "no_such_version" | "site_gone" | "already_claimed" | "invalid_upload" | "too_large" | "blocked" | "challenge_required" | "rate_limited" | "server_error" | "bad_request" | "network" | "interactive_login_required" | "authorization_pending" | "login_denied" | "login_expired" | "login_timeout" | "unexpected";
|
|
3
|
+
export interface CliError {
|
|
4
|
+
code: ErrorCode;
|
|
5
|
+
/** Human-readable reason. Free text; agents branch on `code` instead. */
|
|
6
|
+
error: string;
|
|
7
|
+
/** The literal next step, when there is one. */
|
|
8
|
+
fix?: string;
|
|
9
|
+
/** HTTP status that produced this, when a server was involved. */
|
|
10
|
+
status?: number;
|
|
11
|
+
/** Extra machine-readable fields merged into the JSON envelope. */
|
|
12
|
+
extra?: Record<string, unknown>;
|
|
13
|
+
}
|
|
14
|
+
export declare function exitCodeFor(code: ErrorCode): number;
|
|
15
|
+
/** The wire shape, exactly as it is written to stdout under `--json`. */
|
|
16
|
+
export declare function errorEnvelope(err: CliError): Record<string, unknown>;
|
|
17
|
+
/**
|
|
18
|
+
* Report a failure and return the exit code the caller should propagate.
|
|
19
|
+
*
|
|
20
|
+
* `--json` → one line of JSON on stdout, nothing on stderr. Otherwise the
|
|
21
|
+
* reason goes to stderr with the fix on the next line, prefixed so the user
|
|
22
|
+
* sees which verb failed.
|
|
23
|
+
*/
|
|
24
|
+
export declare function emitError(err: CliError, args: {
|
|
25
|
+
json?: boolean;
|
|
26
|
+
}, io: Pick<CommandIO, "out" | "err">, opts?: {
|
|
27
|
+
prefix?: string;
|
|
28
|
+
}): number;
|
|
29
|
+
/** Shorthand for the common "build the error, emit it, return the code" line. */
|
|
30
|
+
export declare function fail(code: ErrorCode, error: string, args: {
|
|
31
|
+
json?: boolean;
|
|
32
|
+
}, io: Pick<CommandIO, "out" | "err">, opts?: {
|
|
33
|
+
fix?: string;
|
|
34
|
+
prefix?: string;
|
|
35
|
+
status?: number;
|
|
36
|
+
extra?: Record<string, unknown>;
|
|
37
|
+
}): number;
|
|
38
|
+
/**
|
|
39
|
+
* What the server actually said. The control plane answers with
|
|
40
|
+
* `{ error, code }` JSON; older paths and the edge answer with plain text.
|
|
41
|
+
* Either way the caller gets a sentence, never `[object Object]` or an empty
|
|
42
|
+
* string.
|
|
43
|
+
*/
|
|
44
|
+
export declare function readServerMessage(res: Response): Promise<{
|
|
45
|
+
message: string;
|
|
46
|
+
code?: string;
|
|
47
|
+
}>;
|
|
48
|
+
export interface ClassifyContext {
|
|
49
|
+
/** `flypod update`, `flypod comments post`, … — for the human prefix. */
|
|
50
|
+
verb: string;
|
|
51
|
+
/** The site the request was about, for the `fix` wording. */
|
|
52
|
+
siteId?: string;
|
|
53
|
+
/** True when a 404 means "the site is gone" rather than "no such thing". */
|
|
54
|
+
siteScoped?: boolean;
|
|
55
|
+
}
|
|
56
|
+
/**
|
|
57
|
+
* Turn a non-2xx response into a `CliError` with a stable code and a fix.
|
|
58
|
+
* The server's own `code` wins when it sends one (e.g. `token_rejected`);
|
|
59
|
+
* otherwise the status decides.
|
|
60
|
+
*/
|
|
61
|
+
export declare function classifyResponse(res: Response, ctx: ClassifyContext): Promise<CliError>;
|
|
62
|
+
/** A `fetch` that threw: DNS, refused connection, TLS, timeout. */
|
|
63
|
+
export declare function networkError(e: unknown, baseUrl?: string): CliError;
|
|
64
|
+
/** The canonical "nothing is linked here" failure, shared by every verb that targets a site. */
|
|
65
|
+
export declare const NO_SITE: CliError;
|
|
66
|
+
export declare const NOT_SIGNED_IN: CliError;
|
|
67
|
+
/** Message for `main().catch` and any other last-resort handler. */
|
|
68
|
+
export declare function unexpectedError(e: unknown): CliError;
|
|
@@ -0,0 +1,162 @@
|
|
|
1
|
+
export declare const DAY_MS = 86400000;
|
|
2
|
+
/**
|
|
3
|
+
* The column budget every line printed by this module lives inside.
|
|
4
|
+
*
|
|
5
|
+
* Not a style preference. Every launch asset is a terminal recording rendered
|
|
6
|
+
* at a fixed frame size (`docs/growth/assets/README.md`), and a line that wraps
|
|
7
|
+
* mid-word directly under the URL wrecks the hero frame the whole campaign is
|
|
8
|
+
* built on — that README documents two renders where it already happened. 66
|
|
9
|
+
* columns is the width that buys back a 16:9 frame at a legible glyph size.
|
|
10
|
+
*
|
|
11
|
+
* `test/cli-tail-width.test.ts` fails the build when a line outgrows it, which
|
|
12
|
+
* is the point of doing this in code rather than by eye.
|
|
13
|
+
*/
|
|
14
|
+
export declare const TAIL_WIDTH = 66;
|
|
15
|
+
/**
|
|
16
|
+
* Rows `deployTail` may occupy. The surrounding deploy screen (banner, account,
|
|
17
|
+
* source, the ✓ line, and the rule/URL block) is twelve more, which puts the
|
|
18
|
+
* whole thing at nineteen — one 16:9 frame, no scroll.
|
|
19
|
+
*/
|
|
20
|
+
export declare const TAIL_ROWS = 7;
|
|
21
|
+
/** What the terminal actually shows, with color escapes discounted. */
|
|
22
|
+
export declare function visibleWidth(line: string): number;
|
|
23
|
+
/** Whole days from `now` until `expiresAt`, floored at 0. */
|
|
24
|
+
export declare function daysUntil(expiresAt: number, now: number): number;
|
|
25
|
+
/**
|
|
26
|
+
* A date a human can put in a calendar: `27 Sep 2026`. Deliberately not
|
|
27
|
+
* locale-formatted — the string is also read by agents and copied into issues,
|
|
28
|
+
* and an unambiguous day-month-year beats a locale-correct 09/27 vs 27/09
|
|
29
|
+
* coin flip.
|
|
30
|
+
*/
|
|
31
|
+
export declare function expiryDate(expiresAt: number): string;
|
|
32
|
+
/**
|
|
33
|
+
* A version's timestamp, for the `flypod versions` table: `27 Sep 2026 14:03
|
|
34
|
+
* UTC`. Same day-month-year as `expiryDate` plus the clock, because two
|
|
35
|
+
* versions of the same site are usually minutes apart and a date alone cannot
|
|
36
|
+
* tell them apart.
|
|
37
|
+
*
|
|
38
|
+
* Zoned explicitly. A bare `14:03` next to a wall clock showing something else
|
|
39
|
+
* is the kind of small wrongness that makes someone distrust the whole table,
|
|
40
|
+
* and `--json` still carries the raw epoch for anything that needs to compute.
|
|
41
|
+
*/
|
|
42
|
+
export declare function timestamp(ms: number): string;
|
|
43
|
+
/**
|
|
44
|
+
* The version loop, in the order it is used. This is the thing campaigns.md
|
|
45
|
+
* says actually earns retention and it is currently something you "discover
|
|
46
|
+
* later" — so it goes directly under the URL, above the ownership story.
|
|
47
|
+
*/
|
|
48
|
+
export declare const LOOP: Array<{
|
|
49
|
+
label: string;
|
|
50
|
+
command: string;
|
|
51
|
+
effect: string;
|
|
52
|
+
}>;
|
|
53
|
+
export interface TailStyle {
|
|
54
|
+
dim(s: string): string;
|
|
55
|
+
bold(s: string): string;
|
|
56
|
+
muted(s: string): string;
|
|
57
|
+
accent(s: string): string;
|
|
58
|
+
ok(s: string): string;
|
|
59
|
+
}
|
|
60
|
+
/**
|
|
61
|
+
* The TTL, and the one command that removes it. Shared by the deploy tail,
|
|
62
|
+
* `flypod update` and `flypod versions` so there is exactly one wording and one
|
|
63
|
+
* width budget to keep, rather than three that drift apart (they had: 82, 118
|
|
64
|
+
* and 63 columns for the same sentence).
|
|
65
|
+
*
|
|
66
|
+
* Empty for a site that doesn't expire — an owned site gets no nag anywhere.
|
|
67
|
+
*/
|
|
68
|
+
export declare function expiryLines(opts: {
|
|
69
|
+
expiresAt: number | null;
|
|
70
|
+
now?: number;
|
|
71
|
+
style?: TailStyle;
|
|
72
|
+
/**
|
|
73
|
+
* Name `flypod versions` as the way to see this date again. Off inside
|
|
74
|
+
* `flypod versions` itself, which would be telling someone to run the command
|
|
75
|
+
* they are already looking at the output of.
|
|
76
|
+
*/
|
|
77
|
+
check?: boolean;
|
|
78
|
+
}): string[];
|
|
79
|
+
export interface TailOptions {
|
|
80
|
+
/** Epoch ms the site expires, or null when it is owned/permanent. */
|
|
81
|
+
expiresAt: number | null;
|
|
82
|
+
/** Set when the deploy was attributed to an account. */
|
|
83
|
+
owned: boolean;
|
|
84
|
+
now?: number;
|
|
85
|
+
style?: TailStyle;
|
|
86
|
+
}
|
|
87
|
+
/**
|
|
88
|
+
* The lines printed under the live URL, in order. Returned as an array so the
|
|
89
|
+
* test suite asserts on content rather than on one giant template string.
|
|
90
|
+
*
|
|
91
|
+
* Ordering is the argument: the second deploy is the north star, so the loop
|
|
92
|
+
* comes first. Ownership is the safety valve (campaigns.md message hierarchy
|
|
93
|
+
* step 4) and comes after it — an upgrade offered at the end, never a gate at
|
|
94
|
+
* the start.
|
|
95
|
+
*/
|
|
96
|
+
export declare function deployTail(opts: TailOptions): string[];
|
|
97
|
+
/**
|
|
98
|
+
* What `flypod update` says after the second deploy — the moment someone
|
|
99
|
+
* stopped trying flypod and started using it.
|
|
100
|
+
*
|
|
101
|
+
* Same rows as the deploy tail, minus the one they just ran. `flypod versions`
|
|
102
|
+
* is named on the expiry line rather than given a row of its own: it does
|
|
103
|
+
* double duty there as both the history command and the way to re-check the
|
|
104
|
+
* date, which is a row saved and nothing lost.
|
|
105
|
+
*/
|
|
106
|
+
export declare function updateTail(opts: {
|
|
107
|
+
versionId: string;
|
|
108
|
+
url: string;
|
|
109
|
+
expiresAt: number | null;
|
|
110
|
+
/** Whatever survived the deploy, as the server reported it. */
|
|
111
|
+
warnings?: Array<{
|
|
112
|
+
code: string;
|
|
113
|
+
fix_recipe: string;
|
|
114
|
+
}>;
|
|
115
|
+
now?: number;
|
|
116
|
+
style?: TailStyle;
|
|
117
|
+
}): string[];
|
|
118
|
+
/** What `flypod rollback` says. Lean on purpose: this is a recovery action, not
|
|
119
|
+
* a place to sell anything. The URL is accented, as everywhere else. */
|
|
120
|
+
export declare function rollbackTail(opts: {
|
|
121
|
+
versionId: string;
|
|
122
|
+
url: string;
|
|
123
|
+
style?: TailStyle;
|
|
124
|
+
}): string[];
|
|
125
|
+
/**
|
|
126
|
+
* What to say when `flypod` is run in a folder that already deploys somewhere.
|
|
127
|
+
*
|
|
128
|
+
* This is the single most expensive misunderstanding in the product: re-running
|
|
129
|
+
* `flypod` makes a *new* site at a *new* URL and silently repoints the folder,
|
|
130
|
+
* orphaning the old one. Every such run is a fresh anonymous id server-side, so
|
|
131
|
+
* it reads as another one-and-done first-deployer rather than a second deploy
|
|
132
|
+
* by the same person.
|
|
133
|
+
*
|
|
134
|
+
* It is a notice, never a prompt — the deploy proceeds exactly as before.
|
|
135
|
+
*/
|
|
136
|
+
export declare function relinkNotice(prev: {
|
|
137
|
+
site_id: string;
|
|
138
|
+
url: string;
|
|
139
|
+
}, style?: TailStyle): string[];
|
|
140
|
+
export interface AgentNextOptions {
|
|
141
|
+
siteId: string;
|
|
142
|
+
expiresAt: number | null;
|
|
143
|
+
owned: boolean;
|
|
144
|
+
/**
|
|
145
|
+
* Whether the folder → site link was written. Defaults to true. When the
|
|
146
|
+
* config dir was not writable, the bare `flypod update` the note recommends
|
|
147
|
+
* would fail with `no_site` and an agent's natural recovery is a second
|
|
148
|
+
* deploy — so every `next` command carries `--site <id>` instead.
|
|
149
|
+
*/
|
|
150
|
+
linkSaved?: boolean;
|
|
151
|
+
now?: number;
|
|
152
|
+
}
|
|
153
|
+
/**
|
|
154
|
+
* The machine-readable half of everything above. Agents do not read stderr, so
|
|
155
|
+
* without this the 43%+ of deploys that come from a library or a skill never
|
|
156
|
+
* learn that `flypod update` exists — they re-run the deploy verb and make a
|
|
157
|
+
* second site, which is precisely the observed failure.
|
|
158
|
+
*
|
|
159
|
+
* Keys are stable and the values are literal commands, not prose: an agent can
|
|
160
|
+
* execute `next.update` verbatim.
|
|
161
|
+
*/
|
|
162
|
+
export declare function agentNext(opts: AgentNextOptions): Record<string, unknown>;
|
package/dist/src/cli.d.ts
CHANGED
|
@@ -70,3 +70,19 @@ export interface DeployOptions {
|
|
|
70
70
|
* session or ambient env vars the caller didn't pass in `opts`.
|
|
71
71
|
*/
|
|
72
72
|
export declare function deploySite(opts: DeployOptions): Promise<DeployResult>;
|
|
73
|
+
/**
|
|
74
|
+
* A deploy the server refused. Carries the status and whatever the server
|
|
75
|
+
* said, so a caller can tell a rate limit (retry later) from a blocked upload
|
|
76
|
+
* (do not retry) — `deploy failed: 429` on its own could not.
|
|
77
|
+
*/
|
|
78
|
+
export declare class DeployError extends Error {
|
|
79
|
+
readonly status: number;
|
|
80
|
+
/** The response body, verbatim (JSON or plain text), for diagnostics. */
|
|
81
|
+
readonly body: string;
|
|
82
|
+
/** The server's stable error code, when its body carried one. */
|
|
83
|
+
readonly code: string | undefined;
|
|
84
|
+
constructor(status: number, body: string, code?: string);
|
|
85
|
+
static fromResponse(res: Response): Promise<DeployError>;
|
|
86
|
+
/** Rebuild a `Response` so the CLI's classifier can treat it like any other failure. */
|
|
87
|
+
toResponse(): Response;
|
|
88
|
+
}
|
package/dist/src/cli.js
CHANGED
|
@@ -1,12 +1,14 @@
|
|
|
1
1
|
import {
|
|
2
2
|
BUILD_DIR_CANDIDATES,
|
|
3
|
+
DeployError,
|
|
3
4
|
collectDist,
|
|
4
5
|
deploySite,
|
|
5
6
|
resolveDeployDir
|
|
6
|
-
} from "../cli-
|
|
7
|
+
} from "../cli-198a0gkx.js";
|
|
7
8
|
export {
|
|
8
|
-
|
|
9
|
-
|
|
9
|
+
BUILD_DIR_CANDIDATES,
|
|
10
|
+
DeployError,
|
|
10
11
|
collectDist,
|
|
11
|
-
|
|
12
|
+
deploySite,
|
|
13
|
+
resolveDeployDir
|
|
12
14
|
};
|
|
@@ -7,10 +7,35 @@ export declare const SOURCE_HEADER = "x-flypod-source";
|
|
|
7
7
|
* it. It is a device id we minted, not PII — no IP, no user agent.
|
|
8
8
|
*/
|
|
9
9
|
export declare const ANON_ID_HEADER = "x-flypod-anon-id";
|
|
10
|
-
|
|
10
|
+
/**
|
|
11
|
+
* `ci` is ours, and it exists so the growth report can subtract us from our own
|
|
12
|
+
* numbers. Set `FLYPOD_SOURCE=ci` in anything that deploys on our behalf — a
|
|
13
|
+
* workflow, a load test, a demo recording — and the weekly report excludes it
|
|
14
|
+
* from the north star and from C1/C3/C5 instead of counting us as builders.
|
|
15
|
+
* Without this value in the allowlist the header coerces to `unknown` and stays
|
|
16
|
+
* in the denominator, which is the silent version of the same mistake.
|
|
17
|
+
*/
|
|
18
|
+
export declare const DEPLOY_SOURCES: readonly ["cli", "browser", "library", "skill", "ci", "unknown"];
|
|
11
19
|
export type DeploySource = (typeof DEPLOY_SOURCES)[number];
|
|
12
20
|
/** Validate a client-supplied source header; anything unrecognized is `unknown`. */
|
|
13
21
|
export declare function coerceSource(value: string | null | undefined): DeploySource;
|
|
22
|
+
/**
|
|
23
|
+
* What kind of program made the request, as coarsely as is still useful.
|
|
24
|
+
*
|
|
25
|
+
* `source` says which of *our* surfaces deployed. A request that carries no
|
|
26
|
+
* source header reads `unknown`, and that is everyone who calls the HTTP API
|
|
27
|
+
* directly — in the week of 2026-09-28 it was ten of fifteen deploys, and
|
|
28
|
+
* nothing on the event could say whether they were one script or ten people
|
|
29
|
+
* following the `curl` examples in the docs.
|
|
30
|
+
*
|
|
31
|
+
* The user agent itself is never recorded: it carries versions, platforms and
|
|
32
|
+
* sometimes hostnames. It is reduced here to one of nine fixed words, which is
|
|
33
|
+
* the whole of what leaves this function.
|
|
34
|
+
*/
|
|
35
|
+
export declare const CLIENT_FAMILIES: readonly ["curl", "node", "bun", "deno", "python", "go", "browser", "other", "none"];
|
|
36
|
+
export type ClientFamily = (typeof CLIENT_FAMILIES)[number];
|
|
37
|
+
/** Reduce a `User-Agent` header to a `ClientFamily`. Never returns the input. */
|
|
38
|
+
export declare function clientFamily(userAgent: string | null | undefined): ClientFamily;
|
|
14
39
|
/**
|
|
15
40
|
* Validate a client-supplied anon id. PostHog device ids are UUID-shaped, so a
|
|
16
41
|
* conservative charset + length cap is enough to keep anything else (a stray
|
|
@@ -0,0 +1,25 @@
|
|
|
1
|
+
/**
|
|
2
|
+
* Pack a files map into the archive we upload.
|
|
3
|
+
*
|
|
4
|
+
* **Stored, not deflated, and that is deliberate.** The API runs on Cloudflare
|
|
5
|
+
* Workers Free, which gives a request 10 ms of CPU. Measured on the deployed
|
|
6
|
+
* Worker with `scripts/worker-cpu.ts`, for the same 20-file, 489 KB `dist/`:
|
|
7
|
+
*
|
|
8
|
+
* | archive | wire | CPU per deploy | over the 10 ms budget |
|
|
9
|
+
* |----------|--------|----------------|-----------------------|
|
|
10
|
+
* | deflated | 313 KB | 27.8 ms | 8 of 21 |
|
|
11
|
+
* | stored | 491 KB | 1.0 ms | 0 of 20 |
|
|
12
|
+
*
|
|
13
|
+
* Inflating in the isolate is the entire deploy budget and then some; reading
|
|
14
|
+
* a stored entry is a subarray onto bytes already in memory. Before this, a
|
|
15
|
+
* sustained 1 deploy/second killed 88% of deploys with `exceededCpu`.
|
|
16
|
+
*
|
|
17
|
+
* The cost is real and lands on the user: about 57% more to upload, which on a
|
|
18
|
+
* slow uplink is a slower deploy. We take it because CPU is the scarce,
|
|
19
|
+
* shared, cliff-edged resource and bandwidth is none of those things. On a
|
|
20
|
+
* paid Workers plan the trade reverses and this should go back to `zipSync`.
|
|
21
|
+
*
|
|
22
|
+
* The server reads both — a deflated archive from any already-published CLI
|
|
23
|
+
* still deploys, it just costs what it always did.
|
|
24
|
+
*/
|
|
25
|
+
export declare function packDeploy(files: Record<string, Uint8Array>): Uint8Array;
|
package/package.json
CHANGED
|
@@ -1,11 +1,11 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "flypod",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.10.0",
|
|
4
4
|
"description": "Zero-auth deploy primitive. Turns any folder into a live URL in one command. For AI agents and humans.",
|
|
5
5
|
"module": "./dist/src/cli.js",
|
|
6
6
|
"types": "./dist/src/cli.d.ts",
|
|
7
7
|
"type": "module",
|
|
8
|
-
"license": "
|
|
8
|
+
"license": "SEE LICENSE IN LICENSE",
|
|
9
9
|
"exports": {
|
|
10
10
|
".": {
|
|
11
11
|
"types": "./dist/src/cli.d.ts",
|
|
@@ -36,12 +36,11 @@
|
|
|
36
36
|
"scripts": {
|
|
37
37
|
"build": "rm -rf dist && bun build src/cli.ts bin/deploy.ts --outdir dist --target node --splitting && tsc -p tsconfig.build.json",
|
|
38
38
|
"prepublishOnly": "bun run build",
|
|
39
|
-
"test": "bun
|
|
40
|
-
"test:unit": "bun test --test-name-pattern='^(?!.*BDD).*' $(find test -name '*.test.ts' ! -path 'test/comments/bdd.test.ts')",
|
|
41
|
-
"test:bdd": "bun test test/comments/bdd.test.ts",
|
|
39
|
+
"test": "bun test",
|
|
42
40
|
"typecheck": "tsc --noEmit",
|
|
43
41
|
"build:account-page": "bun scripts/build-account-page.ts",
|
|
44
42
|
"deploy": "wrangler deploy",
|
|
43
|
+
"loadtest": "bun scripts/load-test.ts",
|
|
45
44
|
"dev": "bun --hot index.ts"
|
|
46
45
|
},
|
|
47
46
|
"dependencies": {
|
|
@@ -50,7 +49,7 @@
|
|
|
50
49
|
"devDependencies": {
|
|
51
50
|
"@flypod/comments": "workspace:*",
|
|
52
51
|
"@libsql/client": "^0.17.3",
|
|
53
|
-
"@types/bun": "
|
|
52
|
+
"@types/bun": "^1.4.1",
|
|
54
53
|
"better-auth": "1.6.14",
|
|
55
54
|
"drizzle-orm": "^0.45.2",
|
|
56
55
|
"hono": "^4.12.34",
|