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

Gulp webpack slow build #3540

ssvinciak opened this issue Mar 4, 2019 · 2 comments


Copy link

commented Mar 4, 2019


  • Question
  • Typo
  • Bug
  • Additional article idea

Expected or Desired Behavior

Whenever I save source code(small change in one webpart), the build should be fast or at the most several seconds.

Observed Behavior

Each build on save(ctrl+s) takes more than minute. Webpack is especially slow. Below is ouput from gulp serve --no-browser. Performance without no browser option is the same.

Waiting for each build is unbearable.

Steps to Reproduce

I have a simple webpart that displays form with several fields and table. Below is screen with used packages. I have not added any custom tasks in gulpfile.js.


  1. npm install
  2. gulp serve --no-broswer
  3. After minute everything is ready
  4. Save small changes
  5. Another minute on build

I have also seen other slow build issues, but with no success (#3355). I don't why gulp rebuilds whole project after small change as it would be fresh start.

Thanks in advance


This comment has been minimized.

Copy link

commented Mar 4, 2019

Thank you for reporting this issue. We will be triaging your incoming issue as soon as possible.


This comment has been minimized.

Copy link

commented Mar 12, 2019

There's not much that can be done here... that's how the build system works. The gulp task serve reruns the entire build process that includes linting, transpiling, bundling & regenerating the manifest files. It's not a bug, it's just how they've decided to do it.

As you referenced another issue posting about the same topic, I'm going to close this one as a dupe issue. MSFT has tagged that issue as a bug & tracked which implies could be looking into it... better to keep things consolidated to one issue if there's no new info...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
3 participants
You can’t perform that action at this time.