</>PackageGraphPackageGraph

find-up

npmv8.0.0TypeScript

Find a file or directory by walking up parent directories

Safe to adopt

Yes — find-up scores well across adoption, maintenance, weight, supply chain, and licensing. No download data reported for this package yet. Last published 359 days ago.

  • ?Adoption: grade ?, Not reported by this registry.

    No download data reported for this package yet.

  • BMaintenance: grade B, Good.

    Last published 359 days ago.

  • AWeight: grade A, Excellent.

    Pulls in 5 transitive packages, about 61 KB installed (at least — some of the tree is still being crawled).

  • BSupply chain: grade B, Good.

    This package has a single maintainer (bus factor of 1).

  • ALicense: grade A, Excellent.

    MIT — permissive, with no copyleft found in the dependency tree.

Grades are computed deterministically from registry metadata collected by PackageGraph — downloads, dependents, publish dates, the resolved dependency tree, maintainer count, and declared licenses. No third-party scores are used.

Install cost

What you actually take on by adding find-up to a project.

2
Direct dependencies

Runtime packages this one declares itself.

5
Total installed

Distinct packages in the full runtime tree, deduplicated the way a package manager would.

61 KB
Install size

Unpacked size of this package plus its entire runtime tree.

4
Tree depth

Longest resolved dependency chain below this package.

Part of this dependency tree has not been crawled yet, so these figures are a lower bound rather than a final total.

Licenses in the dependency tree

MIT

Every license you inherit by installing find-up, not just its own. Check this before a legal review, not after.

Compatibility

Node.js
node >=20
Module format
ESM only
TypeScript
Types included
Install scripts
None

Quick start

A usage example from the find-up README.

import path from 'node:path';
import {pathExists} from 'path-exists';
import {findUp, findDown} from 'find-up';

console.log(await findUp('unicorn.png'));
//=> '/Users/sindresorhus/unicorn.png'

console.log(await findUp(['rainbow.png', 'unicorn.png']));
//=> '/Users/sindresorhus/unicorn.png'

console.log(await findUp(async directory => {
	const hasUnicorn = await pathExists(path.join(directory, 'unicorn.png'));
	return hasUnicorn && directory;
}, {type: 'directory'}));
Example truncated — see the full README.

find-up vs the alternatives

Packages solving a similar problem in the npm ecosystem, compared on the signals that drive an adoption decision.

PackageWeekly downloadsDependentsLicenseLast release
find-upthis page04MIT11 months ago
pkg-dirdeprecated01MIT1 day ago
find-up-simple02MIT1 day ago
escalade136.6M3MIT1 day ago
make-dir02MIT1 day ago
locate-path01MIT1 day ago

Dependencies

Declared by find-up v8.0.0. Runtime dependencies are installed with the package; dev dependencies are not.

Dev (5)

ava ^6.4.1is-path-inside ^4.0.0tempy ^3.1.0tsd ^0.33.0xo ^1.2.2

Used by

Popular packages that depend on find-up.

Relationship graph

Dependencies (left) and dependents (right) of find-up.

Frequently installed together

Release history

1 release in the last two years, typically about 124 days apart.

Recent versions of find-up
VersionPublishedSizeLicense
8.0.0latest11 months ago24 KBMIT
7.0.02 years ago16 KBMIT
6.3.04 years ago17 KBMIT
6.2.04 years ago16 KBMIT
6.1.05 years ago12 KBMIT
6.0.05 years ago12 KBMIT
5.0.06 years ago11 KBMIT
4.1.07 years ago11 KBMIT
4.0.07 years ago10.0 KBMIT
3.0.08 years ago4.7 KBMIT
2.1.09 years agoMIT
2.0.010 years agoMIT
1.1.210 years agoMIT
1.1.110 years agoMIT
1.1.010 years agoMIT

Overview

find-up is an npm package that find a file or directory by walking up parent directories. It has 4 known dependents in the graph. The latest version is 8.0.0, released under the MIT license.

Who should use it

Teams working in the npm ecosystem who need find a file or directory by walking up parent directories and value a focused solution.

When not to use it

Consider an alternative if you need to or if a more actively-maintained option better fits your npm stack.

Pros

  • Ships TypeScript type definitions.
  • Clear open-source license (MIT).

Cons

  • No significant drawbacks detected from available metadata.

Auto-generated from collected registry metadata. No external claims are inferred.

Maintainers

Keywords

Funding

Frequently asked questions

Should I use find-up?

Yes — find-up scores well across adoption, maintenance, weight, supply chain, and licensing. No download data reported for this package yet. Last published 359 days ago.

How do I install find-up?

Run `npm install find-up` to add find-up to your npm project.

How many dependencies does find-up have?

find-up declares 7 direct dependencies and pulls in 5 packages in total once its runtime tree is resolved totalling about 61 KB on disk.

What license is find-up released under?

find-up is distributed under the MIT license.

How popular is find-up?

npm does not publish download counts. Within PackageGraph's crawl, 4 known packages depend on find-up.

Is find-up still maintained?

The most recent release of find-up (v8.0.0) was published 11 months ago.

Does find-up run install scripts?

No. find-up does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.