Entrypoint undefined = extract-text-webpack-plugin-output-filename after upgrade to webpack 4

[ngohungphuc]

I got this error

My webpack.config file

const path = require("path");
const webpack = require("webpack");
const ExtractTextPlugin = require("extract-text-webpack-plugin");
const UglifyJSPlugin = require("uglifyjs-webpack-plugin");

module.exports = {
  entry: {
    main: "./wwwroot/frontend/js/main.js"
  },
  output: {
    path: path.resolve(__dirname, "wwwroot/dist"),
    filename: "[name].js",
    publicPath: "/dist/"
  },
  plugins: [
    new ExtractTextPlugin({
      filename: "cmscore.css"
    }),
    new UglifyJSPlugin({
      sourceMap: true
    })
  ],
  module: {
    rules: [
      {
        test: /\.scss$/,
        use: ExtractTextPlugin.extract({
          fallback: "style-loader",
          use: "css-loader!sass-loader"
        })
      },
      {
        test: /\.(js|jsx)$/,
        exclude: /node_modules/,
        use: ["babel-loader", "eslint-loader"]
      }
    ]
  },
  watch: true
};

Am I missing something or webpack 4 is not ready to use with this plugin ?

[RussGlover]

I have this same issue, it only occurs when webpack mode is set to production.

[AtofStryker]

Webpack 4's new tapable plugin library broke some of the existing plugins. The fix should be relatively simple

[ngohungphuc]

I get this error in dev mode not sure about prod mode may be the same lol @RussGlover

[jbasilio]

I have the same issue in Webpack 4. Regardless of mode.

[alexander-akait]

Somebody can create minimum reproducible test repo?

[mauriciofergo]

Same error here,
The build is performed properly but when I enter the local server the entry point is not loaded.
In my case I'm using babel-polyfill (not sure if it's the correct way)

main: ['babel-polyfill', './js/main.js'],

[DaveBitter]

Same issue here. The fix probably isn't that big of a task. If I had more knowledge on this I would make a PR. Is there any ETA for the fix. I now have to downgrade to Webpack 3 just for this plugin.

[leereichardt]

Is Webpack 4 even ready for production use? I feel like they need to delay a few more weeks to allow some of the most important plugins to be updated?

[Edward-Lombe]

@leereichardt After using it for a couple of days, my survey would be no. It still works, but for a program as reliant on plugins as webpack is (especially those under the quasi-official webpack contrib), I would expect the release of v4 to correspond to all the important plugins being updated to v4.

[ngohungphuc]

@leereichardt

Webpack 4's new tapable plugin library broke some of the existing plugins. The fix should be relatively simple

[leereichardt]

So it has been said on various issues for the past 50 odd days. Yet this relatively simple fix hasn’t been fixed?

[ngohungphuc]

not sure why is take so long

[oliverguenther]

Responding here because I'm being notified of your recent comment. How about instead of complaining here, you contribute by helping in fixing the broken tests in the v4 compatibility PR ?

Thanks to the maintainers that have provided our project with smooth upgrade paths from the early days of webpack. We are experiencing the same issue and will appreciate it being fixed as soon as the maintainers can handle it. If it will take a few days or weeks more, so be it.

[ngohungphuc]

We just raise the concern, not complain. Also If I have enough knowledge I would make Pr and fix it for you guys

[AvraamMavridis]

Same issue here, with webpack 4

[alexander-akait]

We have a lot of issue when webpack@4 was shipped. 😞

Feel free to PR to fix this.

[alexander-akait]

I can look on ETWP only on next week, sorry

[sukonzer]

Same issue in Webpack 4. Regardless of mode

[zD98]

Maybe entrypoint undefined = xxx is a unfinished feature of webpack 4. ? ? ?

CSS Module Type — CSS as Entry (Goodbye ExtractTextWebpackPlugin)

HTML Module Type — HTML as Entry

And Javascript EntryPoint doesn't have any errors.

[zD98]

    stats: {
        ...
        children: false, 
        ...
    },

Setting the property children to false will show off the log info.
But I don't what happened.

[Krucial92]

Is there any update on this? Any solution to resolve the issue "entrypoint undefined"? Thanks.

[benoitmaudet]

Same error with webpack 4 : Entrypoint undefined = extract-text-webpack-plugin-output-filename.

[waleedahmed3045]

Alot of people are having this issue. Can this be resolved please?

[StalkAlex]

I have experiencing those messages for all non-js entrypoints that I didn't specified myself, like css or html(how I undestand this), but with js entypoint I specified manually it shows correct output Entrypoint main [big] = js/main.3bf77c.js ./css/main.f871d2.css js/main.3bf77c.js.map and it's not causing any real problems, just those messages. Application is working as it suppose to. I'm using last version of webpack and this plugin. So what's real problem with that?
Here's explanation I think.

[polco]

If you're only using the extract-text plugin for CSS, you can use this plugin instead: https://github.com/webpack-contrib/mini-css-extract-plugin

It's compatible with webpack 4.

[mauriciofergo]

Sorry @maphi88 but I'm not continuing with the migration, good luck!

[GabrielDelepine]

@mauriciofergo #759 about compatibility section in the README file

[7iomka]

@michael-ciniawsky
mini-css-extract-plugin not working for me, because I needed to set publicPath in config.
ETP prodive this posibility

 use: ExtractTextPlugin.extract({
                        publicPath: '../',

But mini-css-extract-plugin has no options(
Any ideas how to fix "Entrypoint undefined = extract-text-webpack-plugin-output-filename" ?

[ngohungphuc]

@7iomka check my pr to help you config webpack 4
https://github.com/Awesome-CMS-Core/Awesome-CMS-Core/pull/71/files

[tiendq]

mini-css-extract-plugin currently doesn't work with this error:

Module build failed: TypeError: this[NS] is not a function

I'd stay with extract-text-webpack-plugin, it's better to just see a warning :)

[bspatil0001]

Is this issue closed, Is there a solution for this issue? Moving to other plugin is the only solution.

[AlexGalays]

When plugins are abandoned before a replacement is fully ready :(

[nicolasxu-bg]

I still have the same issue.

[tiendq]

I just tried mini-css-extract-plugin again, version 0.4.0 and it works well with SCSS extraction. As authors of extract-text-webpack-plugin has suggested, you'd better to use mini-css-extract-plugin for CSS now :)

[tiendq]

@samboustani what are your problems? did you raise issues?

[mesmerize86]

Hi @tiendq

Entrypoint mini-css-extract-plugin = *

When i use mini-css-extract-plugin I got above entry point. And it still stop bundling.

{
test: /.(sa|sc|c)ss$/,
use: [
MiniCssExtractPlugin.loader,
'css-loader',
'sass-loader',
],
}

new MiniCssExtractPlugin({
  filename: '[name].min.css'
}),

[ngohungphuc]

Migrate to webpack 4 & extract mini plugins
You guys can take a look here
https://github.com/Awesome-CMS-Core/Awesome-CMS-Core/blob/master/src/AwesomeCMSCore/AwesomeCMSCore/webpack.config.js

[nemanjacosovic]

+1

[wp-kitten]

Well done @ngohungphuc , your solution was the only one that worked and helped me not pulling all my hair out. Thanks a lot buddy!

[ngohungphuc]

@wp-kitten no problem glad that I can help 😄

[bigbizyou]

Hy !!!
do not forget to exclude node_modules, it was OK for me :

module: {
rules: [
{
test: /.scss$/,
exclude: /node_modules/,
use: ExtractTextWebpackPlugin.extract({
fallback: 'style-loader',
use: [{
loader: 'css-loader',
options: {minimize: true}
}, 'sass-loader', 'postcss-loader', 'import-glob-loader']
})
},