FAQ: React Router - Installing React Router

This community-built FAQ covers the “Installing React Router” exercise from the lesson “React Router”.

Paths and Courses
This exercise can be found in the following Codecademy content:

React Router
(Beta) Learn React Router

FAQs on the exercise Installing React Router

There are currently no frequently asked questions associated with this exercise – that’s where you come in! You can contribute to this section by offering your own questions, answers, or clarifications on this exercise. Ask or answer a question by clicking reply (reply) below.

If you’ve had an “aha” moment about the concepts, formatting, syntax, or anything else with this exercise, consider sharing those insights! Teaching others and answering their questions is one of the best ways to learn and stay sharp.

Join the Discussion. Help a fellow learner on their journey.

Ask or answer a question about this exercise by clicking reply (reply) below!
You can also find further discussion and get answers to your questions over in #get-help.

Agree with a comment or answer? Like (like) to up-vote the contribution!

Need broader help or resources? Head to #get-help and #community:tips-and-resources. If you are wanting feedback or inspiration for a project, check out #project.

Looking for motivation to keep learning? Join our wider discussions in #community

Learn more about how to use this guide.

Found a bug? Report it online, or post in #community:Codecademy-Bug-Reporting

Have a question about your account or billing? Reach out to our customer support team!

None of the above? Find out where to ask other questions here!

Upon following the tutorial steps, we are met with this error:

Failed to compile

./src/components/Search.jsAttempted import error: 'useHistory' is not exported from 'react-router-dom'.

It seems that in react-router-dom v6 useHistory() is replaced by useNavigate() . (source)

Replacing instances of useHistory() with useNavigate() seems to do the trick.

Similarly, useRouteMatch needs to be replaced with useMatch.

It would be good for the downloadable code package to be updated for others using this lesson.

2 Likes

Following issues with further sections because of the outdated version of React Router used in this tutorial, I manually updated package,json to use the old version so that I could continue the course.

"react-router-dom": "^5.2.0",

For anybody stranded when trying to start the live server with npm start.

In your package.json: change this line

"start": "react-scripts start"

to

"start": "react-scripts --openssl-legacy-provider start"

Please note that this is only recommended as a temporary fix for this exercise. I would not recommend this when working on a professional project as you are most certainly running with a known insecure SSL.

2 Likes

Hi

Your trick almost worked…

I got this error:

Failed to compile
./src/index.js 1:52
Module parse failed: Unexpected token (1:52)
File was processed with these loaders:
 * ./node_modules/@pmmmwh/react-refresh-webpack-plugin/loader/index.js
 * ./node_modules/babel-loader/lib/index.js
You may need an additional loader to handle the result of these loaders.
> $RefreshRuntime$ = require('C:/react-router-lesson-starter/node_modules/react-refresh/runtime.js');
| $RefreshSetup$(module.id);
|

At this point, rather than trying to configure webpack to work with an outdated version of react router, I would instead just check out the docs on the react router page and see if you can build the same simple app with the new version. The differences aren’t huge. They have clearly written documentation and a tutorial.

1 Like

Exactly what I’ve done, thank you!

The fact that this exercise has been broken for 8 months now and nobody on the Codecademy team has reviewed the exercise to work with the latest version of React Router seems just lazy. I’m paying the pro subscription and putting my trust in the academic team to teach me up to date content. I know as a developer we will have to do work arounds a lot of times to get outdated software to run, but the fact that y’all know it and won’t even want to fix it is lazy. It’s not an unknown bug and just adding a disclaimer at the top of the exercise with the official documentation instead of just reviewing your exercise is just lazy.

7 Likes