Created by @suhmantha1 for Use All Five's Lunch n' Learn.
react-router
react-router-dom
react-transition-group
- React Docs
- React routing issues: https://medium.com/onfido-tech/animations-with-react-router-8e97222e25e1
- https://reacttraining.com
- https://reactcommunity.org/react-transition-group/
- How to build simple fade animation: https://www.youtube.com/watch?v=NUQkajBdnmQ
- Explanatory for TransitionGroup: https://medium.com/@pshrmn/a-shallow-dive-into-react-router-v4-animated-transitions-4b73f634992a
- Base transitions on page history: https://blog.etch.team/react-page-transitions-make-your-website-feel-native-bf2804b011dc
- Implement
<BrowserRouter>
inindex.js
, which will automatically handle route history and UI component display - Add
Switch
inapp.js
, which renders routes based on the specified tag. - Install
react-transition-group
, and import inapp.js
in order to use around theSwitch
- In
app.js
, create wrap theSwitch
in aCSSTransition
- In
app.js
, wrap theCSSTransition
in aTransitionGroup
- Render an empty route in
app.js
, and move theTransitionGroup
inside so that it's always rendered - To render multiple pages at the same time in the group by adding
Location Key
to theCssTransition
. At this point, when you change routes, there is atimeout
ms time where both pages are rendered at the same time. - Pass the
location
to theSwitch
so that it knows what routes to render on transition - Add styling to animate the transitions
This project was bootstrapped with Create React App.
In the project directory, you can run:
Runs the app in the development mode.
Open http://localhost:3000 to view it in the browser.
The page will reload if you make edits.
You will also see any lint errors in the console.
Launches the test runner in the interactive watch mode.
See the section about running tests for more information.
Builds the app for production to the build
folder.
It correctly bundles React in production mode and optimizes the build for the best performance.
The build is minified and the filenames include the hashes.
Your app is ready to be deployed!
See the section about deployment for more information.
Note: this is a one-way operation. Once you eject
, you can’t go back!
If you aren’t satisfied with the build tool and configuration choices, you can eject
at any time. This command will remove the single build dependency from your project.
Instead, it will copy all the configuration files and the transitive dependencies (Webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject
will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.
You don’t have to ever use eject
. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.
You can learn more in the Create React App documentation.
To learn React, check out the React documentation.
This section has moved here: https://facebook.github.io/create-react-app/docs/code-splitting
This section has moved here: https://facebook.github.io/create-react-app/docs/analyzing-the-bundle-size
This section has moved here: https://facebook.github.io/create-react-app/docs/making-a-progressive-web-app
This section has moved here: https://facebook.github.io/create-react-app/docs/advanced-configuration
This section has moved here: https://facebook.github.io/create-react-app/docs/deployment
This section has moved here: https://facebook.github.io/create-react-app/docs/troubleshooting#npm-run-build-fails-to-minify