I'm running nightwatch on tests using the funky new async/await syntax, among others, from the latest node:
node --harmony node_modules\nightwatch\bin\nightwatch -c nightwatch.conf.js
This works just fine.
The problem arises when I try to run things in parallel:
node --harmony node_modules\nightwatch\bin\nightwatch -c nightwatch.conf.js -e test-env1,test-env2
I think the spawned child processes have no notion of the "--harmony" flag and therefore no way to understand the new javascript syntax.
I was wondering whether this is known and whether support is on the roadmap.
I'm running nightwatch on tests using the funky new async/await syntax, among others, from the latest node:
node --harmony node_modules\nightwatch\bin\nightwatch -c nightwatch.conf.js
This works just fine.The problem arises when I try to run things in parallel:
node --harmony node_modules\nightwatch\bin\nightwatch -c nightwatch.conf.js -e test-env1,test-env2
I think the spawned child processes have no notion of the "--harmony" flag and therefore no way to understand the new javascript syntax. I was wondering whether this is known and whether support is on the roadmap.
Thanks!