You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If Config.publicPath contains a dot character, e.g. setPublicPath('./'), this ends up getting parsed as unescaped regex in Manifest.noramlizePath(), which ends up truncating the first character of the path.
Granted, setting ./ as a public path is probably redundant in most cases (I removed it and it works fine), but it seems to me the mix API should be robust enough that it doesn't lead to bizarre results like this that leave devs digging through internals to figure out what configuration error they made.
The text was updated successfully, but these errors were encountered:
I have the same issue, having "./" in the public path works before 1.4.2 tho. Not sure which version does it stop working. The compiled file still go to the proper location, it's just the path in manifest is messed up.
In my case, i have to put './' as public path in order for it to work on windows because of this issue #1126 .
Description:
If
Config.publicPath
contains a dot character, e.g.setPublicPath('./')
, this ends up getting parsed as unescaped regex inManifest.noramlizePath()
, which ends up truncating the first character of the path.Steps To Reproduce:
webpack.mix.js
Resulting
manifest.json
:Granted, setting
./
as a public path is probably redundant in most cases (I removed it and it works fine), but it seems to me themix
API should be robust enough that it doesn't lead to bizarre results like this that leave devs digging through internals to figure out what configuration error they made.The text was updated successfully, but these errors were encountered: