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

pacscan

v0.2.0

Published

Scans for available packages

Downloads

4

Readme

8888888b.                   .d8888b.
888   Y88b                 d88P  Y88b
888    888                 Y88b.
888   d88P 8888b.   .d8888b "Y888b.    .d8888b  8888b.  88888b.
8888888P"     "88b d88P"       "Y88b. d88P"        "88b 888 "88b
888       .d888888 888           "888 888      .d888888 888  888
888       888  888 Y88b.   Y88b  d88P Y88b.    888  888 888  888
888       "Y888888  "Y8888P "Y8888P"   "Y8888P "Y888888 888  888

PacScan provides information about all available packages for your module at runtime by scanning node_modules as opposed to digging into dependency trees.

Build Coverage Dependencies Dev Dependencies License Release

Install

$ npm install --save pacscan

You'll need to have at least Node.js 4 or newer.

API

pacscan([options])

Scans for all packages available to your module asynchronously, returning a Promise to retrieve all of the package information, each of which will be in a format similar to the following:

{
  // The directory of the package
  directory: '/path/to/my-example-package/node_modules/example-server',
  // The file path of the "main" file for the package or null if it has none
  main: '/path/to/my-example-package/node_modules/example-server/server.js',
  // The name of the package
  name: 'example-server',
  // The version of the package
  version: '3.2.1'
}

The options parameter is entirely optional and supports the following:

| Option | Description | Default Value | | ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------- | ------- | | includeParents | Whether the highest level package directory should be scanned or only the lowest level base directory. | false | | knockknock | Any options to be passed to KnockKnock. limit will always be overridden to 1. | null | | path | The file/directory path from where to derive the base directory to be scanned. Path to module that called PacScan will be used when null. | null |

If you only want to list the packages available to your module/package:

const pacscan = require('pacscan');

module.exports = function() {
  pacscan()
    .then((packages) => {
      console.log(`${packages.length} packages found`);

      // ...
    });
};

However, if you're calling PacScan from within a library that is most likely being included in another package as a dependency. In these cases, you might want to know all of the packages available in the base package (i.e. the highest level package that is not a dependency itself). All that you need to do for this is to enable the includeParents option.

pacscan.sync([options])

A synchronous alternative to pacscan([options]).

const pacscan = require('pacscan');

module.exports = function() {
  const packages = pacscan.sync();

  console.log(`${packages.length} packages found`);

  // ...
};

pacscan.version

The current version of PacScan.

const pacscan = require('pacscan');

pacscan.version;
=> "0.2.0"

Bugs

If you have any problems with PacScan or would like to see changes currently in development you can do so here.

Contributors

If you want to contribute, you're a legend! Information on how you can do so can be found in CONTRIBUTING.md. We want your suggestions and pull requests!

A list of PacScan contributors can be found in AUTHORS.md.

License

See LICENSE.md for more information on our MIT license.

Copyright !ninja