version 2.0 issue with output.path

[kentcdodds]

I'm using [email protected] (latest beta) and [email protected] and having trouble with output.path. I set output.path to a dist directory. When I run webpack. The bundle gets generated and placed in the dist directory as expected. But when I run webpack-dev-server the bundle is served from the root (as if no output.path is specified). Any ideas?

Here's a repo that reproduces the issue.

Here's the webpack.config.js:

const {resolve} = require('path')
module.exports = {
  entry: './js/app.js',
  output: {
    filename: 'bundle.js',
    path: resolve(__dirname, 'dist'),
    pathinfo: true,
  },
  context: __dirname,
  devtool: 'eval',
  module: {
    loaders: [
      {test: /\.js$/, loader: 'babel!eslint', exclude: /node_modules/},
      {test: /\.css$/, loader: 'style!css'},
    ],
  },
}

Here's a gif demonstrating the issue:

Let me know if you need any more information. I'm in the process of creating a video course about Webpack and I'll be using Webpack 2. I'd really like this to work. Help is definitely appreciated! Let me know if there's anything I can do! Happy to submit a PR with a little direction.

[kentcdodds]

Ok, so I worked around it by using --content-base as @xyyjk suggested, but was also required to add a prebuild and prestart script which deletes the dist and copies the index.html and favicon.ico over to the dist directory as well. I still feel like this behavior could be a bug though, so I'll leave the issue open.

[LegNeato]

Sounds like the same as webpack/webpack#2376... can you try that patch and see if it fixes it?

[kentcdodds]

Thanks for looking into this @LegNeato! Unfortunately it doesn't appear to solve my issue :-( https://github.com/kentcdodds/es6-todomvc/pull/2/files

[LegNeato]

Ah, darn...the symptoms sounded a bit similar :-(

[SpaceK33z]

Hey @kentcdodds, I think this is actually a dupe of #337. It seems that the CLI does something like output.path = '/'.

Could you confirm this?

[kentcdodds]

Hi @SpaceK33z! It's been a while, and I got it working eventually. I'm thinking this is a dupe of #337, so I'm going to close this one. Thanks!