Skip to content

AnthoGdn/labo_redux_vs_react-context

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

13 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Purpose

It's a demonstration of "rerendering" when we use Props, React Context and Redux.

You can find my article for more explanation.

React Context or Redux? What's difference about rerendering (performance)?

There is one page contains 3 components with the same feature. One uses React props, another uses React context and the last one uses Redux.

We can open the browser console to see every console.log where we change the state of one component.

We can observe that with Redux, React doesn't rerender Component1 and Component3 because they are not branch to Redux.

Screens

Demo screenshot

Representations of the architecture

State shared by Props

Demo screenshot

State shared by React Context

Demo screenshot

State shared by State

Demo screenshot

Versions

Tested with:

  • Node v14.17.6
  • Yarn 1.22.10

Manual

This project was bootstrapped with Create React App, using the Redux and Redux Toolkit template.

Available Scripts

In the project directory, you can run:

yarn start

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.

yarn test

Launches the test runner in the interactive watch mode.
See the section about running tests for more information.

yarn build

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.

yarn eject

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.

Learn More

You can learn more in the Create React App documentation.

To learn React, check out the React documentation.

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published