Skip to content
This repository has been archived by the owner on Aug 7, 2023. It is now read-only.

Stopped working with language-babel #348

Closed
haveanicedavid opened this issue Sep 29, 2016 · 4 comments
Closed

Stopped working with language-babel #348

haveanicedavid opened this issue Sep 29, 2016 · 4 comments
Labels

Comments

@haveanicedavid
Copy link

Upon updating to the most recent version of language-babel, JSHint linting stopped working.

'Lint JSX' is currently enabled, and i'm not sure how to troubleshoot. Another JSHint plugin seems to be working, and switching the language to vanilla JS instead of Language-babel also seems to work.

Is there something else I can do to troubleshoot?

@Arcanemagus
Copy link
Member

v3 removed the support of linting JSX code. I could find no mention on the JSHint site stating that it actually supports this, and we kept getting errors related to running on that code. I would recommend you check out other linters that are meant to support that setup, such as ESLint with the proper plugins.

@Arcanemagus
Copy link
Member

Arcanemagus commented Oct 12, 2016

Filed an issue on language-babel about this.

@Arcanemagus
Copy link
Member

It sounds like JSX people are terrible, and just use .js for JSX files, it could be "fixed" so that it only marks files as source.js.jsx when in a JSX block, but that could lead to issues of running source.js linters on a file that is partially JSX.

I would recommend disabling language-babel if you are not using the JSX features, or just remembering to change the file language to JS on regular JS files.

@AnnanFay
Copy link

It sounds like JSX people are terrible, and just use .js for JSX files

I realise this issue is a bit old but I am just coming across this.

@Arcanemagus The official recommendation appears to be to use .js for JSX files.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants