The vendored fumadb fork was published under the bare name "fumadb", which collides with the upstream npm package — so a published @executor-js/sdk would resolve the wrong dependency. Scope the package to @executor-js/fumadb and update every workspace dependency, import specifier, and the build filter to match.
Showing the changes to packages/core/cli/src (1 of 37 files). Show all
Unified · Split
| @@ -36,9 +36,9 @@ const schemaGenerateAction = async (opts: SchemaGenerateOptions) => { · 35 unmodified lines | |||
| 36 | } | 36 | } |
| 37 | 37 | ||
| 38 | const [{ fumadb }, { drizzleAdapter }, { schema: fumaSchema }] = await Promise.all([ | 38 | const [{ fumadb }, { drizzleAdapter }, { schema: fumaSchema }] = await Promise.all([ |
| 39 | import("fumadb"), | 39 | import("@executor-js/fumadb"), |
| 40 | import("fumadb/adapters/drizzle"), | 40 | import("@executor-js/fumadb/adapters/drizzle"), |
| 41 | import("fumadb/schema"), | 41 | import("@executor-js/fumadb/schema"), |
| 42 | ]); | 42 | ]); |
| 43 | 43 | ||
| 44 | const schema = fumaSchema({ | 44 | const schema = fumaSchema({ |