Enable more rules from the import plugin

[LinusU]

There seems to be a lot of rules from the import plugin that aren't enable, I think that we should consider enabling them.

Currently the ones enabled are:

"import/export": "error",
"import/first": "error",
"import/no-duplicates": "error",
"import/no-webpack-loader-syntax": "error",

which leaves a lot of rules not enabled:

Rules

Static analysis:

• Ensure imports point to a file/module that can be resolved. (no-unresolved)
• Ensure named imports correspond to a named export in the remote file. (named)
• Ensure a default export is present, given a default import. (default)
• Ensure imported namespaces contain dereferenced properties as they are dereferenced. (namespace)
• Restrict which files can be imported in a given folder (no-restricted-paths)
• Forbid import of modules using absolute paths (no-absolute-path)
• Forbid require() calls with expressions (no-dynamic-require)
• Prevent importing the submodules of other modules (no-internal-modules)
• Forbid Webpack loader syntax in imports (no-webpack-loader-syntax)

Helpful warnings:

• Report any invalid exports, i.e. re-export of the same name (export)
• Report use of exported name as identifier of default export (no-named-as-default)
• Report use of exported name as property of default export (no-named-as-default-member)
• Report imported names marked with @deprecated documentation tag (no-deprecated)
• Forbid the use of extraneous packages (no-extraneous-dependencies)
• Forbid the use of mutable exports with var or let. (no-mutable-exports)

Module systems:

• Report potentially ambiguous parse goal (script vs. module) (unambiguous)
• Report CommonJS require calls and module.exports or exports.*. (no-commonjs)
• Report AMD require and define calls. (no-amd)
• No Node.js builtin modules. (no-nodejs-modules)

Style guide:

• Ensure all imports appear before other statements (first)
• Report repeated import of the same module in multiple places (no-duplicates)
• Report namespace imports (no-namespace)
• Ensure consistent use of file extension within the import path (extensions)
• Enforce a convention in module import order (order)
• Enforce a newline after import statements (newline-after-import)
• Prefer a default export if module exports a single name (prefer-default-export)
• Limit the maximum number of dependencies a module can have (max-dependencies)
• Forbid unassigned imports (no-unassigned-import)
• Forbid named default exports (no-named-default)
• Forbid anonymous values as default exports (no-anonymous-default-export)

[feross]

no-absolute-path was enabled in the past, but we had to remove it because it was too slow. See: #861

Fortunately, it appears to have been sped up. If we benchmark it we can consider re-enabling it. import-js/eslint-plugin-import#803 (comment)

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[brodybits]

Add this to the list for Standard 14 (#1321)?

[feross]

I just re-enabled no-absolute-path. Which other rules are folks interested in seeing enabled?

[sonicdoe]

I’d be interested in import/order.

[Nomeasmo]

I find named and default pretty important. Are there any concerns?

[LinusU]

Issue for import/order: #1490

[mightyiam]

Here's another one. Easy profit.
https://github.com/benmosher/eslint-plugin-import/blob/HEAD/docs/rules/no-useless-path-segments.md

[dziku86]

What about Dynamic import() ? https://v8.dev/features/dynamic-import
Is it possible to enable new ECMAScript features without a custom parser?