npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@snyk/cli-interface

v2.14.0

Published

Snyk CLI interface definitions

Downloads

229,126

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.