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

mresolve

v0.1.1

Published

Resolve module dependencies to paths

Downloads

5

Readme

npm version Build Status Coverage Status

mresolve

Resolve module dependencies to a list of possible paths.

npm install --save mresolve

This module doesn't access files directly and doesn't check if a file exists. It only access package.json files from your application and its dependants.

API

mresolve(opts)

Create a new resolver with the specified options:

  • base: your application / repository base path (default to process.cwd())
  • extensions: the list of possible extensions for a file (default to ['.js'])
  • moduleDirectory: the directory name where npm dependencies are located (default to node_modules)
  • paths: a lists of additional paths where files can be located (default to []). This is handy if you don't want to use relative paths when importing / requiring modules.

resolver.resolveDependency(dependency[, relativeTo])

Returns an object containing the following properties:

  • base: the base path specified in options
  • dependencyName: the name of your dependency as passed to the function (resolved if relative)
  • npmDepdendency: true or false depending if the dependency is external (located in opts.moduleDependency)
  • possiblePaths: a list of possible paths where this module could be found

If dependency is relative, do not forget to pass to the function the directory of the module where the dependency was found (relative to base path).

Usage

import mresolve from 'mresolve'

let resolver = resolve({
    base: process.cwd(),
    extensions: ['js'],
    moduleDirectory: 'node_modules',
    paths: []
});

resolver.resolveDependency('../components/dropdown', 'views');

// Will output:
// =>
// {
//     base: <your base path>,
//     dependencyName: components/dropdown,
//     npmDependency: false,
//     possiblePaths: ['components/dropdown.js', 'components/dropdown/index.js']
// }