Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

unable to update dependacies #37

Closed
vlados opened this issue Jul 20, 2017 · 1 comment
Closed

unable to update dependacies #37

vlados opened this issue Jul 20, 2017 · 1 comment
Labels

Comments

@vlados
Copy link

vlados commented Jul 20, 2017

[x] bug report

Current behavior
When run npm update I am getting

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

  1. Clone repo
  2. 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

@fulls1z3 fulls1z3 changed the title Unable to update dependacies [invalid] unable to update dependacies Jul 29, 2017
@fulls1z3 fulls1z3 assigned fulls1z3 and unassigned fulls1z3 Jul 29, 2017
@fulls1z3 fulls1z3 changed the title [invalid] unable to update dependacies [question] unable to update dependacies Jul 29, 2017
@fulls1z3 fulls1z3 self-assigned this Jul 29, 2017
@fulls1z3
Copy link
Owner

@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).

@fulls1z3 fulls1z3 removed their assignment Aug 10, 2017
@fulls1z3 fulls1z3 changed the title [question] unable to update dependacies unable to update dependacies Sep 16, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants