Skip to content

Conversation

SimenB
Copy link
Contributor

@SimenB SimenB commented Oct 27, 2016

Probably a reason you haven't done it yet (other than the fact it's a breaking change), but it's annoying having ava override our setting just because we want to use recommended config, which means we have to specify ecmaVersion multiple places (as we only have ava in test dirs)

An idea might be to drop the version entirely from recommended? That's still breaking, though.

Could do require('eslint/package.json').version and check if it's new enough to keep it non-breaking?

@sindresorhus
Copy link
Member

An idea might be to drop the version entirely from recommended? That's still breaking, though.

I think the reason we set it is that AVA uses Babel, so you can use the latest syntax without setting anything. We should always have this to the latest mode ESLint provides.

We've already planned a breaking release, so can include this then.

@sindresorhus sindresorhus merged commit 0612a43 into avajs:master Nov 3, 2016
sindresorhus pushed a commit that referenced this pull request Nov 3, 2016
@SimenB SimenB deleted the ecma-version branch November 3, 2016 09:23
@SimenB
Copy link
Contributor Author

SimenB commented Nov 3, 2016

We should always have this to the latest mode ESLint provides.

Would be cool if they accepted latest or something, kinda like https://babeljs.io/docs/plugins/preset-latest/

@sindresorhus
Copy link
Member

@SimenB Indeed. Open an issue on ESLint ;)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants