Syntax highlighting different colours after update to 1.4

[kokono2]

Syntax highlighting has changed after I updated from 1.3.3 to 1.4 on Windows 10. I didn't see anything in the changelog so I'm assuming this is a bug.

Before the update (1.3.3):

After the update (1.4):

[jonathanprl]

I am also getting mixed up syntax colouring since the new update.

[farzd]

My JSX is all white

[spypsy]

keywords (in this case return) also seem to get mixed colours:


These are in the same file (JSX)

[50Wliu]

I didn't see anything in the changelog so I'm assuming this is a bug.

It is in fact in the changelog, just not very noticeable. Highlighting changes generally aren't part of the main changelog; you have to scroll down to the package name. The changes are as follows:

language-javascript

v0.100.0...v0.104.0

• atom/language-javascript#242 - Support for properties, function/method calls
• atom/language-javascript#255 - Reword opening line of readme file
• atom/language-javascript#256 - Add support for OpenJsCad
• atom/language-javascript#257 - improve function snippet
• atom/language-javascript#260 - Revert argumetns matching
• atom/language-javascript#264 - Fix 'this', 'super'
• atom/language-javascript#265 - Fix not a constant properties
• atom/language-javascript#269 - Fix comments in 'import', 'export' statements
• atom/language-javascript#272 - Allow $dollar$ signs in identifiers
• atom/language-javascript#266 - Support JSON5 files
• atom/language-javascript#277 - Tokenize let and var as storage.type.var.js

Please file any issues you have with the new syntax highlighting on the language-javascript repository (while also making sure that you aren't filing duplicates). We're working hard on improving the language support, but are aware that new bugs were introduced and more work is needed.

@antigirl, @spypsy: I'm not aware of how the JSX highlighting works, but unless it imports language-javascript, you may want to file it on the JSX repository instead.

[lock]

This issue has been automatically locked since there has not been any recent activity after it was closed. If you can still reproduce this issue in Safe Mode then please open a new issue and fill out the entire issue template to ensure that we have enough information to address your issue. Thanks!