language-javascript-jsx
language-javascript-jsx copied to clipboard
JavaScript with JSX Bundle for Atom
I am having strange highlighting issues with v0.3.7. Most of the test appears read. Basically its the same happening with this package what happend once to the language-javascript package. https://github.com/atom/language-javascript/issues/258...
e.g. ``` const bar = 42; const baz = `foo ${bar}`; // 'foo 42' ``` `foo` should be styled as string and `${bar}` should be styled as variable. http://babeljs.io/docs/learn-es2015/#template-strings
I noticed a line collapsing on top of another line. The behavior can be seen here:  The behavior went away when I disabled this package. I also strangely only...
Hi, I found a small bug on the latest version of the package. Whenever you write the hidden attribute on any component, with a value other than a string, i.e....
See below:
this is `Plain Text`  this is `JavaScript with JSX`  As u can see most ligatures are broken... Also the fat arrow ligature seems not broken in my example...
I find it hard to work with JSX in Atom Editor with this plugin since it skips a lot of ES6 features and also doesn't include the tons of JavaScript...
Stuff like `event` and `document` highlight as though they're special. When developing something for which these types are undefined or irrelevant (such as server-side node.js), it's annoying having these words...
So, I'm definitely only seeing this when I invoke a function, but it negates everything after that:  Not a big deal, but definitely looks worse when there are a...
When writing a new react component method in ES6 class syntax, I came across this nasty bug. Here is some context: ``` js export default class BlahBlah extends Component {...