You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 2, 2018. It is now read-only.
I'm using duo in a gulp build script. I've been a little behind on updating, and have begon updating to the latest duo version (pr here, and duo build script). However, from what I understand duo now needs to be run with the node --harmony-generators flag.
Which is a problem for me, since I'm using gulp and not node directly. Now I can get everything to work as expected by running:
But of course, I'd just like to be able to use gulp build. Is there a way solve this from within duo, without modifying my entire build process? I'm asking here because this is sort of a duo-specific requirement, and I'd like to solve this as close to duo as possible.
The text was updated successfully, but these errors were encountered:
I've solved this for myself with https://github.com/dcodeIO/node-harmonize, but thought this would still be a valid duo issue. Since I couldn't really find any info in the documentation on duo requiring the --harmony-generators flag, or only working with iojs (which has generators turned on by default).
In my opinion It would be helpful to add this requirement to the docs (if the --harmony-generators flag can't be enabled from within duo).
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm using duo in a gulp build script. I've been a little behind on updating, and have begon updating to the latest duo version (pr here, and duo build script). However, from what I understand duo now needs to be run with the node
--harmony-generators
flag.Which is a problem for me, since I'm using gulp and not node directly. Now I can get everything to work as expected by running:
But of course, I'd just like to be able to use
gulp build
. Is there a way solve this from within duo, without modifying my entire build process? I'm asking here because this is sort of a duo-specific requirement, and I'd like to solve this as close to duo as possible.The text was updated successfully, but these errors were encountered: