New Case Study:See how Anthropic automated 95% of dependency reviews with Socket.Learn More
Socket
Sign inDemoInstall
Socket

@elastic/eslint-import-resolver-kibana

Package Overview
Dependencies
Maintainers
18
Versions
9
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@elastic/eslint-import-resolver-kibana

Kibana eslint-plugin-import resolver for Kibana

  • 2.0.0
  • latest
  • Source
  • npm
  • Socket score

Version published
Weekly downloads
23
decreased by-34.29%
Maintainers
18
Weekly downloads
 
Created
Source

@elastic/eslint-import-resolver-kibana

Resolver for Kibana imports, meant to be used with eslint-plugin-import.

Usage

Specify this resolver with the import/resolver setting in your eslint config file:

# .eslintrc.yml
settings:
  import/resolver: "@elastic/eslint-import-resolver-kibana"

Settings

NOTE: All relative paths are resolved as relative to the project root, which is determined by walking up from the first linted file and looking for a package.json file. If your project has multiple package.json files then make sure to specify the rootPackageName setting.

PropertyDefaultDescription
rootPackageNamenullThe "name" property of the root package.json file. If your project has multiple package.json files then specify this setting to tell the resolver which package.json file sits at the root of your project.
pluginPaths[] if rootPackageName is set, otherwise [.]Array of relative paths which contain a Kibana plugin. Plugins must contain a package.json file to be valid.
pluginDirs[]Array of relative paths pointing to directories which contain Kibana plugins. Plugins must contain a package.json file to be valid.

Settings Usage

To specify additional config add a : after the resolver name and specify the argument as key-value pairs:

# .eslintrc.yml
settings:
  import/resolver:
    "@elastic/eslint-import-resolver-kibana":
      # if your project has multiple package.json files
      rootPackageName: my-project
      
      # if your project stores plugin source in sub directories you can specify
      # those directories via `pluginPaths`.
      pluginPaths:
        - ./plugin-one
        - ./plugin-two
        
      # if all of your plugins have the same parent directory you can specify
      # that directory and we will look for plugins there
      pluginDirs:
        - ./kibana-plugins

See the resolvers docs or the resolver spec for more details.

Debugging

For debugging output from this resolver, run your linter with DEBUG=eslint-plugin-import:resolver:kibana.

This resolver defers to eslint-import-resolver-node and eslint-import-resolver-webpack for all of it's actual resolution logic. To get debugging output from all resolvers use DEBUG=eslint-plugin-import:resolver:*.

FAQs

Package last updated on 12 Dec 2017

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc