Managing Version Consistency for Effect in a Monorepo Setup
I see a couple discussions for issues with version mismatches with effect in a monorepo. Is there any advice for how to setup my package.jsons so the same effect version is used?
- schema
- 🚀-effect
I have something like:
-
-
-
And
-
-
-
Each package in
My guess is that each "app" should have the direct dependency on effect, @effect/schema, etc
And, each "package" should have peer dependencies. Is that good enough?
Does anything change if I'm using bun for workspaces?
- schema
- 🚀-effect
I have something like:
-
apps/server-
apps/editor-webui-
apps/seo-cms-webuiAnd
-
packages/helpers-
packages/database-
packages/environmentsEach package in
appsMy guess is that each "app" should have the direct dependency on effect, @effect/schema, etc
And, each "package" should have peer dependencies. Is that good enough?
Does anything change if I'm using bun for workspaces?
Similar Threads
Was this page helpful?
