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
mix.setPublicPath() shaves off the first portion of the output path of mix.js() only if it set to a variant of "one directory up". So the same goes for
Self-closing this issue because I feel like it's too specific and too much of an edgecase to be overly useful or worth investigating. Save the energy for actual issues :)
npm list --depth=0
)node -v
): 17.2.0npm -v
): 8.1.4Description:
mix.setPublicPath()
shaves off the first portion of the output path of mix.js() only if it set to a variant of "one directory up". So the same goes forSteps To Reproduce:
Having a project structure like this:
With a Mix setup like this:
creates the following output:
What I would expect:
This does not seem to happen in any other constellation, so
mix.setPublicPath("../..")
ormix.setPublicPath("foo/bar")
work as expected.Might be related to #3106
The text was updated successfully, but these errors were encountered: