#Plugin(s) project set up
5 messages · Page 1 of 1 (latest)
It's meant as one big monorepo as a whole. Your build will build all of those packages at once
What if it's for a big organization. In spotify does everyone put their plugins to the same backstage repo?
Yes. It's just super convenient and speeds things up for everyone. You don't have to though. You can have one part of the org with their own monorepo and publishing their packages into an internal NPM for example, and then a "master" repository that has external dependencies on those packages
But really, those who develop in that external repo are likely to be frustrated and having to ask the owners of the master repo all the time "hey can you please update and deploy, we want to release our changes because there was a bug and our users are complaining" etc. A lot of companies feel it's not worth the separation.