search

jharris4 / html-webpack-tags-plugin

lets you define html tags to inject with html-webpack-plugin
MIT License
256 stars 31 forks source link

Why would webpack-cli require html-webpack-include-assets-plugin #40

Closed blachawk closed 5 years ago

blachawk commented 5 years ago

I am getting a strange error and don't understand why its happening via npm.

I have the following npm packages installed:

"devDependencies": {
    "@fortawesome/fontawesome": "^1.1.8",
    "@fortawesome/fontawesome-free-solid": "^5.0.13",
    "bootstrap": "^4.1.1",
    "css-loader": "^0.28.11",
    "exports-loader": "^0.7.0",
    "html-webpack-plugin": "^3.2.0",
    "jquery": "^3.3.1",
    "json-loader": "^0.5.7",
    "mini-css-extract-plugin": "^0.4.0",
    "node-sass": "^4.9.0",
    "popper.js": "^1.14.3",
    "postcss-loader": "^2.1.5",
    "sass-loader": "^7.0.3",
    "webpack": "^4.12.0",
    "webpack-cli": "^3.2.1",
    "webpack-dev-server": "^3.1.4"
  },

when I run npm start from the terminal, I get the following error message:

C:\Users\...\node_modules\webpack-cli\bin\cli.js:235
                                throw err;
                                ^
Error: Cannot find module 'html-webpack-include-assets-plugin'

Why is this happening to me?

jharris4 commented 5 years ago

Sounds like you have it in your webpack config. Try doing a text search across all files maybe?

blachawk commented 5 years ago

Yeah I did that. Nothing comes up. So strange. My Webpack environment runs great with it. I don't mind holding on to it in development, but I wish I knew why npm is complaining about it when its gone...

jharris4 commented 5 years ago

Very strange, it must be loading the plugin from somewhere, in some kind of webpack.config.js file would be my bet.

I don't think there's much I can do to help, since the issue is actually outside of this plugin somewhere.

Gonna close it, good luck tracking down where config is that's causing your error!