Sub Directory entry points about file-loader

[sokra]

The url (from a file loaded with the file-loader) starts with output.publicPath. So you need to provide a correct publicPath. The publicPath should be a relative path relative to the HTML file or and server absolute path.
output.publicPath = '' means it can find the files in the same folder of the HTML file.
output.publicPath = '/' means it can find the files in the server root.

In your case the location of the HTML file is not constant. So you either need to provide a server-relative publicPath or provide the publicPath while runtime (set __webpack_public_path__).

[talves]

@sokra This kinda seems like a hack? But it worked for my use case by setting __webpack_public_path__ = "../" in my entry files for the sub directories.

Although this does not solve the issue for the webpack-dev-server, I can live with this solution for now because it is definitely the most elegant solution so far.

Note:

It does not really solve the issue of having to be dependent on the context root. I believe a change in the file-loader would solve this easily by adhering to a relative path resolve when the public path is not set to absolute. Unfortunately, this would require us to know the context root of each entry point in the file loader to resolve to the correct relative path.
Here is my first stab at that change, but required me to pass the query.context="<dirname>"

Final proposed solution

Here is a compare of the adds to consider
Consideration

• Only applies when output.publicPath = '' (empty string)
• Assumes that all file-loader assets will be in the relative path to the entry point
• Allows for the checking of webpack-dev-server and run as absolute (see here)
• allows for a root entry point at the same time as sub dir entry points
• If running all entry points from the root of the context, then this would still work properly

[philipheyde]

Thank you @sokra. Your reply helped me greatly!

[SpaceK33z]

Closing since it looks like the root problem has been solved now. If there's still a problem, please make a new issue.