Different build environment causing mix error

[imaje89]

Hey everyone, I have a bit of a weird problem following a bit of a restructure of one of my jigsaw projects.

I was building two sites in one essentially but recently felt the need to move one into its own Jigsaw project / site.. It's only small so I only had to copy/paste the directory, remove and re-install node package dependencies and remove the stuff that I didn't need from the project.

All was well and both sites build locally just fine.

But, in the new site (the copy) whenever I run npm staging, the build fails with the following:

Unable to locate Mix file: /scripts/header.js.

which is injected into the head using this:

<link rel="preload" href="{{ mix('/scripts/header.js', 'assets') }}" as="script" type="text/javascript" crossorigin>

using this line in my webpack file

mix.setPublicPath('source/assets/');
mix.combine(['source/_assets/js/header.js'], 'source/assets/scripts/header.js');

and here's the corresponding mix-manifest entry

"/scripts/header.js": "/scripts/header.js?id=2ea66a9025404825e4e1",

when I run vendor/bin/jigsaw build staging staging builds fine (but without the much needed minification, purgeCSS etc)

It's worth noting here too that the original (larger) project continues to build fine with no issues at all.

I have tried lots of things and checked and re-checked in case I've deleted something by accident,

but i'm in a state where both local, and staging are in an identical state, but staging always fails with the 'unable to locate mix file' error shown above.

I'm wondering if this is a symptom of something else going wrong but I'm being led down the wrong path by the console output, is there a way for node to tell me more at all?

Thanks for your help!