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

@danielbayley/uproot

v0.1.3

Published

Reliable method to find the root path of your git repo, [p]npm/yarn package or app.

Downloads

9

Readme

Uproot

Reliable method to find the root path of your git repository, [p]npm/yarn package, or app.

The algorithm is primarily reliant on git rev-parse --show-toplevel, but will fallback on the following glob patterns to determine the root path:

| Path/pattern | Examples | |:------------------------|:-------------------------------------------------| | pnpm-*.yaml | pnpm-workspace.yaml, pnpm-lock.yaml | | package.{yaml,json} | package.json, package.yaml | | package-lock.json | | | npm-shrinkwrap.json | | | yarn.lock | | | .git* | .gitignore, .gitattributes, .github/ | | .npmrc | | | .editorconfig | | | LICEN[SC]E* | LICENSE.md | | .vscode/ | | | packages/ | | | src/ | | | public/ | |

Examples

import {root} from "@danielbayley/uproot"
console.log(root) // ~/path/to/project/root
import {uproot} from "@danielbayley/uproot"

const cwd  = import.meta.dirname
const root = await uproot({ cwd })

You can override the above search patterns with the match option:

const root = await uproot({ match: ["tsconfig.json"] })

or append an additional pattern to find:

import { uproot, match } from "@danielbayley/uproot"

match.push("tsconfig.json")
const root = await uproot({ match })

Any additional options will be passed onto matchup:

import path from "node:path"

const object = await uproot({ cwd, parse: true })
const root = path.format(object)
console.log(root) // ~/path/to/project/root

Install

pnpm install @danielbayley/matchup

[!IMPORTANT] This package is ESM only, so must be imported instead of required, and depends on Node.js >=20.

Specify this requirement with engines and/or devEngines:

// package.json
"type": "module",
"engines": {
  "node": ">=20"
},
"devEngines": {
  "runtime": {
    "name": "node",
    "version": ">=20"
  }
},

License

MIT © Daniel Bayley