Is more granular versioning in a monorepo with a container possible?

[DonaldTaylor]

My team has a monorepo written with React, built with Webpack, and managed with Lerna.

Currently, our monorepo contains a package for each screen in the app, plus a "container" package that is basically a router that lazily serves each screen. The container package has all the screens' packages as dependencies.

The problem we keep running into is that, by Lerna's convention, that container package always contains the latest version of each screen. However, we aren't always ready to take the latest version of each screen to production.

I think we need more granular control over the versions of each screen/dependency.

What would be a better way to handle this? Module Federation? peerDependencies? Are there other alternatives?

Thank you so much!