Shared content base for multiple compiler instances about webpack-dev-middleware HOT 6 CLOSED

It is potential unsafe, that is why it was changed, you can have the same URL for different files here, why you need it?

from webpack-dev-middleware.

As in my demo repository, the output is in two separate subfolders (/foo and /bar), so there will be no files collision. If output subfolders overlap (/foo and /foo/bar), that's a problem in any way because webpack build would overwrite the files.

Dev server here is a reflection of the output of the normal build, does not need any additional validations

from webpack-dev-middleware.

In theory we can implement overriding outputPath, so you can override it for any numbers of compiles, I don't want to support it by default, because it is really unsafe

from webpack-dev-middleware.

How is this more unsafe than the webpack build output, which produces the same files on the disk? Does it print a warning when overwriting a file from another compiler?

In any way, would you accept a PR adding contentBase property to the middleware options? (I think, it should belong here)

from webpack-dev-middleware.

How is this more unsafe than the webpack build output, which produces the same files on the disk? Does it print a warning when overwriting a file from another compiler?

The main problem here is the same URLs, you can potential create situation when the same URL returns different content, but if you use different directories (like in your example) you should not have these problems

In any way, would you accept a PR adding contentBase property to the middleware options? (I think, it should belong here)

It is not related to contentBase, I think we need better name here, but yes, PR welcome, we will improve name in a PR

from webpack-dev-middleware.

les't close in favor #979, we want to move webpack-dev-middleware into webpack-dev-server (monorepo), so we do some cleaup before moving issues, yeah, I agree, we don't have good support for multi compiler mode and share assets between them

from webpack-dev-middleware.