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

@@ -21,9 +21,12 @@ import * as Effect from "effect/Effect"; · 20 unmodified lines
21	21	import * as Layer from "effect/Layer";
22	22	import * as Predicate from "effect/Predicate";
23	23	import { HttpClient, HttpClientResponse, type HttpClientRequest } from "effect/unstable/http";
24		−import { fumadb } from "fumadb";
25		−import { createDrizzleRuntimeSchemaFromTables, drizzleAdapter } from "fumadb/adapters/drizzle";
26		−import { schema as fumaSchema } from "fumadb/schema";
	24	+import { fumadb } from "@executor-js/fumadb";
	25	+import {
	26	+ createDrizzleRuntimeSchemaFromTables,
	27	+ drizzleAdapter,
	28	+} from "@executor-js/fumadb/adapters/drizzle";
	29	+import { schema as fumaSchema } from "@executor-js/fumadb/schema";
27	30	import postgres from "postgres";
28	31
29	32	import {