eslint-import-resolver-node

v0.3.9

Node default behavior import resolution plugin for eslint-plugin-import. For more information about how to use this package see README

Latest version published 1 year ago

License: MIT

NPM

GitHub

Package Health Score

88 / 100

security
No known security issues
popularity
Key ecosystem project
maintenance
Sustainable
community
Active

Explore Similar Packages

Security

No known security issues

All security vulnerabilities belong to production dependencies of direct and indirect packages.

Security and license risk for significant versions

All Versions

Version				Vulnerabilities	License Risk
0.3.9	\|	08/2023	Popular	0 C 0 H 0 M 0 L	0 H 0 M 0 L
0.2.3	\|	08/2016		0 C 0 H 0 M 0 L	0 H 0 M 0 L
0.1.1	\|	11/2015		0 C 0 H 0 M 0 L	0 H 0 M 0 L

License

MIT

Security Policy

Yes

Is your project affected by vulnerabilities?

Scan your projects for vulnerabilities. Fix quickly with automated fixes. Get started with Snyk for free.

Get started free

Popularity

Key ecosystem project

Weekly Downloads (18,909,417)

GitHub Stars: 5.59K
Forks: 1.57K
Contributors: 350

Direct Usage Popularity

The npm package eslint-import-resolver-node receives a total of 18,909,417 downloads a week. As such, we scored eslint-import-resolver-node popularity level to be Key ecosystem project.

Based on project statistics from the GitHub repository for the npm package eslint-import-resolver-node, we found that it has been starred 5,594 times.

Downloads are calculated as moving averages for a period of the last 12 months, excluding weekends and known missing data points.

Community

Active

Readme.md: Yes
Contributing.md: Yes
Code of Conduct: Yes
Contributors: 350
Funding: Yes

A good and healthy external contribution signal for eslint-import-resolver-node project, which invites more than one hundred open source maintainers to collaborate on the repository.

Embed Package Health Score Badge

Maintenance

Sustainable

Commit Frequency

Open Issues: 529
Open PR: 94
Last Release: 1 year ago
Last Commit: 6 days ago

Further analysis of the maintenance status of eslint-import-resolver-node based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Sustainable.

An important project maintenance signal to consider for eslint-import-resolver-node is that it hasn't seen any new versions released to npm in the past 12 months, and could be considered as a discontinued project, or that which receives low attention from its maintainers.

As a healthy sign for on-going project maintenance, we found that the GitHub repository had at least 1 pull request or issue interacted with by the community.

Keep your project healthy

Check your package.json

Ensure all the packages you're using are healthy and well-maintained

Snyk Vulnerability Scanner

Get health score & security insights directly in your IDE

Package

Node.js Compatibility: not defined

Age: 9 years
Dependencies: 3 Direct
Versions: 17
Install Size: 5.29 kB
Dist-tags: 2
# of Files: 4
Maintainers: 3
TS Typings: No

eslint-import-resolver-node has more than a single and default latest tag published for the npm package. This means, there may be other tags available for this package, such as next to indicate future releases, or stable to indicate stable releases.

Not sure how to use eslint-import-resolver-node?

To help you get started, we've collected the most common ways that eslint-import-resolver-node is being used within popular public projects.

elastic / kibana / packages / kbn-eslint-import-resolver-kibana / import_resolver_kibana.js View on Github

function tryNodeResolver(importRequest, file, config) {
  return nodeResolver.resolve(
    importRequest,
    file,
    // we use Object.assign so that this file is compatible with slightly older
    // versions of node.js used by IDEs (eg. resolvers are run in the Electron
    // process in Atom)
    Object.assign({}, config, {
      extensions: ['.js', '.json', '.ts', '.tsx'],
      isFile,
    })
  );
}

View more ways to use eslint-import-resolver-node

eslint-import-resolver-node

Default Node-style module resolution plugin for eslint-plugin-import.

Published separately to allow pegging to a specific version in case of breaking changes.

Config is passed directly through to resolve as options:

settings:
  import/resolver:
    node:
      extensions:
        # if unset, default is just '.js', but it must be re-added explicitly if set
        - .js
        - .jsx
        - .es6
        - .coffee

      paths:
        # an array of absolute paths which will also be searched
        # think NODE_PATH
        - /usr/local/share/global_modules

      # this is technically for identifying `node_modules` alternate names
      moduleDirectory:

        - node_modules # defaults to 'node_modules', but...
        - bower_components

        - project/src  # can add a path segment here that will act like
                       # a source root, for in-project aliasing (i.e.
                       # `import MyStore from 'stores/my-store'`)

or to use the default options:

settings:
  import/resolver: node

eslint-import-resolver-node dependencies

debug is-core-module resolve

eslint-import-resolver-node development dependencies

chai mocha nyc

FAQs

What is eslint-import-resolver-node?

Node default behavior import resolution plugin for eslint-plugin-import. Visit Snyk Advisor to see a full health score report for eslint-import-resolver-node, including popularity, security, maintenance & community analysis.

Is eslint-import-resolver-node popular?

The npm package eslint-import-resolver-node receives a total of 18,909,417 weekly downloads. As such, eslint-import-resolver-node popularity was classified as a key ecosystem project. Visit the popularity section on Snyk Advisor to see the full health analysis.

Is eslint-import-resolver-node well maintained?

We found indications that eslint-import-resolver-node maintenance is sustainable demonstrating some project activity. We saw a total of 350 open source contributors collaborating on the project. See the full package health analysis to learn more about the package maintenance status.

Is eslint-import-resolver-node safe to use?

The npm package eslint-import-resolver-node was scanned for known vulnerabilities and missing license, and no issues were found. Thus the package was deemed as safe to use. See the full health analysis review.

Last updated on 21 December-2024, at 01:12 (UTC).

Build a secure application checklist

Select a recommended open source package

Minimize your risk by selecting secure & well maintained open source packages

DONE

Scan your app for vulnerabilities

Scan your application to find vulnerabilities in your: source code, open source dependencies, containers and configuration files

SCAN NOW

Fix identified vulnerabilities

Easily fix your code by leveraging automatically generated PRs

AUTO FIX

Monitor for new issues

New vulnerabilities are discovered every day. Get notified if your application is affected

MONITOR APP

Package Health Score

Explore Similar Packages

Security and license risk for significant versions

Is your project affected by vulnerabilities?

Weekly Downloads (18,909,417)

Direct Usage Popularity

Embed Package Health Score Badge

Commit Frequency

Keep your project healthy

Check your package.json

Snyk Vulnerability Scanner

Not sure how to use eslint-import-resolver-node?

eslint-import-resolver-node

eslint-import-resolver-node dependencies

eslint-import-resolver-node development dependencies

FAQs

What is eslint-import-resolver-node?

Is eslint-import-resolver-node popular?

Is eslint-import-resolver-node well maintained?

Is eslint-import-resolver-node safe to use?

Build a secure application checklist

Select a recommended open source package

Scan your app for vulnerabilities

Source Code

Open Source

Container

Config

Fix identified vulnerabilities

Monitor for new issues