Closed akakak1 closed 3 years ago
I also ran into problems with npm run start
.
Cannot read property 'entryOption' of undefined
Update Webpack and Webpack CLI due to this comment
"webpack": "^4.20.2",
"webpack-cli": "^3.1.1",
This caused another error:
Plugin could not be registered at 'html-webpack-plugin-before-html-processing'. Hook was not found.
This comment prompted me to try swapping the order of HtmlWebpackPlugin
and InterpolateHtmlPlugin
as shown below.
module.exports = {
//...
plugins: [
new HtmlWebpackPlugin({
// ...
}),
new InterpolateHtmlPlugin(env.raw),
//..
]
}
The dev server now starts, but I'm getting another error...
Module parse failed: Unexpected token (10:11)
You may need an appropriate loader to handle this file type.
|
| var Dashboards = lazy(function () {
> return import('../../DemoPages/Dashboards');
| });
URIError: Failed to decode param '/%PUBLIC_URL%/favicon.ico'
Most likely caused by %PUBLIC_URL%
and the swapping of the plugins order
Module parse failed: Unexpected token (10:11) You may need an appropriate loader to handle this file type. | | var Dashboards = lazy(function () { return import('../../DemoPages/Dashboards'); | }); URIError: Failed to decode param '/%PUBLIC_URL%/favicon.ico'
I'm getting this issue how can I resolve this? please help me.
Hello @akakak1 @kildareflare
We have resolved this issue in the previous release, please check.
Thank you.
GOT THIS ERROR while doing: npm run start