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.
Webpack 4.29.4 depends on unpublished long@4.0.1 via git
See original GitHub issueBug report
What is the current behavior?
Latest webpack (4.29.4) pulls in long@4.0.1 using Git.
long is still on 4.0.0, so 4.0.1 hasn’t been published yet. This mean it is doing so via git, which creates a hard dependency on git for projects bundled with webpack. This creates issues w/CI pipelines that do not use git.
If the current behavior is a bug, please provide the steps to reproduce. Simply install webpack with yarn/npm and inspect the lock files, and you should see something like:
long "git://github.com/dcodeIO/long.js.git#8181a6b50a2a230f0b2a1e4c4093f9b9d19c8b69"
What is the expected behavior?
Webpack itself should not have a dependency on git. This is an unnecessary dependency for CI/build systems.
Other relevant information: webpack version: 4.29.4 Node.js version: v8.15.0 Operating System: Ubuntu 18.04.2 LTS Additional tools:
Issue Analytics
- State:
- Created 5 years ago
- Reactions:24
- Comments:19 (6 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
https://github.com/webpack/webpack/releases/tag/v4.29.5 has been published
works! thanks for the fast fix!