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 apps/cloud/src (2 of 37 files). Show all

Unified · Split

2 files

apps/cloud/src/db/executor-schema.ts +1 −1
apps/cloud/src/db/fuma.ts +3 −3

apps/cloud/src/db/executor-schema.ts+1−1

@@ -8,7 +8,7 @@ import { · 7 unmodified lines
8	8	uniqueIndex,
9	9	bigint,
10	10	} from "drizzle-orm/pg-core";
11		−import { createId } from "fumadb/cuid";
	11	+import { createId } from "@executor-js/fumadb/cuid";
12	12
13	13	export const integration = pgTable(
14	14	"integration",

apps/cloud/src/db/fuma.ts+3−3

@@ -1,7 +1,7 @@
1	1	import { Effect, Layer } from "effect";
2		−import { type FumaDB } from "fumadb";
3		−import { type DrizzleConfig } from "fumadb/adapters/drizzle";
4		−import { type schema as fumaSchema, type RelationsMap } from "fumadb/schema";
	2	+import { type FumaDB } from "@executor-js/fumadb";
	3	+import { type DrizzleConfig } from "@executor-js/fumadb/adapters/drizzle";
	4	+import { type schema as fumaSchema, type RelationsMap } from "@executor-js/fumadb/schema";
5	5
6	6	import {
7	7	createExecutorFumaDb,