Package Exports
- @snyk/cli-interface
- @snyk/cli-interface/index.js
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@snyk/cli-interface) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
snyk-cli-interface
Interface definitions for interactions between Snyk CLI and associated components:
- plugins for analyzing various build systems
- monitor states sent to snyk.io website
This library should be only imported from Typescript.
The types can be imported in one of the following ways:
whole sub-module import from the top level
import { legacyPlugin as api } from '@snyk/cli-interface'; // use api.InspectOptions
"deep import" (discouraged but possible)
import { InspectOptions } from '@snyk/cli-interface/legacy/plugin';
The npm package does not follow the usual Snyk convention and
exports the build files in the root directory, not in dist, to enable "deep imports".
We still have to publish the package using the compiled files, because many tools in Node.js ecosystem assume that published libraries should be always in Javascript.