You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now that all LTS versions of node other than 18.x (which is soon to fall out of LTS) support require(esm), it means we should be able to move to ES modules.
ESLint will internally already import(module) plugins when used by legacy eslintrc configs.
So the people this would affect are those using CommonJS flat configs in a version of Node below 20.
Given they're already using a version of ESLint which supports flat config, they could quite easily move their config to eslint.config.mjs without having to migrate their whole repo to ES modules.
This all tells me it should be a fairly safe move to change this repo to type: "module". What do you think?
The text was updated successfully, but these errors were encountered:
Now that all LTS versions of node other than 18.x (which is soon to fall out of LTS) support
require(esm)
, it means we should be able to move to ES modules.ESLint will internally already
import(module)
plugins when used by legacyeslintrc
configs.So the people this would affect are those using CommonJS flat configs in a version of Node below
20
.Given they're already using a version of ESLint which supports flat config, they could quite easily move their config to
eslint.config.mjs
without having to migrate their whole repo to ES modules.This all tells me it should be a fairly safe move to change this repo to
type: "module"
. What do you think?The text was updated successfully, but these errors were encountered: