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
Vladislavs-MacBook-Pro:udoma personal$ npm upgrade
@ng-seed/universal@0.4.0-beta.2 /Users/personal/code/udoma
├── UNMET PEER DEPENDENCY @ngx-cache/core@0.4.0-beta.2
├── gulp@4.0.0-alpha.2 (git://github.com/gulpjs/gulp.git#38246c3f8b6dbb8d4ef657183e92d90c8299e22f)
├── uglify-js@2.8.22 (git://github.com/mishoo/UglifyJS2.git#278577f3cb75e72320564805ee91be63e5f9c806)
└── UNMET PEER DEPENDENCY webpack@3.3.0
npm WARN @ngtools/webpack@1.3.3 requires a peer of webpack@^2.2.0 but none was installed.
npm WARN @ngx-cache/fs-storage@0.4.0-beta.2 requires a peer of @ngx-cache/core@0.4.0-beta.1 but none was installed.
npm WARN extract-text-webpack-plugin@2.1.2 requires a peer of webpack@^2.2.0 but none was installed.
Expected/desired behavior
Npm update successful
Minimal reproduction of the problem with instructions
Clone repo
Run npm update
What is the motivation / use case for changing the behavior?
So I can use the repo with the latest versions of node modules, install other node modules
Please tell us about your environment:
OSX
Node (for AoT issues):node --version = v6.10.3
The text was updated successfully, but these errors were encountered:
fulls1z3
changed the title
Unable to update dependacies
[invalid] unable to update dependacies
Jul 29, 2017
@vlados actually npm updates the deps, but displays a warning if there're any unmet peer dependencies. So, things should work fine (because higher versions of those deps are already included in node_modules directory).
Current behavior
When run
npm update
I am gettingExpected/desired behavior
Npm update successful
Minimal reproduction of the problem with instructions
npm update
What is the motivation / use case for changing the behavior?
So I can use the repo with the latest versions of node modules, install other node modules
Please tell us about your environment:
OSX
Node (for AoT issues):
node --version
= v6.10.3The text was updated successfully, but these errors were encountered: