Brackets 1.8 does not support es6 in the UI portion of extensions in Linux #13096

catdad opened this Issue Feb 12, 2017 · 2 comments


None yet

2 participants

catdad commented Feb 12, 2017


Since Brackets updated to Node 6, I have been using it in my extension, which I primarily develop on Windows. On Windows, I can wrote es6 both in the main UI portion of an extension, as well as in a Node domain, and both work just fine. I loaded up the extension on Brackets 1.8 (the latest installed last night) on Ubuntu 16, and the UI portion of the extension gets syntax errors for all es6 code. The Node domain portion correctly executes using es6. When I remove es6 from the Ui portion of the extension, it works fine. Isn't all JavaScript code supposed to be running against Node 6 in Brackets 1.8?

Steps to Reproduce

  1. Load an extension with es6 in the main part of the extension on Windows -- for example, use template strings using backticks.
  2. Load same extension on Linux (I used Ubuntu 16).

Expected behavior:

Both Windows and Linux should execute that extension correctly.

Actual behavior:

Windows executes the extension correctly, but Linux received syntax errors.


Windows 10 using Brackets 1.8 (latest as of 2/11/17).
Ubuntu 16.04 using Brackets 1.8 (latest as of 2/11/17).

@catdad catdad referenced this issue in catdad/brackets-open-shell-here Feb 12, 2017
@catdad catdad getting rid of es6 in UI portion of the extension dda086d
petetnt commented Feb 13, 2017

Hi @catdad,

this is sadly a long running issue of the Linux version going out of date due to the difficulty of integrating/keeping up with CEF releases on the Linux version. The Brackets-Electron version that we now usually recommend to install over the CEF Linux version has vastly better support for ES2015 features AFAIK, but I understand that this might not be a solution for an extension.

Note to self: Might be worth adding that issue to the Linux Guide too:

catdad commented Feb 13, 2017

Thanks for the info, that's good to know. I already updated my code, so that's not a big deal. But it is good to know that I will need to test against Brackets-Electron, since that is officially recommended in the docs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment