Fix published package imports (#934)

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.

Rhys Sullivan committed 5 months ago

Commit 17174c41 parent 2c8f2d037 files · +89 −80Browse files

Showing the changes to packages/kernel/runtime-dynamic-worker/src (1 of 37 files). Show all

Unified · Split

packages/kernel/runtime-dynamic-worker/src/integration.test.ts+6−3

 import * as Layer from "effect/Layer";
 import * as Predicate from "effect/Predicate";
 import { HttpClient, HttpClientResponse, type HttpClientRequest } from "effect/unstable/http";
-import { fumadb } from "fumadb";
+import { fumadb } from "@executor-js/fumadb";
-import { createDrizzleRuntimeSchemaFromTables, drizzleAdapter } from "fumadb/adapters/drizzle";
+import {
-import { schema as fumaSchema } from "fumadb/schema";
+  createDrizzleRuntimeSchemaFromTables,
+  drizzleAdapter,
+} from "@executor-js/fumadb/adapters/drizzle";
+import { schema as fumaSchema } from "@executor-js/fumadb/schema";
 import postgres from "postgres";
 import {