Is your feature request related to a problem? Please describe.
Consider a project with one "core" package that's private and not published, and several "native binary" packages. If we update the "core" we want to publish a new version of the native packages. We do not want to list core as a dependency of "native" because it's private and shouldn't be downloaded by consumers. It should be a devDependency.
Describe the solution you'd like
Do NOT strip private packages in getDependents and getTopologicalSort in @monodeploy/dependencies. Remove all "private" package filtering through monodeploy and move it to the generation of the "updated packages" / changeset / publish.
Is your feature request related to a problem? Please describe.
Consider a project with one "core" package that's private and not published, and several "native binary" packages. If we update the "core" we want to publish a new version of the native packages. We do not want to list core as a dependency of "native" because it's private and shouldn't be downloaded by consumers. It should be a devDependency.
Describe the solution you'd like
Do NOT strip private packages in getDependents and getTopologicalSort in @monodeploy/dependencies. Remove all "private" package filtering through monodeploy and move it to the generation of the "updated packages" / changeset / publish.