@walkeros/cli 4.8.2 → 4.8.3-next-1793115089237

package/dist/examples/shared/README.md

@@ -20,3 +20,7 @@ walkeros bundle packages/cli/examples/flow-complete.json -f web -o packages/cli/
 walkeros bundle packages/cli/examples/flow-complete.json -f server -o dist/server.mjs
 runneros start dist/server.mjs -p 8080 --env-file .env
 ```
+
+- `runneros` refuses an `.env` that group or other can read
+  (`Refusing to load env file ".env": it is readable by group or other`);
+  restrict it with `chmod 600 .env`.

package/dist/index.d.ts

@@ -1,9 +1,49 @@
-import { Flow, PreviewKey, Elb, Simulation, Ingest, WalkerOS, ObserveWeb, MoinTarget } from '@walkeros/core';
+import { Flow, StepType, PreviewKey, Elb, Simulation, Ingest, WalkerOS, ObserveWeb, MoinTarget } from '@walkeros/core';
 export { Flow } from '@walkeros/core';
 import { BuildOptions as BuildOptions$1 } from 'esbuild';
 import { z, ValidateResult as ValidateResult$1, ValidationError as ValidationError$1, ValidationWarning as ValidationWarning$1, ValidationType } from '@walkeros/core/dev';
 export { ValidationType, validateFlowStructure } from '@walkeros/core/dev';
 
+/**
+ * Shared resolver for the export name to import from a flow component's
+ * package.
+ *
+ * Both `walkeros bundle` and `walkeros setup` need to know which named export
+ * (or default) to pull off a package referenced by a flow component. The
+ * precedence chain is:
+ *
+ * 1. `flow.<kind>.<id>.import` if set (named export selector at the step).
+ * 2. `flow.config.bundle.packages[<package>].imports[0]` if set.
+ * 3. Otherwise undefined; the caller falls back to the package's `default`
+ *    export.
+ *
+ * This lives in `cli/src/core/` so both `commands/bundle/*` and
+ * `commands/setup/*` import the same function. Duplicating the chain is how
+ * setup ended up out of sync with bundle (Bug F: `setup destination.pubsub`
+ * routed through BigQuery's setup because it ignored the `code` field and
+ * always grabbed `mod.default`).
+ */
+
+type ComponentKind = StepType;
+type ResolveSource = 'import' | 'imports' | 'default';
+interface ResolvedExportName {
+    /**
+     * The named export to pull off the imported module, or `undefined` to
+     * indicate the caller should use the package's `default` export.
+     */
+    exportName: string | undefined;
+    /** Which precedence step produced the result (useful for diagnostics). */
+    source: ResolveSource;
+}
+/**
+ * Resolve the export name to import for a flow component's package.
+ *
+ * See module docs for the precedence chain. Inline code (`code` is an object)
+ * doesn't enter this resolver at all — setup rejects inline code at a higher
+ * layer.
+ */
+declare function resolveExportName(flow: Flow, kind: ComponentKind, id: string): ResolvedExportName;
+
 /**
  * CLI Build Configuration
  *
@@ -1510,46 +1550,6 @@ declare function loadJsonConfig<T>(configPath: string): Promise<T>;
  */
 declare function collectKnownSecrets(flow: Flow.Json, env?: NodeJS.ProcessEnv): string[];
 
-/**
- * Shared resolver for the export name to import from a flow component's
- * package.
- *
- * Both `walkeros bundle` and `walkeros setup` need to know which named export
- * (or default) to pull off a package referenced by a flow component. The
- * precedence chain is:
- *
- * 1. `flow.<kind>.<id>.import` if set (named export selector at the step).
- * 2. `flow.config.bundle.packages[<package>].imports[0]` if set.
- * 3. Otherwise undefined; the caller falls back to the package's `default`
- *    export.
- *
- * This lives in `cli/src/core/` so both `commands/bundle/*` and
- * `commands/setup/*` import the same function. Duplicating the chain is how
- * setup ended up out of sync with bundle (Bug F: `setup destination.pubsub`
- * routed through BigQuery's setup because it ignored the `code` field and
- * always grabbed `mod.default`).
- */
-
-type ComponentKind = 'source' | 'transformer' | 'destination' | 'store';
-type ResolveSource = 'import' | 'imports' | 'default';
-interface ResolvedExportName {
-    /**
-     * The named export to pull off the imported module, or `undefined` to
-     * indicate the caller should use the package's `default` export.
-     */
-    exportName: string | undefined;
-    /** Which precedence step produced the result (useful for diagnostics). */
-    source: ResolveSource;
-}
-/**
- * Resolve the export name to import for a flow component's package.
- *
- * See module docs for the precedence chain. Inline code (`code` is an object)
- * doesn't enter this resolver at all — setup rejects inline code at a higher
- * layer.
- */
-declare function resolveExportName(flow: Flow, kind: ComponentKind, id: string): ResolvedExportName;
-
 /**
  * Selects the dev examples of one export from a package's awaited `/dev`
  * module.