webpack --version reports 2.4.1
See original GitHub issueDo you want to request a feature or report a bug?
- Report a bug
What is the current behavior?
- Run
webpack --version
- Prints
2.4.1
- Run
webpack
- Prints
Version: webpack 3.2.0
If the current behavior is a bug, please provide the steps to reproduce.
(above)
What is the expected behavior?
- Print the actual version
If this is a feature request, what is motivation or use case for changing the behavior?
Please mention other relevant information such as the browser version, Node.js version, webpack version and Operating System.
Issue Analytics
- State:
- Created 6 years ago
- Comments:5
Top Results From Across the Web
webpack - npm
webpack is a module bundler. Its main purpose is to bundle JavaScript files for usage in a browser, yet it is also capable...
Read more >webpack-dev-server 2.4.1 vulnerabilities | Snyk
Automatically find and fix vulnerabilities affecting your projects. Snyk scans for vulnerabilities and provides fixes for free. Fix for free. Vulnerability ...
Read more >Error running npm run build - webpack@2.4.1 · Issue #4780
If the current behavior is a bug, please provide the steps to reproduce. Running npm run build leads to: Invalid configuration object. Webpack...
Read more >umi-webpack-bundle-analyzer | Yarn - Package Manager
In static mode single HTML file with bundle report will be generated. In json mode single JSON file with bundle report will be...
Read more >eslint-webpack-plugin - NPM Package Overview - Socket - Socket.dev
A ESLint plugin for webpack. Version: 3.2.0 was published by ricardogobbosouza. Start using Socket to analyze eslint-webpack-plugin and its 5 dependencies ...
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
Upgrading to
yarn
0.28.4
fixes this, not an issue withwebpack
butyarn
@bfricka Indeed I was using
yarn 0.27.5