У меня есть проект angular, назовем его Project-A, который можно развернуть в производство. Project-A имеет много дочерних angular библиотек, которые загружаются лениво и включены в его пакет. json в качестве зависимости. Как это: В пакете. json:
"@common-project-B": "1.2.0",
"@project-C": "0.2.0",
"@project-D": "0.12.0"
}```
The library(common-project-B) is also included in all the other libraries(project-C and project-D) because of the common components/directives/pipes in it.
My problem is Even though I'm including different versions of **common-project-B** in child libraries (project-C and project-D) whatever version is in project-A(parent app) is taking precedence.
Ex: Project-C has common-project-B version as 0.2.1 and project-D has common-project-B version as 0.2.2
When project-A gets deployed project-C and project-D are using common-project-B version as 0.2.0 which was included in project-A(parent app).
Can someone help me with this how to use different versions of common library in child libraries without getting overridden by the version in parent angular application?