The need for multiple output paths?

I have the following use case, I am using React and along with that I have certain CSS files as dependencies. I have the following distribution folder tree:

-- dist/
    --js/
    --css/
    --media/

Since, now I would like to include CSS into the build system, but now since I have my output path in the webpack.config.js to ./dist/js, so even my CSS files are being generated there.

I think it is important to have multiple output paths. If not, could anybody suggest me any other workflow?

[sashless]

The example from @sokra wasnt exactly clear to me as well but it led me to a solution 👍

It works like this @matthewmueller @activatedgeek

We assume webpack.config.js is in the root directory of your project.

entry: {
  'build/application/bundle': './src/application', // will be  ./build/application/bundle.js,
  'build/library/bundle': './src/library`'// will be  ./build/library/bundle.js
},
output: {
  path: './',
  filename: '[name].js'
}

[sokra]

output: {
  path: path.resolve(__dirname, "./dist"),
  filename: "js/bundle.js"
},
... "css/bundle.css"