@executor-js/cli 0.2.1 → 0.2.3

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/README.md CHANGED
@@ -1,57 +1,7 @@
1
1
  # @executor-js/cli
2
2
 
3
- Command-line tool for `@executor-js/sdk` projects. Generates Drizzle schema files from the plugins registered in your `executor.config.ts` so database migrations stay in sync with the executor you actually run.
3
+ Minimal command-line entrypoint for Executor projects.
4
4
 
5
- ## Install
6
-
7
- ```sh
8
- bun add -d @executor-js/cli
9
- # or
10
- npm install --save-dev @executor-js/cli
11
- ```
12
-
13
- The binary is installed as `executor`.
14
-
15
- ## Quick start
16
-
17
- Create an `executor.config.ts` alongside your app code:
18
-
19
- ```ts
20
- import { defineExecutorConfig } from "@executor-js/sdk";
21
- import { mcpPlugin } from "@executor-js/plugin-mcp";
22
- import { openApiPlugin } from "@executor-js/plugin-openapi";
23
-
24
- export default defineExecutorConfig({
25
- dialect: "pg",
26
- plugins: [mcpPlugin(), openApiPlugin()],
27
- });
28
- ```
29
-
30
- Then generate a Drizzle schema from it:
31
-
32
- ```sh
33
- bunx executor generate --output ./src/db/executor-schema.ts
34
- # or
35
- npx executor generate --output ./src/db/executor-schema.ts
36
- ```
37
-
38
- The generator walks every plugin in the config, collects their schema contributions, and emits a single Drizzle schema file ready to hand to `drizzle-kit`.
39
-
40
- ## Commands
41
-
42
- ```
43
- executor generate [options]
44
- --cwd <dir> Project directory (default: cwd)
45
- --config <path> Path to executor.config.ts (default: auto-discover)
46
- --output <path> Output file for the generated schema
47
- ```
48
-
49
- Run `executor --help` to see the current command list.
50
-
51
- ## Status
52
-
53
- Pre-`1.0`. APIs may still change between beta releases. Part of the [executor monorepo](https://github.com/RhysSullivan/executor).
54
-
55
- ## License
56
-
57
- MIT
5
+ Schema generation and migrations are owned by FumaDB now. Hosts should build a
6
+ FumaDB client from `collectTables(plugins)` and use FumaDB's adapter/migrator
7
+ APIs directly instead of generating Executor-specific storage adapters.
@@ -0,0 +1,2 @@
1
+ import { Command } from "commander";
2
+ export declare const schema: Command;