I have an existing project, which has react#15 and all it's dependencies according to that. But now I have to upgrade to react#16 along with it's dependencies. Now, the problem is - there are a lot of dependencies and it is very time consuming to identify version of each dependency.
So, I was wondering if there was a way where I could upgrade the versions of React and it's dependencies mentioned in package.json, without manually modifying the package.json file.
Using npm
Latest version while still respecting the semver in your package.json: npm update <package-name>.
So, if your package.json says "react": "^15.0.0" and you run npm update react your package.json will now say "react": "^15.6.2" (the currently latest version of react 15).
But since you want to go from react 15 to react 16, that won't do.
Latest version regardless of your semver: npm install --save react#latest.
If you want a specific version, you run npm install --save react#<version> e.g. npm install --save react#16.0.0.
https://docs.npmjs.com/cli/install
Using yarn
Latest version while still respecting the semver in your package.json: yarn upgrade react.
Latest version regardless of your semver: yarn upgrade react#latest.
https://yarnpkg.com/lang/en/docs/cli/upgrade/
if you want to update your react and react-dom version in your existing react step then run this command I hope You get the latest version of react and react-dom.
Thanks
npm install react#latest react-dom#latest
I found a nice article here.
All we need to do (for npm, globally) is:
sudo npm install -g npm-check-updates
Then run it like below:
ncu -u
It will show you all dependencies (upgraded) nicely like below:
Upgrading /home/ajay/Documents/react-beast/package.json
[====================] 7/7 100%
#testing-library/user-event ^11.4.2 → ^13.0.16
react ^17.0.1 → ^17.0.2
react-dom ^17.0.1 → ^17.0.2
react-scripts 4.0.1 → 4.0.3
web-vitals ^1.1.0 → ^1.1.1
Try running ncu -u again immediately after above and you will a message like this:
Upgrading /home/ajay/Documents/react-beast/package.json
[====================] 7/7 100%
All dependencies match the latest package versions :)
Do a npm install after that and you should have all the latest versions for all your dependencies for your project.
To me this was the nicest and cleanest solution (well - in most cases) if we need to keep our (npm/React) project - latest and greatest - rather than wasting time on manually updating the versions.
I highly recommend using yarn upgrade-interactive to update React, or any Node project for that matter. It lists your packages, current version, the latest version, an indication of a Minor, Major, or Patch update compared to what you have, plus a link to the respective project.
You run it with yarn upgrade-interactive --latest, check out release notes if you want, go down the list with your arrow keys, choose which packages you want to upgrade by selecting with the space bar, and hit Enter to complete.
Npm-upgrade is ok but not as slick.
Some packages are interdependent and are to be used with the same versions of each other... for example recently had a problem with npm react#16.5.2 and react-dom#16.5.2. I wanted to use a hook but could not so I ran:
npm update react#latest react-dom#latest
this did not work... went into some of the react.js blogs/documentation and found that these particular packages are interdependent and the versions must be the same. To update these:
npm uninstall react
npm uninstall react-dom
npm install react#^16.8.0 react-dom#^16.8.0
And everything worked just fine. Look for stable releases. Read the documentation.
https://reactjs.org/blog/2019/02/06/react-v16.8.0.html
https://reactjs.org/warnings/invalid-hook-call-warning.html
Yes, you can use Yarn or NPM to edit your package.json.
yarn upgrade [package | package#tag | package#version | #scope/]... [--ignore-engines] [--pattern]
Something like:
yarn upgrade react#^16.0.0
Then I'd see what warns or errors out and then run yarn upgrade [package]. No need to edit the file manually. Can do everything from the CLI.
Or just run yarn upgrade to update all packages to latest, probably a bad idea for a large project. APIs may change, things may break.
Alternatively, with NPM run npm outdated to see what packages will be affected. Then
npm update
https://yarnpkg.com/lang/en/docs/cli/upgrade/
https://docs.npmjs.com/getting-started/updating-local-packages
If you want to update react use npx update react on the terminal.
If you want to update any specific version from the package.json you can update the version of the package by doing ==>
yarn add package-name#version-number
or
npm install --save package-name#version-number
If you want to update all packages to the latest version you can run command ==>
npm audit fix --force
you can update all of the dependencies to their latest version by
npm update
You can just use this command
npm install -g create-react-app
if you don't have root user permissions then use this with
sudo npm install -g create-react-app
👇️ with NPM
npm install react#latest react-dom#latest
👇️ only if you use TypeScript
npm install --save-dev #types/react#latest #types/react-dom#latest
------------------------------
👇️ with YARN
yarn add react#latest react-dom#latest
👇️ only if you use TypeScript
yarn add #types/react#latest #types/react-dom#latest --dev
Use this command to update react npm install --save react#16.12.0
Don't forget to change 16.12.0 to the latest version or the version you need to setup.
No need to install react, just do the following command in terminal in Linux/Mac or cmd in Windows:
npx create-react-app my-app
my-app - is a optional name, you may name it whatever you want it to.
It would create the updated template for your next project up and ready!
In terminal run the commands to update the react versions
$npm i react#next react-dom#next
Related
I am running "npx create-react-app experiment" to create a new project and I get this warning. How can I solve it? I have been researching but I get nothing
warning react-scripts > #svgr/webpack > #svgr/plugin-svgo > svgo#1.3.2: This SVGO version is no longer supported. Upgrade to v2.x.x.
I encountered this error while installing dependencies (npm install) for an existing projects
and solved this by installing svgo globally using the command below:
npm install -g svgo
or
npm i -g svgo
hope this helps :)
This below command line helped me when I was creating my react app, try it.
npx create-react-app#latest my-app --use-npm
After a long struggle, I solved the problem and I wanted to share it with you.
Firstly , you should sure updated all npm packages.
For this you can use "npm outdated" command. After that you updated all packages.
second step ,
"npx ncu"
npx ncu stands for "npm check updates". It is a command line tool used to check the outdated dependencies in a Node.js project. This command will list the packages that have newer versions available and allows you to upgrade them to the latest version.
My error after this command is that I need to update #types/react version. It may be different for you, but you need to complete the all updates with the "npx ncu" command.
The easiest way to solve is change the version that "npx ncu" command says, in "package.json" and install npm
sample my case;
#types/react ^18.0.26 → ^18.0.27
hope it helps
As per the title, I don't want to use
npx create-react-app app-name
, because that command installs react (17x) and react-scripts (4.x)
I tried
npm init react-app app-name --scripts-version 3.4.4
, but even though it installs react-scripts (v3.4.4), it still installs react (17.x)
Also, this gives another error:
error : Cannot find module 'cra-template'
EDIT: To clarify, I want to use CRA for sure.
Just not with the current versions of react-17, react-dom-17, and react-scripts-4
I also don't want to waste time installing v17.x, and v4.x, delete them manually, modify package.json to the versions I want, and npm (re-)install. That will work, but it's not the point.
npm init react-app appname --scripts-version <XX.XX.XX>
or sudo npm init react-app appname --scripts-version <XX.XX.XX>
The version number <XX.XX.XX> is for react-scripts to generate a specific react-app based on dependent version of the initiated react-scripts module.
You will have to do some legwork to see which react-scripts version relates to the specific react version when initializing a building of a new react-app.
React Versions: https://reactjs.org/versions/
React Scripts Versions: https://www.npmjs.com/package/react-scripts
If it keeps installing the newest React version
Enter npm uninstall react,
Then npm install react#XX.XX.XX
Where XX.XX.XX is your target number
You will have to do the same for react-dom (same ver# as react) and react-scripts.
Also the #testing-library dependencies may also need uninstalling (There should be 3 on instantiation - they will not work with previous versions (pre-v17 React))
I came across this exact same problem today, and that was my solution.
Trying to add TypeScript to an already created React app via: https://create-react-app.dev/docs/adding-typescript
I do everything bu get the following error when I try and start:
> npx react-scripts start
Could not find a required file.
Name: index.js
Searched in: /home/karl/dev/afry/tmr-client/src
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! tmr-client#0.1.0 start: `npx react-scripts start`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the tmr-client#0.1.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/karl/.npm/_logs/2020-11-06T18_43_02_622Z-debug.log
I renamed the index.js to index.ts as stated in the guide.
I faced the same issue today with create-react-app. The problem is the version of react-scripts as per this Git issue: Git Reference
A quick solution is to update react-scripts. I am using react-scripts version 4.0.3 with no issues.
A safe way to do it based on the documentation: Create React App Docs would be to change the version of react-scripts in the package.json file to the most recent stable version like "react-scripts": "^4.0.3". Then, run npm install from the command line.
TLDR: npm i -D react-scripts#latest
Outdated react-scripts Version
I'm not sure why index.ts isn't working for you, it seems to be supported.
The only explanation is that you're using an outdated version of react-scripts, which you can update by simply running npm i -D react-scripts#latest. More detail from Updating to New Releases:
Create React App is divided into two packages:
create-react-app is a global command-line utility that you use to
create new projects. react-scripts is a development dependency in the
generated projects (including this one). When you run npx
create-react-app my-app it automatically installs the latest version
of Create React App.
If you've previously installed create-react-app globally via npm
install -g create-react-app, please visit Getting Started to learn
about current installation steps.
Create React App creates the project with the latest version of
react-scripts so you’ll get all the new features and improvements in
newly created apps automatically.
To update an existing project to a new version of react-scripts, open
the changelog, find the version you’re currently on (check
package.json in this folder if you’re not sure), and apply the
migration instructions for the newer versions.
In most cases bumping the react-scripts version in package.json and
running npm install (or yarn install) in this folder should be enough,
but it’s good to consult the changelog for potential breaking changes.
We commit to keeping the breaking changes minimal so you can upgrade
react-scripts painlessly.
If this is the issue, you're relying on global installation of create-react-app - which is not recommended given that it won't use the latest version. See note under Quick Start:
If you've previously installed create-react-app globally via npm
install -g create-react-app, we recommend you uninstall the package
using npm uninstall -g create-react-app or yarn global remove
create-react-app to ensure that npx always uses the latest version.
difference between npm install react-router-dom and npm install --save react-router-dom command
I tried both commands and got same result so can't understand what the actual working difference between these commands
Starting from version 5 npm will save the package to your dependencies by default. For previous versions you needed --save flag to do that.
More info: https://github.com/npm/npm/issues/5108
With the advent of npm v5 or greater, by default, it will be saved without the --save flag.
Prior to npm 5, the --save command will also save the package name under the package.json file under the dependencies object.
This will ensure than if this project was to be pulled/cloned on a different computer, you can type npm install to install all the dependencies listed under the package.json.
Whereas without --save, the dependency will not be put into package.json dependencies list. And when you type npm install in a new environment, you will be missing that package.
I want to use the latest fontawesome version. but i cannot install using npm. How to install the fontawesome latest version(5.0.10) using npm?
I tried like this
npm i #fortawesome/fontawesome
It will always install latest version by default. However you can force package manager to install specified version too.
Just run
npm i #fortawesome/fontawesome#5.0.10 --save
You need to add --save for it to also show up in package.json
or by using yarn
yarn add #fortawesome/fontawesome#latest
just use this command
npm i fontawesome#5.0.10 --save
You need to add --save for it to also show up in package.json
We are actually at 5.0.13 as of today. We also have some pre-release files for 5.1 that improve things quite a bit.
You can install the pre-release version like this:
npm install --save #fortawesome/fontawesome-free
If you are a Pro subscriber and you've configured NPM to use our private NPM repository you can do this:
npm install --save #fortawesome/fontawesome-pro
And finally if you want to install the latest 5.0.x version:
npm install --save #fortawesome/fontawesome-free-webfonts
or
npm install --save #fortawesome/fontawesome-pro-webfonts
Also note that everything that comes from Font Awesome officially will be under the #fortawesome scope.