npmpackage.info

Gathering detailed insights and metrics for @stdlib/fs-resolve-parent-path

Gathering detailed insights and metrics for @stdlib/fs-resolve-parent-path

@stdlib/fs-resolve-parent-path - 0.2.2 | npmpackage.info

@stdlib/fs-resolve-parent-path

Resolve a path by walking parent directories.

0.2.2

2

Apache-2.0

JavaScript

4.10 kB

Installations

npm install @stdlib/fs-resolve-parent-path

Developer Guide

BETA

Typescript

Yes

Module System

CommonJS

Min. Node Version

>=0.10.0

Node Version

16.20.2

NPM Version

8.19.4

Pull Requests

Open

0

Total

0

Closed

0

Issues

Open

0

Total

0

Closed

0

Releases

Unable to fetch releases

Languages

1

JavaScript

JavaScript (100%)

Developer

Download Statistics

Total Downloads

79,040,517

Last Day

91,561

Last Week

463,345

Last Month

2,004,087

Last Year

24,457,571

GitHub Statistics

Apache-2.0 License

2 Stars

70 Commits

3 Watchers

6 Branches

12 Contributors

Updated on Apr 07, 2025

Bundle Size

15.33 kB

Minified

4.10 kB

Minified + Gzipped

Bundlephobia

Sponsor this package

https://opencollective.com/stdlib

Maintainers

4

View All 12 Contributors

Package Meta Information

Latest Version

0.2.2

Package Id

@stdlib/fs-resolve-parent-path@0.2.2

Unpacked Size

45.41 kB

Size

11.24 kB

File Count

13

NPM Version

8.19.4

Node Version

16.20.2

Published on

Jul 27, 2024

Total Downloads

Cumulative downloads

Total Downloads

79,040,517

Last Day

23.3%

91,561

Compared to previous day

Last Week

2.4%

463,345

Compared to previous week

Last Month

3.5%

2,004,087

Compared to previous month

Last Year

-38.8%

24,457,571

Compared to previous year

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dependencies

9

@stdlib/assert-has-own-property @stdlib/assert-is-function @stdlib/assert-is-plain-object @stdlib/assert-is-string @stdlib/fs-exists @stdlib/process-cwd @stdlib/string-format @stdlib/utils-define-nonenumerable-read-only-property @stdlib/error-tools-fmtprodmsg

About stdlib...

We believe in a future in which the web is a preferred environment for numerical computation. To help realize this future, we've built stdlib. stdlib is a standard library, with an emphasis on numerical and scientific computation, written in JavaScript (and C) for execution in browsers and in Node.js.

The library is fully decomposable, being architected in such a way that you can swap out and mix and match APIs and functionality to cater to your exact preferences and use cases.

When you use stdlib, you can be absolutely certain that you are using the most thorough, rigorous, well-written, studied, documented, tested, measured, and high-quality code out there.

To join us in bringing numerical computing to the web, get started by checking us out on GitHub, and please consider financially supporting stdlib. We greatly appreciate your continued support!

Resolve Parent Path

Resolve a path by walking parent directories.

Installation

1npm install @stdlib/fs-resolve-parent-path

Usage

1var resolveParentPath = require( '@stdlib/fs-resolve-parent-path' );

resolveParentPath( path[, options], clbk )

Asynchronously resolves a path by walking parent directories.

1resolveParentPath( 'package.json', onPath );
2
3function onPath( error, path ) {
4    if ( error ) {
5        throw error;
6    }
7    console.log( path );
8    // => '...'
9}

The function accepts the following options:

dir: base directory from which to begin walking. May be either an absolute path or a path relative to the current working directory.

By default, the function begins walking from the current working directory. To specify an alternative directory, set the dir option.

1var opts = {
2    'dir': __dirname
3};
4resolveParentPath( 'package.json', opts, onPath );
5
6function onPath( error, path ) {
7    if ( error ) {
8        throw error;
9    }
10    console.log( path );
11    // => '...'
12}

resolveParentPath.sync( path[, options] )

Synchronously resolves a path by walking parent directories.

1var path = resolveParentPath.sync( 'package.json' );
2// returns '...'

The function accepts the same options as resolveParentPath().

Notes

If unable to resolve a path, both functions return null.
This implementation is not similar in functionality to core path.resolve. The latter performs string manipulation to generate a full path. This implementation walks parent directories to perform a search, thereby touching the file system. Accordingly, this implementation resolves a real absolute file path and is intended for use when a target's location in a parent directory is unknown relative to a child directory; e.g., when wanting to find a package root from deep within a package directory.

Examples

1var resolveParentPath = require( '@stdlib/fs-resolve-parent-path' );
2
3var opts = {
4    'dir': __dirname
5};
6
7/* Sync */
8
9var out = resolveParentPath.sync( 'package.json', opts );
10// returns '...'
11
12out = resolveParentPath.sync( 'non_existent_basename' );
13// returns null
14
15/* Async */
16
17resolveParentPath( 'package.json', opts, onPath );
18resolveParentPath( './../non_existent_path', onPath );
19
20function onPath( error, path ) {
21    if ( error ) {
22        throw error;
23    }
24    console.log( path );
25}

Notice

This package is part of stdlib, a standard library for JavaScript and Node.js, with an emphasis on numerical and scientific computing. The library provides a collection of robust, high performance libraries for mathematics, statistics, streams, utilities, and more.

