"node" environment is missing `URL` global

Tell us about your environment

• ESLint Version: 4.19.1
• Node Version: 10.0.0
• npm Version: 5.6.0

What parser (default, Babel-ESLint, etc.) are you using? babel-eslint@8.2.3

Please show your full configuration:

Configuration

{
  "env": {
    "jest": true,
    "node": true
  },

  "extends": [
    "bespoke",
    "plugin:react/recommended"
  ],

  "parser": "babel-eslint"
}

What did you do? Please include the actual source code causing the issue, as well as the command that you used to run ESLint.

new URL(import.meta.url).pathname

eslint --ext .mjs --ignore-path .gitignore .

What did you expect to happen?

URL to be a known global when specifying "node": true. (SEE https://nodejs.org/api/url.html)

What actually happened? Please include the actual, raw output from ESLint.

4:17  error  'URL' is not defined                      no-undef

---

I’m using babel-eslint until import.meta is more widely supported.

[kaicataldo]

It looks like this was added in globals v11.5, which we updated to in ESLint v5. Updating to the latest version of ESLint will fix this. Thanks!

[platinumazure]

@medikoo That would result in a larger maintenance burden for us as different Node versions go into or out of LTS. I’m not sure we have the resources to maintain the Node globals as you suggested. That is why I offered the workaround.