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.
@types/eslint-scope@3.7.2 dependency doesn't exist but is present in yarn.lock
See original GitHub issueBug report
What is the current behavior? Webpack has a direct dependency to a nonexistent package (@types/eslint-scope@3.7.2)
If the current behavior is a bug, please provide the steps to reproduce.
What is the expected behavior? Webpack should not have a direct dependency to a nonexistent package (@types/eslint-scope@3.7.2)
Other relevant information: webpack version: 5.65.0 Node.js version: 14.16.1 Operating System: Windows 10 Additional tools: Angular 12 / Angular 13
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:7 (3 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
I think we can close it because
3.7.2in npm register (https://www.npmjs.com/package/@types/eslint-scope), also our lock file has no effect on your project, maybe something was wrong with the register, I can’t reproduce it locally, feel free to feedback, also we have https://github.com/webpack/webpack/blob/main/package.json#L8, i.e.3.7.0I agree, this problem is present in almost all Webpack v5.x.x versions. @types/eslint-scope@3.7.2 has been flagged has malicious and removed from npm : https://eslint.org/blog/2018/07/postmortem-for-malicious-package-publishes