History

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/core/cli/src (1 of 37 files). Show all

Unified · Split

packages/core/cli/src/commands/schema.ts+3−3
@@ -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({

Keyboard shortcuts

General

Show keyboard shortcuts
?
Focus the current search
/

Issues and pull requests

Open filters
f

Issues, pull requests and Inbox

Select next item
j↓
Select previous item
k↑
Open selected item
Enter
Dismiss filters or clear selection
Esc

Repository code

Go to file
t