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 package.json (1 of 37 files). Show all

Unified · Split

package.json+1−1
@@ -36,7 +36,7 @@ · 35 unmodified lines
3636 "test": "turbo run test --filter=!@executor-js/e2e",
3737 "test:e2e": "bun run --cwd e2e test",
3838 "test:release:bootstrap": "vitest run tests/release-bootstrap-smoke.test.ts",
39− "build:packages": "bun run --filter='fumadb' build && bun run --filter='@executor-js/codemode-core' build && bun run --filter='@executor-js/runtime-quickjs' build && bun run --filter='@executor-js/sdk' build && bun run --filter='@executor-js/config' build && bun run --filter='@executor-js/execution' build && bun run --filter='@executor-js/cli' build && bun run --filter='@executor-js/plugin-*' build",
39+ "build:packages": "bun run --filter='@executor-js/fumadb' build && bun run --filter='@executor-js/codemode-core' build && bun run --filter='@executor-js/runtime-quickjs' build && bun run --filter='@executor-js/sdk' build && bun run --filter='@executor-js/config' build && bun run --filter='@executor-js/execution' build && bun run --filter='@executor-js/cli' build && bun run --filter='@executor-js/plugin-*' build",
4040 "typecheck": "turbo run typecheck",
4141 "typecheck:slow": "turbo run typecheck:slow",
4242 "ci": "bun run lint && bun run typecheck && bun run test",