-
Notifications
You must be signed in to change notification settings - Fork 26
Atom plugin broken #396
Comments
…rams (issue #396) Right now one also needs to regenerate the runtime: ./tools/build_sdk --no-destructure-named-params
Sent a PR with a flag that disables destructuring (and filed #397 to track multiple runtimes). @devoncarew, if running build_sdk.sh as part of the plugin's build is not an option, then I can flip |
It would be a lot more convenient to not have to do rebuild it :) |
@devoncarew It looks like destructuring is behind a separate "--harmony-destructuring" in Chrome 45. Is that possible to turn on? If not (or it doesn't work), we can disable it by default until Atom rolls forward. @ochafik does anything break without destructuring? |
Allow disabling named param destructuring with --destructure-named-params (issue #396)
Destructuring fixes a pattern that breaks Closure's advanced mode, but it's not ready yet anyway, so can definitely compile the sdk without it (it will just grow 1% bigger ;-)). If that's an acceptable middle ground, I suggest building the sdk without it, but leaving it as a default (and have the Atom build to add the |
sgtm! I tried adding this to my start-up script:
which changed the failure mode, but did hit another exception. |
This is so the Atom plugin doesn't need to regenerate the SDK (it still needs to be compiled with --no-destructure-named-params, though, until Atom is updated to more ES6-compliant node/Chrome).
Compile the sdk with --no-destructure-named-params (#396)
@devoncarew Let us know if this is still an issue. Destructuring has been disabled by default. We're also now regressing on Electron (the Chrome 47 version - non-trivial to move that earlier as our karma/travis version doesn't make it easy to run older Electron with --harmony). This would have caught the destructuring issue early. |
Thanks! Will re-test w/ the latest DDC. |
tentatively closing, let us know if it reoccurs! |
Sorry, yup, it's working for me again. |
It looks like the destructuring commit broke Atom (c9d909c) ... probably because they're on an older version of Chrome.
I think the new code has fallback logic already in some cases, so we could likely add a flag to turn that on always.
CC @devoncarew @vsmenon
The text was updated successfully, but these errors were encountered: