Replies: 1 comment 1 reply
-
To set expectations here, this has unrelated to turborepo. Turborepo does not manage your dependencies or publishing your packages. That said, this is a tricky problem with Monorepos and @anthonyshew is working on guides that will help set some blueprints!
I'm assuming you mean usage of the public (
This seems right to me also! I think the easiest way to achieve this is by bundling |
Beta Was this translation helpful? Give feedback.
-
Summary
Is it possible to release packages that depend on internal packages in their
dependencies
?Additional information
Imagine the following structure:
Let's say we want to publish
a-public
, a package containing code fromb-internal
as it is installed ina-public
'sdependencies
:Is this a supported flow? We tried achieving this and while the build is not failing, the usage fails since the imports
import { Thing } from "@repo/b-internal";
are failing for referencing a non-existent import.Ideally, there would be a flow that outputs
@repo/b-internal
to thenode_modules
of the@repo/a-external
package.What are we missing?
Beta Was this translation helpful? Give feedback.
All reactions