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
Bumping this issue as we are now supporting es6 imports in bedrock, so this means rules such as:
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)
Forbid a module from importing itself (no-self-import)
Forbid a module from importing a module with a dependency path back to itself (no-cycle)
Prevent unnecessary path segments in import and require statements (no-useless-path-segments)
Forbid importing modules from parent directories (no-relative-parent-imports)
Prevent importing packages through relative paths (no-relative-packages)
Are suddenly super useful. I would like to see no-unresolved immediately.
aljones15
changed the title
Evaluate eslint-plugin-import
Add eslint-plugin-import as a peerDependency to rules
Apr 1, 2022
This is an amazing plugin with a long history:
https://www.npmjs.com/package/eslint-plugin-import
probably 100% worth it, but need consensus on this one.
The text was updated successfully, but these errors were encountered: