Skip to content

upgrade to eslint@8 #2583

@trentm

Description

@trentm

If after we switch to eslint (#2579) is in, we should upgrade from the current eslint@6 to eslint@7. https://eslint.org/docs/user-guide/migrating-to-7.0.0

  • drops node v8 support
  • Deal with "no-var" rule. A quick run with the update to eslint-config-standard@16 results in ~2000 of these. I'm not sure if --fix will automatically fix these.
  167:7   warning  Unexpected var, use let or const instead  no-var

Note: Why not eslint@8 yet? The current latest is eslint@8, but eslint-config-standard and standard aren't ready for eslint@8 until eslint-config-standard@17 (https://github.com/standard/standard/blob/master/CHANGELOG.md#1700-0---2022-01-31), which is current in pre-release.

Update (2022-07-14): eslint-config-standard@17 is released now, so I believe moving to eslint@8 would be possible now. See #2820 and #2817

Metadata

Metadata

Assignees

No one assigned

    Labels

    agent-nodejsMake available for APM Agents project planning.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions