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

How to quickly update project dependencies of an outdated project #571

Closed
vibhanshuc opened this Issue Feb 4, 2019 · 4 comments

Comments

Projects
None yet
5 participants
@vibhanshuc
Copy link

vibhanshuc commented Feb 4, 2019

If I have a react project which has a lot of devDependencies and dependencies and I haven't worked on that project for a while.
Naturally these dependencies will receive some updated version. Now when I have to start working on the project, I would want to use updated versions of the dependencies. I have to first check which all dependencies have received updates and then go on to check which one have received what changes by going into the CHANGELOG of each dependency's github repository. Then we have to make changes in our code wherever applicable.

Is there some other way using which can help me make this process quick.

Consider this react project as standalone application rather than a library.

@artivilla

This comment has been minimized.

Copy link

artivilla commented Feb 18, 2019

Integrations like https://greenkeeper.io/ help keep your dependencies updated if a new version is published by the author rather than running npm outdated every few months. With some minimal setup, provided you have tests in place this is much easier to maintain than going and updating 20+ dependencies.

Given minor and patch updates can still cause havoc, I'd still be cautious.

You can also start with udpating only patch/minor versions and test if your application works. If so then, go through the docs for major breaking updates and make the necessary changes.

Obviously, this is Kent's ama so I'll let him answer.

@kevinwolfcr

This comment has been minimized.

Copy link

kevinwolfcr commented Mar 6, 2019

I can recommend running yarn upgrade-interactive --latest, since it will let me selectively upgrade packages and also persist to package.json and yarn.lock files.

@Apidcloud

This comment has been minimized.

Copy link

Apidcloud commented Mar 10, 2019

I also use yarn, but if you are using npmyou can use something similar, npm-upgrade: https://www.npmjs.com/package/npm-upgrade

@kentcdodds

This comment has been minimized.

Copy link
Owner

kentcdodds commented Mar 22, 2019

I answered this today on 3 minutes with Kent :) https://www.briefs.fm/3-minutes-with-kent/101

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.