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.
Investigate upgrading Gulp, Webpack and Node.js dependencies
See original GitHub issueFrom #10176:
Webpack is pinned because versions higher than this cause the viewer not
to work (see https://github.com/mozilla/pdf.js/pull/10170#issuecomment-431697032).
Node.js is pinned for Travis CI because version 11 requires that we
update to Gulp 4.
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Webpack or Browserify & Gulp: Which Is Better? - Toptal
Which bundling tool should you use: Webpack or Browserify + Gulp? ... app.js , and those dependencies may themselves have further dependencies to...
Read more >How to Migrate to Gulp.js 4.0 - SitePoint
Update your package.json dependencies as shown above, then run npm install to upgrade. You can also update the command-line interface using npm ...
Read more >See How Easily You Can Upgrade To Webpack
Start to break things into steps · Upgrade the node version from 0.10 to the latest version available · Fixing errors shown on...
Read more >Fixing security vulnerabilities in npm dependencies in less ...
Solution. Solution to this problem is in steps:- npm update. This is the first thing you should do and it's the simplest one...
Read more >Build Performance - webpack
This guide contains some useful tips for improving build/compilation performance. ... Staying up-to-date with Node.js can also help with performance.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I have filed an upstream issue for this bug at https://github.com/webpack/webpack/issues/8829. If that is fixed, we can remove the workaround. Tracking this upstream now.
Gulp and Node.js are taken care of in the meantime, only Webpack remains.