Monokai, after Update, get async keyword color back (green)

[rokstar]

After update Monokai theme changed color for async keyword in function declaration (JS)

How to make it green back?

I have plugin for resources exploring, but I don’t know what to look for and where to change.

Thanks!

[rwols]

Could you put the cursor on the word async and then go to Tools -> Developer -> Show Scope Name? What does the pop-up box say?

[rokstar]

I have slightly modified my own syntax highlighting, but I don’t touch there any of scope appeared in my screen shot

[rwols]

It should include

storage.type.js

Is there any package you’re using to highlight JS?

[rokstar]

this is my user sublime-syntax file:

%YAML 1.2
---
name: JavaScript Appkit
file_extensions:
  - js
scope: source.js.appkit
contexts:
  main:
    - match: ""
      push: scope:source.js
      with_prototype:
      - match: 'styles: `'
        push:
          - meta_content_scope: source.css.embedded.html
          - include: scope:source.css
          - match: '`'
            pop: true
      - match: '`'
        push:
          - meta_content_scope: text.html.basic.embedded.js
          - include: scope:text.html.basic
          - match: '@@\w+|@\w+'
            scope: entity.name.tag.block.any.html
          - match: '`'
            pop: true

[rokstar]

this is inside object literal:

var obj = {
async myFunc() { … }
}

[FichteFoll]

This looks like an oversight in the JavaScript syntax to me. async is not recognized for function definitions in object literals (with the function providing the key name).

I suggest opening an issue at https://github.com/sublimehq/Packages/issues and including some example code, like this:

var obj = {
    async myFunc() { ... }
}

async function function_name(argument) {
    // body...
}

[ThomSmith]

It’s worth noting that there’s a huge JavaScript change awaiting review: https://github.com/sublimehq/Packages/pull/1009 .

Once that PR is sorted out, I should be able to take care of all outstanding JS issues. It’s tricky now, because any changes not based on that PR would be unlikely to gracefully merge, whereas adding more fixes to that PR might further delay the review process.