React Router: hashHistory vs browserHistory

Earler I used to do this.props.history.push() to navigate to a rote dynamically. Now, it throws error. How to do the same with context?

disagree that an express application is a general case. in fact I doubt that react has prerequisites at all, certainly not node.js. disagree that const Home = () => <div><Links /></div>; goes without explanatory comments. It is not even worth a comment. So if all is clear and we know everything, why do we need this lecture at all?

another example is this line: ReactDOM.render( <App />, document.getElementById( 'app' ) ); That being written, without further "note that ", we are all enlighted that we are now rendering Routes into the app.

Again, if everything is clear, why the course? I feel a little bit upset with the wealth on skill shared. Literally reading, what any third person types in: I do not need a course for that.

h2m2, this course does presume some familiarity with React. Sorry if that was not clear and thanks for pointing it out.

Regarding the two lines of code you mentioned requiring more explanation:

ReactDOM.render( <App />, document.getElementById( 'app' ) );

const Home = () => <div><Links /></div>

These common React usages are covered in courses like https://egghead.io/courses/react-fundamentals or https://egghead.io/courses/build-your-first-react-js-application

To make browserHistory work without a server you can add historyApiFallback: true to your devServer block in your webpack.config.

just so everyone is aware for this lesson use React-Router-Dom. This is the new version and works much much better.