search

michaelgmcd / vscode-language-babel

VSCode syntax highlighting for today's JavaScript
https://marketplace.visualstudio.com/items?itemName=mgmcdermott.vscode-language-babel
MIT License
131 stars 17 forks source link

Syntax highlighting option doesn't appear in list #59

Closed karmeleon closed 4 years ago

karmeleon commented 4 years ago

When I open any file and open the syntax highlighting menu, I don't see "Babel JavaScript". It used to work, but at some point it stopped appearing. I don't see anything in the inspector that seems relevant. I've tried deleting all my extensions and settings and only installing this extension, but it didn't help. Let me know if there are any logs or anything that might help!

VSCode 1.40.1 Windows 10 x64 Enterprise 1903

ThaJay commented 4 years ago

The setting used for .js files (the ones that were configured to use this) have also reverted to just JavaScript.

mdrx-io commented 4 years ago

Anyone know offhand which was the last version of VSCode to have it working?

karmeleon commented 4 years ago

Ah I figured it out! I'm using VSCode Remote SSH, and when I'm connected the extensions menu shows that the Babel JavaScript extension is "Enabled on 'SSH: [my ssh server name]' and disabled locally.". If I open a new, local VSCode window and open a new file, the extension is installed and I can successfully enable the Babel JS syntax highlighting.

The fix is to tag this extension's package.json with extensionKind: ["ui"] as outlined in the VSC remote extension docs. As a quick local fix until a new version can be released, you can force the extension to be ui installed by copypasting this into your settings.json:

"remote.extensionKind": {
    "mgmcdermott.vscode-language-babel": ["ui"]
},

Reload the window and Babel JavaScript will appear as a syntax highlighting option, with the extension showing up as installed locally.

Addendum: you may need to open a non-SSH window and install the extension there; otherwise, VSC may only install the extension on your remote box.

ThaJay commented 4 years ago

@karmeleon I think this issue has been solved and you are posting about a different issue.

michaelgmcd commented 4 years ago

Cleaning up some issues. It seems like this is fixed. Please comment here if that is not the case.