Use source.js.regexp provided by the Javascript grammar #1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've been working on improving the grammar compiler for Linguist and I noticed it reporting this problem:
This is caused by the babel grammar never including the
Regular Expressions (JavaScriptNext).YAML-tmLanguage
andRegular Expressions (JavaScriptNext).tmLanguage
files in babel@cc420f2 when it started out.Rather than including them and taking our fork too much further away from upstream, I'm switching this to use
source.js.regexp
as provided by the Javascript grammar we use on Linguist. Quite a few other grammars in Linguist use this, so adding another shouldn't be the end of the world. It does however mean that this becomes another grammar that'll start reporting problems if/when we replace the Javascript grammar as I attempted in github-linguist/linguist#3044 (comment)