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

dir-resolve

v1.0.2

Published

Extension for require.resolve which will resolve directories as well as files

Downloads

537

Readme

dir-resolve

Build Status

Purpose

An extension to require.resolve(). Traditionally, require.resolve() calls only work if you're working with files, as opposed to directories. For example:

node_modules/
  module/
    package.json
    test/
    index.js

You could run require.resolve('module') or require.resolve('module/package') and it would return paths to the files you expected. However, if you ran require.resolve('module/test') it would throw an exception. Since require.resolve() is designed to be the underlying mechanism upon which require() works, this is good and expected behavior. After all, what does requiring a directory even mean in node?

That said, I recently have had the desire of being able, to not require() the directories of my dependencies, but to get their locations via require.resolve() at which point this this behavior became a hindrance.

Thus, I have written dir-resolve. Meant to be an extension to require.resolve(), dir-resolve provides all the functionality of require.resolve() but adds the ability to resolve the directories of your dependencies as well.

Installation

npm install dir-resolve

Usage

var resolve = require('dir-resolve');

//Assuming the example above is at /path

resolve('module/package'); // -> '/path/node_modules/module/package.json'

resolve('module/test'); // -> '/path/node_modules/module/test'

In my testing it is compatible with Windows.

Development

Clone this repo and run npm install to run locally.

To run the tests do npm test or npm test -- --watch.