For more information on the project, filing bug reports and feature requests, and guidance on how to develop stdlib, see the main project repository.

Community

License

Copyright

Copyright © 2016-2024. The Stdlib Authors.

Empty State

No vulnerabilities found.

10

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

10

Dangerous-Workflow

Determines if the project's GitHub Action workflows avoid dangerous patterns.

10

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

10

License

Determines if the project has defined a license.

9

Security-Policy

Determines if the project has published a security policy.

3

Pinned-Dependencies

Determines if the project has declared and pinned the dependencies of its build process.

Reason

dependency not pinned by hash detected -- score normalized to 3

Details

Warn: third-party GitHubAction not pinned by hash: .github/workflows/productionize.yml:84: update your workflow using https://app.stepsecurity.io/secureworkflow/stdlib-js/fs-resolve-parent-path/productionize.yml/main?enable=pin
Warn: third-party GitHubAction not pinned by hash: .github/workflows/productionize.yml:274: update your workflow using https://app.stepsecurity.io/secureworkflow/stdlib-js/fs-resolve-parent-path/productionize.yml/main?enable=pin
Warn: third-party GitHubAction not pinned by hash: .github/workflows/productionize.yml:448: update your workflow using https://app.stepsecurity.io/secureworkflow/stdlib-js/fs-resolve-parent-path/productionize.yml/main?enable=pin
Warn: third-party GitHubAction not pinned by hash: .github/workflows/productionize.yml:456: update your workflow using https://app.stepsecurity.io/secureworkflow/stdlib-js/fs-resolve-parent-path/productionize.yml/main?enable=pin
Warn: third-party GitHubAction not pinned by hash: .github/workflows/productionize.yml:621: update your workflow using https://app.stepsecurity.io/secureworkflow/stdlib-js/fs-resolve-parent-path/productionize.yml/main?enable=pin
Warn: npmCommand not pinned by hash: .github/workflows/benchmark.yml:58
Warn: npmCommand not pinned by hash: .github/workflows/benchmark.yml:58
Warn: npmCommand not pinned by hash: .github/workflows/benchmark.yml:58
Warn: npmCommand not pinned by hash: .github/workflows/examples.yml:58
Warn: npmCommand not pinned by hash: .github/workflows/examples.yml:58
Warn: npmCommand not pinned by hash: .github/workflows/examples.yml:58
Warn: npmCommand not pinned by hash: .github/workflows/productionize.yml:794
Warn: npmCommand not pinned by hash: .github/workflows/productionize.yml:794
Warn: npmCommand not pinned by hash: .github/workflows/productionize.yml:794
Warn: npmCommand not pinned by hash: .github/workflows/productionize.yml:156
Warn: npmCommand not pinned by hash: .github/workflows/productionize.yml:156
Warn: npmCommand not pinned by hash: .github/workflows/productionize.yml:156
Warn: npmCommand not pinned by hash: .github/workflows/productionize.yml:164
Warn: npmCommand not pinned by hash: .github/workflows/productionize.yml:268
Warn: npmCommand not pinned by hash: .github/workflows/productionize.yml:268
Warn: npmCommand not pinned by hash: .github/workflows/productionize.yml:268
Warn: npmCommand not pinned by hash: .github/workflows/productionize.yml:435
Warn: npmCommand not pinned by hash: .github/workflows/productionize.yml:435
Warn: npmCommand not pinned by hash: .github/workflows/productionize.yml:435
Warn: npmCommand not pinned by hash: .github/workflows/productionize.yml:615
Warn: npmCommand not pinned by hash: .github/workflows/productionize.yml:615
Warn: npmCommand not pinned by hash: .github/workflows/productionize.yml:615
Warn: npmCommand not pinned by hash: .github/workflows/test.yml:76
Warn: npmCommand not pinned by hash: .github/workflows/test.yml:76
Warn: npmCommand not pinned by hash: .github/workflows/test.yml:76
Warn: npmCommand not pinned by hash: .github/workflows/test.yml:83
Warn: npmCommand not pinned by hash: .github/workflows/test_bundles.yml:72
Warn: npmCommand not pinned by hash: .github/workflows/test_coverage.yml:67
Warn: npmCommand not pinned by hash: .github/workflows/test_coverage.yml:67
Warn: npmCommand not pinned by hash: .github/workflows/test_coverage.yml:67
Warn: npmCommand not pinned by hash: .github/workflows/test_coverage.yml:74
Warn: npmCommand not pinned by hash: .github/workflows/test_install.yml:75
Warn: npmCommand not pinned by hash: .github/workflows/test_install.yml:75
Warn: npmCommand not pinned by hash: .github/workflows/test_install.yml:75
Warn: npmCommand not pinned by hash: .github/workflows/test_published_package.yml:93
Info: 37 out of 37 GitHub-owned GitHubAction dependencies pinned
Info: 23 out of 28 third-party GitHubAction dependencies pinned
Info: 0 out of 35 npmCommand dependencies pinned

1

Maintained

Determines if the project is "actively maintained".

0

Code-Review

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

0

CII-Best-Practices

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

0

Fuzzing

Determines if the project uses fuzzing.

0

Token-Permissions

Determines if the project's workflows follow the principle of least privilege.

0

SAST

Determines if the project uses static code analysis.

0

Branch-Protection

Determines if the default and release branches are protected with GitHub's branch protection settings.

Score

4.3

/10

Last Scanned on 2025-04-28

The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.