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
[canary] Update npm dependencies #2691
Comments
The deps project is autogenerated from all possible deps whenever we do a release, so it's only as up-to-date as the last release number. Feel free to submit any update PRs to this repo. |
|
Awesome I understand now and found where I was confused. Thanks for the clarification, I'll get to work! |
|
I would like to claim this if this is still open? |
|
@Phanx091 I don't think it's 'claimed'. This is definitely an issue that should be tackled in pieces. One giant PR that updates all of the out-of-date packages at once can be overwhelming. |
This update is required to allow the generator to work with node v10.0.0 Part of angular-fullstack#2691
Update sequelize to v4 and fix the user model to work with this. Part of angular-fullstack#2691
Update sequelize to v4 and fix the user model to work with this. Part of angular-fullstack#2691
Update sequelize to v4 and fix the user model to work with this. Part of angular-fullstack#2691
Update sequelize to v4 and fix the user model to work with this. Part of angular-fullstack#2691
|
I'm working on that |
|
شكرا علي التوضيح مازلت مبتدأ واحتاج المزيد من التعليم |

Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.

See:
https://david-dm.org/angular-fullstack/angular-fullstack-deps/5.0.0
https://david-dm.org/angular-fullstack/angular-fullstack-deps/5.0.0?type=dev
The text was updated successfully, but these errors were encountered: