Bundling Error: code=-1, error:spawn ENOENT about meteor-up-legacy

[cramhead]

I resolved the error condition.
The problem was that I was deploying from a different machine, and as such, have a different username and home directory path. I changed the location of the app parameter and all worked well.

I'm aim still wondering how to debug, but I'll close the open issue.

[crapthings]

@cramhead

hey @cramhead how do u solve your error?

[cramhead]

The path to the project was wrong. When I moved from machine to machine the locations of the checkout were different. The mup.json file app value needs to point the correct location. Using a symbolic link or relative path is my approach to allowing variation in path while still keeping the mup.json the same.

[brylie]

I just had this issue as well. I had moved my local development folder to a new location and failed to update the mup.json settings.

[papayaah]

can we make so that mup look up for current directory?