overlookmotel / eslint-config-node Goto Github PK

Some rules are already enforced by eslint-plugin-import, which is used in @overlookmotel/eslint-config so produce double warnings.

e.g. require('./foo.js') where foo.js doesn't exist produces two different rule failures:

import/no-unresolved
node/no-missing-require

There are further circumstances where import and node plugin rules are both triggered for same require() / import.

NB Dynamic import import('./foo.js') where foo.js does not exist does not trigger import/no-unresolved rule but does trigger the node/no-missing-import rule. Not sure if this is due to options passed to import plugin.

ESM files are any which:

• Have .mjs extension
• Are inside a directory with a package.json file with type field set to 'module'

.mjs can be dealt with by adding:

overrides: [{
  files: ['*.mjs'],
  parserOptions: {
    sourceType: 'module'
  }
}]

Not sure how to tackle package.json type field.