New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Docs: Clarify ecmaVersion doesn't imply globals (refs #9812) #11364

Merged

not-an-aardvark merged 1 commit into eslint:master from maxwell-k:patch-1

Feb 10, 2019

Commits on Feb 9, 2019

Docs: Clarify ecmaVersion doesn't imply globals (refs #9812 )

Before this change users can mistakenly assume that setting
parserOptions.ecmaVersion automatically implies the globals from that
ecmaVersion are available, in fact globals are controlled by a separate
environment setting that is not affected by ecmaVersion.

This PR implements the suggestion from
#9812

maxwell-k committed Feb 9, 2019