You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 11, 2022. It is now read-only.
Lets say I have an angular 2 project which was created and managed with Angular CLI 1.0.0 and for some reason That Angular CLI project has been updated to 2.0.0. This updated packages do everything based on Angular 4, which is problem for our older project. So have these global CLI's based on project would help us manage that.
What's the feature?
What problem is the feature intended to solve?
Lets say I have an
angular 2
project which was created and managed withAngular CLI 1.0.0
and for some reasonThat Angular CLI project
has beenupdated to 2.0.0
. This updated packages do everything based onAngular 4
, which is problem for our older project. So have these global CLI's based on project would help us manage that.Following article have also tried to explain this pain (https://www.sitepoint.com/solve-global-npm-module-dependency-problem/)
Is the absence of this feature blocking you or your team? If so, how?
Is this feature similar to an existing feature in another tool?
Is this a feature you're prepared to implement, with support from the npm CLI team?
The text was updated successfully, but these errors were encountered: