Closed ctaepper closed 3 years ago
We tried it earlier on and it ended up being too problematic because of devkit introducing breaking changes in patch releases. It's more stable now, so we might try it again.
The problem you are you having now is that you have two versions of the packages, so two versions of the same class. You could set up your workspace to have a single version of the package (see here: https://github.com/nrwl/nx/issues/2458). This will likely resolve your issue.
This issue has been automatically marked as stale because it hasn't had any recent activity. It will be closed in 14 days if no further activity occurs. If we missed this issue please reply to keep it active. Thanks for being a part of the Nx community! 🙏
This issue has been closed for more than 30 days. If this issue is still occuring, please open a new issue with more recent context.
Please make sure you have read the submission guidelines before posting an issue
Expected Behavior
For @nrwl packages to use the projects version of
@angular-devkit
dependenciesCurrent Behavior
@angular-devkit
dependencies are pinned to8.3.23
, which leads to type mismatches if the project has another version installedSteps to Reproduce
npx create-nx-plugin@8 my-org --pluginName my-plugin
npm install @angular-devkit/{core,schematics}@8.3.25
to simulate existing dependenciesng build my-plugin
<-- breaksContext
I try to use the nx-plugin package to create my own plugins in an existing ng turned nx workspace. So I have angular cli and angular-devkit deps installed in the project. Also, in my case it is an angular 8 project with nx 8.12.10 dependencies
Failure Logs