babel-eslint not respecting babel config?

[unbracketed]

I have the following in my package.json:

"babel": {
    "stage": 0
  },
"standard": {
    "parser": "babel-eslint"
}

The stage 0 is for decorators, etc. When I run standard in my project directory, I get no errors. However I'm getting a warning by the linter on a @decorator about illegal token. Adding the 'stage 0' stanza is what enabled standard to pass on the command line. Do you have any insight about making sure the proper parser/transforms/configs are getting picked up by the linter?

[ricardofbarros]

Will look onto this, but most certainly standard is looking in package.json for babel key

[ricardofbarros]

Hmm, do you have babel-eslint installed as a local dependency? Or you have it installed as a global?

[unbracketed]

IIRC (on another machine) babel-eslint is installed globally. I'll poke at it some more.

[blakeembrey]

Doesn't appear to work for me either. Standard actually parses fine using the CLI, but the linter is erroring - like it isn't using the parser option from package.json. All dependencies are installed locally, not globally.

[unbracketed]

I've seen the behavior on multiple OS's: OSX and Ubuntu

[jamescostian]

I experience it on Windows, with babel-eslint installed globally and locally, and a similar package.json (babel stage 1, and babel-eslint set as the parser) On Tue, Aug 18, 2015 at 5:13 PM Brian Luft notifications@github.com wrote:

I've seen the behavior on multiple OS's: OSX and Ubuntu

— Reply to this email directly or view it on GitHub https://github.com/ricardofbarros/linter-js-standard/issues/40#issuecomment-132371746 .

[jamescostian]

I figured out how to fix this issue:

• Go to your Atom Settings
• Click on packages in the right sidebar
• Find linter-js-standard and click on it
• Under the Settings heading, check the box labeled "Honor Style Settings"
• Restart Atom

[unbracketed]

Thank you @jamescostian