Question

112

Conflict: Multiple assets emit to the same filename

rated 0 times [ 115] [ 3] / answers: 1 / hits: 182607 / 7 Years ago, thu, february 9, 2017, 12:00:00

I'm a webpack rookie who wants to learn all about it.
I came across a conflict when running my webpack telling me:

ERROR in chunk html [entry] app.js Conflict: Multiple assets emit to
the same filename app.js

What should I do to avoid the conflict?

This is my webpack.config.js:

module.exports = {

  context: __dirname + /app,



  entry: {

    'javascript': ./js/app.js,

    'html': ./index.html,

  },

  output: {

    path: __dirname + /dist,

    filename: app.js,

  },

  resolve: {

    extensions: ['.js', '.jsx', '.json']

  },

  module: {

    loaders: [

      {

        test: /.jsx?$/,

        exclude: /node_modules/,

        loaders: [babel-loader]

      },

      {

        test: /.html$/,

        loader: file-loader?name=[name].[ext],

      }

    ]

  }

};

Answers

Only authorized users can answer the question. Please sign in first, or register a free account.

irvinjovannix

Add To Favorites

Follow

Total Points: 416

Total Questions: 94

Total Answers: 117

Location: South Korea

Member since Sun, Aug 8, 2021

3 Years ago

answered 7 Years ago grayson · Accepted Answer

i'm not quite familiar with your approach so I'll show you a common way to help you out.

First of all, on your output, you are specifying the filename to app.js which makes sense for me that the output will still be app.js. If you want to make it dynamic, then just use filename: [name].js.

The [name] part will make the filename dynamic for you. That's the purpose of your entry as an object. Each key will be used as a name in replacement of the [name].js.

And second, you can use the html-webpack-plugin. You don't need to include it as a test.