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.
What kind of change does this PR introduce? (check at least one)
Does this PR introduce a breaking change? (check one)
Other information:
Now that ESLint is legitimately supported for Coffeescript as of Coffeescript v2.5.0 (via
eslint-plugin-coffee
), people using Coffeescript + Vue should be able to successfully run ESLint against their Coffeescript filesBut there have been a few issues encountered (see helixbass/eslint-plugin-coffee#27)
Specifically here, I needed to adjust the Vue CLI ESLint config to run against
.coffee
filesThese changes (plus vuejs/vue-eslint-parser#62) got ESLint working with Coffeescript in an example Vue project: https://github.com/helixbass/vue-coffee-eslint-example
But I'm not sure if further refinement is needed here for this to be flexible enough eg for projects that include
.coffee
files but don't have ESLint configured for Coffeescript, or for "hybrid" projects that include both Coffeescript + JS?