One of the tenets of using a monorepo is that the apps and the libraries share the same version. This simplifies the usage and maintenance of the projects. In your case, using a monorepo/workspace may not be a good option.

My team has found that all of apps using the same versioned libraries has simplified our developer workflow. We no longer have to build and publish libraries and manage different version in different applications.

There are many other benefits of a monorepo — however, there are considerations that may not work with all development teams/environments. Would you be able to share the motivation and/or use case for needing to manage different versions?

--

I love tacos, code, jazz, my husky and maybe 3 people in this world...and of course: Angular. Angularlicious podcast — more info at www.AngularArchitecture.com

Love podcasts or audiobooks? Learn on the go with our new app.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Matt Vaughn

Matt Vaughn

I love tacos, code, jazz, my husky and maybe 3 people in this world...and of course: Angular. Angularlicious podcast — more info at www.AngularArchitecture.com