I am using packer to package my application for win32, running qode.exe works in the build directory, however if I move the entire build folder, running qode.exe opens and closes instantly (although sometimes it lingers around for 10 seconds) - doesn't appear to be loading my index.js file from the dist folder.
What is strange is that if I move the folder to some locations, it will work. I tried running it from the C drive root, and this did not work. Which probably rules out 'spaces in pathname' theory which I first thought.
Very confused.
Is there a way I can see any error qode is producing before it dies? My app already pipes the stdout and stderr to log files, but I don't see these as it appears qode.exe is dying before getting to my code.
Update
It appears only to run if there is a package.json in a parent/grand parent folder
Ok, so there appears to be some requirement for a package.json, even an empty one
I'm an idiot
It appears the library 'conf' I'm using requires a package.json to exist. So compltely unreleated to qode. I'll close!
I am using packer to package my application for win32, running qode.exe works in the build directory, however if I move the entire build folder, running qode.exe opens and closes instantly (although sometimes it lingers around for 10 seconds) - doesn't appear to be loading my index.js file from the dist folder.
What is strange is that if I move the folder to some locations, it will work. I tried running it from the C drive root, and this did not work. Which probably rules out 'spaces in pathname' theory which I first thought.
Very confused.
Is there a way I can see any error qode is producing before it dies? My app already pipes the stdout and stderr to log files, but I don't see these as it appears qode.exe is dying before getting to my code.
Update It appears only to run if there is a package.json in a parent/grand parent folder
I'm an idiot
It appears the library 'conf' I'm using requires a package.json to exist. So compltely unreleated to qode. I'll close!