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

resolve-app-path

v1.0.2

Published

Resolves an application's path.

Downloads

30

Readme

Application Path

NPM version Build Status Coverage Status Dependencies

Resolves an application's path.

Installation

$ npm install resolve-app-path

Usage

var resolve = require( 'resolve-app-path' );

resolve()

Resolves an application's path.

var root = resolve();
// returns <dirpath>

Notes

This module attempts the following strategies for resolving an application path:

  • When this module is a local module dependency, the module looks for an earliest ancestor node_modules directory, where we assume that the ancestor's parent is the application root. For example, given the following dependency chain

    /
    └── foo
        └── bar
            └── node_modules
                └── beep
                    └── node_modules
                        └── resolve-app-path
                            └── index.js

    the application root is /foo/bar.

  • When this module is loaded from a global Node path, the module tries to find the nearest package.json walking up from the current working directory. For example, given the following directory structure

    /
    └── Users
        └── <user>
            └── .node_modules
                └── resolve-app-root
                    └── index.js
    └── foo
        └── bar
            └── app
                └── root
                    └── package.json
                    └── bin
                        └── cli

    and

    $ cd /foo/bar/app/root
    $ node ./bin/cli

    the application root is /foo/bar/app/root.

  • When an alternative dependency strategy is used, e.g., copy and paste or git submodule, where this module is not located in a node_modules directory, the module also attempts to find the nearest package.json walking up from the current working directory. For example, given the following directory structure,

    /
    └── foo
        └── bar
            └── app
                └── root
                    └── package.json
                    └── libs
                        └── resolve-app-root
                            └── index.js

    the application root is /foo/bar/app/root.

  • When none of the above methods resolve a root directory, the module uses require.main.filename as a fallback. For example, given the following directory structure,

    /
    └── foo
        └── bar
            └── app
                └── root
                    └── index.js
            └── resolve-app-root
                └── index.js

    where, in app/root/index.js,

    var root = require( './../../resolve-app-path' );

    and

    $ cd /foo/bar
    $ node ./app/root

    the application root is /foo/bar/app/root, as the main requiring file is index.js in /foo/bar/app/root.

Examples

var path = require( 'path' ),
	root = require( 'resolve-app-path' );

var parts = root().split( path.sep );
console.log( parts );

To run the example code from the top-level application directory,

$ node ./examples/index.js

Tests

Unit

Unit tests use the Mocha test framework with Chai assertions. To run the tests, execute the following command in the top-level application directory:

$ make test

All new feature development should have corresponding unit tests to validate correct functionality.

Test Coverage

This repository uses Istanbul as its code coverage tool. To generate a test coverage report, execute the following command in the top-level application directory:

$ make test-cov

Istanbul creates a ./reports/coverage directory. To access an HTML version of the report,

$ make view-cov

License

MIT license.

Copyright

Copyright © 2015. Athan Reines.