Breaking change from 1.6.0 to 1.6.1
Hi, I just recently installing prep version 1.6.1 and it didn't work because of the following errors:
Retry 1 for route: /
Retry 1 for route: /portfolio
Retry 2 for route: /
Retry 2 for route: /portfolio
Retry 3 for route: /
Retry 3 for route: /portfolio
Retry 4 for route: /
Retry 4 for route: /portfolio
Retry 5 for route: /
Retry 5 for route: /portfolio
Retry 6 for route: /
Retry 6 for route: /portfolio
Retry 7 for route: /
Retry 7 for route: /portfolio
Retry 8 for route: /
Retry 8 for route: /portfolio
Retry 9 for route: /
Retry 9 for route: /portfolio
Retry 10 for route: /
Retry 10 for route: /portfolio
{ Error: Command failed: cp -rf "/Users/antony/Documents/Code/Web/antonybudianto-web/.prep-tmp"/* "/Users/antony/Documents/Code/Web/antonybudianto-web/build"/
cp: /Users/antony/Documents/Code/Web/antonybudianto-web/.prep-tmp/*: No such file or directory
`cp -rf "/Users/antony/Documents/Code/Web/antonybudianto-web/.prep-tmp"/* "/Users/antony/Documents/Code/Web/antonybudianto-web/build"/` (exited with error code 1)
at callback (/Users/antony/Documents/Code/Web/antonybudianto-web/node_modules/child-process-promise/lib/index.js:33:27)
my prep.js:
exports.default = {
routes: [
"/",
"/portfolio"
],
timeout: 5000
}
When I downgraded to version 1.6.0, it worked well. Thanks for the work!
Must have been to #17. @msalahat can you take a look pls?
@schickling sure will check it out
Thanks @msalahat!
@antonybudianto can you check 1.6.2 and close if it's fixed for you?
Hi @schickling , I've tried 1.6.2 but still same error
{ Error: Command failed: cp -rf "/Users/antony/Documents/Code/Web/antonybudianto-web/.prep-tmp"/* "/Users/antony/Documents/Code/Web/antonybudianto-web/build"/
cp: /Users/antony/Documents/Code/Web/antonybudianto-web/.prep-tmp/*: No such file or directory
`cp -rf "/Users/antony/Documents/Code/Web/antonybudianto-web/.prep-tmp"/* "/Users/antony/Documents/Code/Web/antonybudianto-web/build"/` (exited with error code 1)
We'll soon re-write prep to use Chromeless under the hood. Could you use the 1.6.0 release for now?
@schickling Of course.