question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Dev server startup increased from 20 seconds to 2 minutes after upgrade to 4.0.0

See original GitHub issue

Describe the bug

Dev server startup time increased drastically after upgrade to 4.0.0 from 3.4.3. From 20 seconds to more than 2 minutes afte upgrade.

Did you try recovering your dependencies?

Removed all node_modules before upgrading.

Which terms did you search for in User Guide?

Did not find anything related to this issue - slow startup time of devserver.

Environment

  current version of create-react-app: 4.0.0

System:
    OS: Linux 5.4 Ubuntu 20.04 LTS
   CPU: (8) x64 Intel(R) Core(TM) i7-** CPU @ 1.80GHz
Binaries:
    Node: 14.4.0 - ~/.nvm/versions/node/v14.4.0/bin/node
    Yarn: 1.22.4 - /usr/bin/yarn
npmPackages:
    react: 16.12.0 => 16.12.0 
    react-dom: 16.13.1 => 16.13.1 
    react-scripts: 4.0.0 => 4.0.0
   
   "typescript": "4.0.3",

Steps to reproduce

TBD - it might be somehow specific to our project. Which is medium size TypeScript project.

More info

I know that this report might be hard to reproduce and I will probably need to provide more information. But there also might be more people having same issue when comparing build/startup times and we might be able to figure out why is this happening - because this seems def as a bug, as build is incredibly slow now and this is blocker for upgrading to new version.

It might be related to project setup, but I dont have idea where to start debugging issue - maybe someone from maintainers will know what might be cause. And where to start look.

Issue Analytics

  • State:open
  • Created 3 years ago
  • Reactions:43
  • Comments:10 (3 by maintainers)

github_iconTop GitHub Comments

16reactions
mareksuscakcommented, Oct 29, 2020

Our builds have slowed down considerably, too. In my opinion, eslint should NOT be a part of the dev build at all or at least should be configurable. These days, most devs run an eslint plugin in their IDE for a more integrated dev experience anyway. Another odd default is treating all eslint warnings as errors in a CI/CD environment without any way to opt out.

Read more comments on GitHub >

github_iconTop Results From Across the Web

React app stuck on "Starting the development server"
Run npm install command before you start the server. Then if it is still not running, please try the second command. Remove the...
Read more >
Release Notes for MongoDB 4.2
SERVER -45137 : Increasing memory allocation in Top::record with high rate of collection creates and drops. SERVER-44904 : Startup recovery should not delete ......
Read more >
Building, running, and managing containers
This section shows how to upgrade to rootless containers from Red Hat Enterprise Linux 7. You must configure user and group IDs manually....
Read more >
Docker Desktop for Windows Edge Release notes
Starting with Docker Desktop 2.5.2, updates will be much smaller as they will be ... Increased timeout for virtual machine boot startup to...
Read more >
Bug listing with status UNCONFIRMED as at 2022/12/24 17 ...
freeseer - a video capture utility capable of capturing and streaming video" ... Bug:376869 - "new ebuild - dev-util/motor-3.4.2 IDE" status:UNCONFIRMED ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found