Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement React lazy loading and Upgrade to webpack 4 #1164

Open
wants to merge 10 commits into
base: develop
Choose a base branch
from

Conversation

EXTREMOPHILARUM
Copy link
Contributor

@EXTREMOPHILARUM EXTREMOPHILARUM commented Aug 20, 2021

The initial load time for the web interface is very large because of the large js file. This is a result of the complete static components loading on the first page itself. My PR aims to resolve the speed issue by removing dead code from the production build of the Webpack and implementing react lazy loading.

Description

Performance comparison before and after using Chrome lighthouse:

Before

image

After

image

Motivation and Context

A website experience is defined by how smooth it can function and how fast it can function also this is a step forward in upgrading the project with the latest dependencies.

Reviewers

@viyatb @sharmamohit123

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Other

Checklist:

  • My code follows the code style (modified PEP8) of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.

"start": "NODE_ENV=development node server",
"precommit": "pretty-quick --staged",
"test": "jest",
"test:watch": "npm test -- --watch"
"test:watch": "npm test -- --watch",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

want to use yarn vs npm for consistency?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure I will change it to yarn.

Copy link
Member

@viyatb viyatb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you also fix the merge conflict by rebasing?
The Python tests have some problem where it does not run correctly. Did you run the node tests to make sure nothing broke?

@EXTREMOPHILARUM
Copy link
Contributor Author

Sure will rebase and fix the conflict.
The python error is due to a database issue @amanpro30 has solved and it has been merged. Rebasing will solve this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants