setPublicPath sets wrong path when using mix.js()

• Laravel Mix Version: 1.0.7
• Node Version: 6.10.2
• NPM Version: 5.0.4
• OS: Windows 7 Ultimate x64

Description:

I’m trying to relocate my assets to an ‘assets’ subfolder inside /public. The mix-manifest.json gets created in the correct location and mix.less() outputs my CSS files and updates the reference in the manifest with the correct location as well. The mix.js() method however behaves strangely, as you can see in the screenshot.

I’m using the simplest possible setup to demonstrate this - a fresh installation of Laravel and npm install. I have tried adding and removing slashes all over the place, but to no avail.

Steps To Reproduce:

1. Edit the webpack.mix.js file with the following:

mix.setPublicPath('public/assets');
mix.js('resources/assets/js/index.js', 'js');
mix.less('resources/assets/less/index.less', 'css');

1. npm run dev

[TopFuel]

• Laravel Mix Version: 1.2.2
• OS: Windows 10 Creators Update x64

Can confirm that using path.normalize on mix.setPublicPath fixes the issue where I needed to change from:

mix.setPublicPath('../public');
mix.js('resources/assets/js/app.js', '../public/js/app.js'); // or 'js/app.js'

to:

mix.setPublicPath('..\\public');
mix.js('resources/assets/js/app.js', '..\\public/js/app.js'); // or 'js/app.js'

for it to work correctly, or it would freeze at 95% emitting on the npm run development command, and outputs this to the mix-manifest.json:

{
    "/E:/projects/test-project/public/E:/projects/test-project/public/js/app.js": "/E:/projects/test-project/public/E:/projects/test-project/public/js/app.js"
}

But adding path.normalize fixes it:

mix.setPublicPath(path.normalize('../public'));
mix.js('resources/assets/js/app.js', '../public/js/app.js'); // or 'js/app.js'

mix-manifest.json:

{
    "/js/app.js": "/js/app.js"
}

[gabrieldasilva]

Hey! I’m having some throubles with this too. Actually I have a project from tree weeks ago with last mix version at that moment (0.*) and the public path was working fine. Today I start a new project and I realize that already comes with the Mix 1.1.1.

So, I basically copy / paste my webpack.mix and this issue appears…

My public path is somehing like ‘public/assets/www/…’ so then I have website folders for css, images, fonts, js etc…

I think I figure it out by using the path.normalize inside setPublicPath like this:

mix.setPublicPath(path.normalize('public/assets/www/'));

but I want to know if now this is the way to use the custom path.

My configuration its actually the same that @omnichronous uses…

Btw, I’m using Windows 10 x64.