Upgrading to webpack 4 issue
See original GitHub issueI’m getting the following when trying to build webpack 4:
TypeError: Cannot read property ‘tapAsync’ of undefined at /Users/user/react-boilerplate/node_modules/favicons-webpack-plugin/index.js:73:62
this is the code in index.js:73
if (!tapped++) {
cmpp.hooks.htmlWebpackPluginBeforeHtmlProcessing.tapAsync(
'favicons-webpack-plugin',
addFaviconsToHtml
);
}
any ideas?
Issue Analytics
- State:
- Created 5 years ago
- Reactions:11
- Comments:18 (3 by maintainers)
Top Results From Across the Web
To v4 from v3 - webpack
If you are still using Node.js v4 or lower, you need to upgrade your Node.js installation to Node.js v6 or higher. Instructions for...
Read more >Upgrading Webpack 4 → 5 | Square Corner Blog
Upgrading developer tools is usually not pressing, can be time consuming, and modifying a bundler can be high risk. Since we rely on...
Read more >Step-by-step Guide to Upgrading to Webpack 4 - Oleg Chursin
Step-by-step Guide to Upgrading to Webpack 4 · 9. Fix any deprecation errors you may be getting. · 8. Update and reconfigure uglifyjs-webpack-plugin...
Read more >Upgrade to Webpack 4 - DEV Community
Upgrading your project from Webpack 3 to Webpack 4. ... I ran into a weird issue with webpack-hot-middleware but once I upgraded it...
Read more >Just some notes about my attempt to upgrade to webpack 4
For loader options: webpack 2 no longer allows custom properties in configuration. Loaders should be updated to allow passing options via loader options...
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

actually I used this plugin https://github.com/brunocodutra/webapp-webpack-plugin witch is a fork of your plugin and brunocodutra fixed it
It seems that solution is to add mandatory
html-webpack-pluginplugin! Yes?Environment
Possible solution
This solution works for me (using Laravel Mix v4.0.16) Code:
…and then of course -
$ npm run productionI am waiting to hear some others experiences 😃 👍 👎