Bump eslint-plugin-import to avoid vulnerability in dependency
This commit is contained in:
parent
10695e6a20
commit
ed9506bbaf
1660 changed files with 67726 additions and 27926 deletions
8
node_modules/eslint-plugin-import/docs/rules/no-absolute-path.md
generated
vendored
8
node_modules/eslint-plugin-import/docs/rules/no-absolute-path.md
generated
vendored
|
|
@ -1,7 +1,13 @@
|
|||
# import/no-absolute-path: Forbid import of modules using absolute paths
|
||||
# import/no-absolute-path
|
||||
|
||||
🔧 This rule is automatically fixable by the [`--fix` CLI option](https://eslint.org/docs/latest/user-guide/command-line-interface#--fix).
|
||||
|
||||
<!-- end auto-generated rule header -->
|
||||
|
||||
Node.js allows the import of modules using an absolute path such as `/home/xyz/file.js`. That is a bad practice as it ties the code using it to your computer, and therefore makes it unusable in packages distributed on `npm` for instance.
|
||||
|
||||
This rule forbids the import of modules using absolute paths.
|
||||
|
||||
## Rule Details
|
||||
|
||||
### Fail
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue