Don't output empty JS files

[TomS-]

I have seen people use the Extract plugin and name the file the same to prevent a useless .js file, however, naming the file the same in this instance gives the error:
Conflict: Multiple assets emit to the same filename main.js

I only want to take a CSS file and run it though autoprefix and minify, I don't need it to output a JS file.

[alexander-akait]

@TomS- can you create minimum reproducible test repo?

[TomS-]

@evilebottnawi Yup, I'll set it up this evening

[TomS-]

https://github.com/TomS-/minicss Sorry for the delay

[tiendq]

@TomS- I'm not sure I understand your issue. Do you want to not output tailwind.js from importing tailwind.css because there is already a tailwind.js in your source?

[TomS-]

@tiendq I don't want Webpack to output a JS file for CSS. It seems strange to me for it to do that. At the moment I'm getting the CSS file and a JS file. I'm coming from Gulp so maybe it's just I don't understand Webpack.

[tiendq]

@TomS- I don't want it too :)

[paulmasek]

+1 Mainly because it'll probably fix Va1/browser-sync-webpack-plugin#69

[giancarlosisasi]

+1

[alexander-akait]

Weppack is js bundle, i can not imagine why this might be necessary, please provide use case

[thewebsitedev]

Same issue. I have a PHP application but I am managing assets with Webpack. With Webpack 4 & MiniCssExtractPlugin, generating CSS files is a pain at the moment. I need to directly load CSS file.

Part of my config:

{
    mode: "development",
    entry: {
        "admin": "./assets/admin/src/scss/theme.scss"
    },
    module: {
        rules: [
            {
                test: /\.(sa|sc|c)ss$/,
                use: [
	            MiniCssExtractPlugin.loader,
                    'css-loader',
                    'sass-loader'
                ],
            },
        ]
    },
    plugins: [
        new MiniCssExtractPlugin({
            filename: "[name].css",
            chunkFilename: "[id].css"
        })
    ],
    output: {
        path: path.resolve(__dirname, 'assets/admin/dist/css')
    }
},

Files generated are: admin.css & admin.js.

I don't need admin.js file. It's useless in my case.

[bregenspan]

The cause of this is probably webpack/webpack#7300, which has been added to the Webpack 4.x milestone.

[jarrodpayne]

This issue is biting me as well. Feel free to close this if this plugin can't offer an alternative. Btw, webpack/webpack#7300 has been retagged with Webpack 5.x, so we won't likely see a fix in webpack until then.

[alexander-akait]

We search way to fix it inside plugin