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 🙏

© 2026 – Pkg Stats / Ryan Hefner

project-path-resolver

v0.1.0

Published

TS package, to get `project root dir path` and `script list with call order`, work stable

Readme

this is a npm package of TS, can get project root dir path and script list with call order.

it can get project root —— not modules root like other npm packages.

Features

  • Feature 1: different path to run script/project, always get same and right result.
  • Feature 2: no depend
  • Feature 3: it support pnpm all mode
  • Feature 4: work stable and well, also for issue below:
    • package find-project-root will return incorrect path, when you run modules/script out of the project.
    • here a local package project(just call A), and call project-root-directory package in it. When you import/require A in another project B via pnpm link, now it will get incorrect result in A —— is A but expect B.
  • Feature 5: support absolute or relative path for called script.
  • Feature 6: support convert pnpm modules path to general path(with project root).

Installation

To install the package, use the following command:

npm install project-path-resolver

yarn add project-path-resolver

pnpm add project-path-resolver

Usage

Import the package in your project as follows:

const { getProjectRootPath, getScriptCallList, getScriptListInCallStack } = require("project-path-resolver");
import { getProjectRootPath, getScriptCallList, getScriptListInCallStack } from "project-path-resolver";

Use it as follows:

// get project root dir path
console.log("ProjectRoot:", getProjectRootPath());
console.log("ProjectRoot:", getProjectRootPath({ rootFileName: "package.json" }));
console.log("ProjectRoot:", getProjectRootPath({ scriptListInCallStack: getScriptListInCallStack() }));
console.log(
	"ProjectRoot:",
	getProjectRootPath({ rootFileName: "package.json", scriptListInCallStack: getScriptListInCallStack() })
);

// get script list with call order
console.log("ScriptCallList:", getScriptCallList({ absolute: true, pnpmTranslate: true }));
console.log("ScriptCallList:", getScriptCallList({ absolute: true, pnpmTranslate: false }));
console.log("ScriptCallList:", getScriptCallList({ absolute: false, pnpmTranslate: false }));
console.log("ScriptCallList:", getScriptCallList({ absolute: false, pnpmTranslate: true }));

Contributing

Contributions are welcome! Please follow these steps:

  1. Fork the repository.
  2. Create a new branch for your feature or bug fix.
  3. Commit your changes and push the branch.
  4. Submit a pull request.

License

This project is licensed under the MIT License. See the LICENSE file for details.