Any recommended best practices for having multiple resolves while internally sharing first-party modules/resources. It seems like if you had a project tree with a more general library, you'd have to go update what resolves that general library is discoverable under each time a new project with a different resolve is added. Is that correct?
12/13/2022, 11:25 PM
best practice then is to use multiple resolves sparingly, and probably to track them as tech debt (while migrating repos into a monorepo, etc)
12/13/2022, 11:29 PM
Makes sense. I wasn't sure from the docs if multiple resolves with heavy project sharing was common and just less optimized or less optimized because it's not good repo design.