Gathering detailed insights and metrics for eslint-import-resolver-custom-alias
Gathering detailed insights and metrics for eslint-import-resolver-custom-alias
Gathering detailed insights and metrics for eslint-import-resolver-custom-alias
Gathering detailed insights and metrics for eslint-import-resolver-custom-alias
Plugin for eslint-plugin-import to use custom alias
npm install eslint-import-resolver-custom-alias
Typescript
Module System
Node Version
NPM Version
JavaScript (100%)
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
MIT License
41 Stars
40 Commits
2 Forks
1 Watchers
5 Branches
1 Contributors
Updated on May 05, 2025
Latest Version
1.3.2
Package Id
eslint-import-resolver-custom-alias@1.3.2
Unpacked Size
7.33 kB
Size
2.86 kB
File Count
4
NPM Version
8.1.0
Node Version
16.13.0
Published on
May 14, 2023
Cumulative downloads
Total Downloads
Last Day
0%
NaN
Compared to previous day
Last Week
0%
NaN
Compared to previous week
Last Month
0%
NaN
Compared to previous month
Last Year
0%
NaN
Compared to previous year
This plugin will help you configure eslint-plugin-import to allow customized alias and extensions.
To install this plugin, run:
1npm install --dev eslint-import-resolver-custom-alias
or
1yarn add --dev eslint-import-resolver-custom-alias
1{ 2 "settings": { 3 "import/resolver": { 4 "eslint-import-resolver-custom-alias": { 5 "alias": { 6 "src": "./src" 7 }, 8 "extensions": [".js", ".jsx"], 9 "packages": [ 10 "packages/*" 11 ] 12 } 13 } 14 } 15}
Here, alias
is a key-value pair, where key
represents the alias, and value
represents
it's actual path. Relative path is allowed for value
. When used, it's relative to project
root, where command line is running. (i.e. root path will be process.cwd()
)
extensions
is an array of possible suffix. If not provided, default value will be [".js"]
.
packages
is an optional configuration. When using lerna to manage packages and use eslint at
root folder, packages
lets the resolver know where each package folder exist. This way, when
resolving alias, relative path will be resolved based on current package, instead of root folder.
Consider the file as an example:
1import * as utils from '@/utils';
Suppose the above file locates at ./packages/subfolder/src/components/button.jsx
and command is
running at root folder (i.e. ./
). If the resolver is configured the following way:
1{ 2 "settings": { 3 "import/resolver": { 4 "eslint-import-resolver-custom-alias": { 5 "alias": { 6 "@": "./src" 7 }, 8 "extensions": [".js", ".jsx"], 9 } 10 } 11 } 12}
Resolver will tries to find file at ./src/utils
folder. However, with packages
configured:
1{ 2 "settings": { 3 "import/resolver": { 4 "eslint-import-resolver-custom-alias": { 5 "alias": { 6 "@": "./src" 7 }, 8 "extensions": [".js", ".jsx"], 9 "packages": [ 10 "packages/*" 11 ] 12 } 13 } 14 } 15}
Resolver will try to find it at ./packages/subfolder/src/utils
folder instead.
One special alias is empty string ""
. If configured, the resolver will try to
add prefix in front of the path before resolving. For example, with following configuration
1{ 2 "settings": { 3 "import/resolver": { 4 "eslint-import-resolver-custom-alias": { 5 "alias": { 6 "": "./src" 7 }, 8 "extensions": [".js", ".jsx"], 9 "packages": [ 10 "packages/*" 11 ] 12 } 13 } 14 } 15}
The resolver will try to find the following import at path ./packages/subfolder/src/utils/helper
.
1import * as helper from 'utils/helper';
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
license file detected
Details
Reason
7 existing vulnerabilities detected
Details
Reason
Found 2/9 approved changesets -- score normalized to 2
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
project is not fuzzed
Details
Reason
security policy file not detected
Details
Reason
branch protection not enabled on development/release branches
Details
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Score
Last Scanned on 2025-07-07
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More