chdir-promise 0.3.0
Change working dir and return a promise, a stack of folders is maintained to jump back
chdir-promise@0.3.0 was published on 2016-12-04. Its manifest declares 6 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. No Node.js engine requirement is declared in this manifest.
All chdir-promise versions · Permanent reference to 0.3.0 · Latest release
Package specifications
| Version | 0.3.0 |
|---|---|
| License declaration | MIT |
| Published | 2016-12-04T23:18:00.200Z |
| Node.js requirement | Not declared |
| Type declarations | Not declared |
| Runtime dependency count | 6 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | Not supplied |
| Published file count | Not supplied |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | index.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 7 |
| Repository stars | 2 |
| Repository forks | 0 |
Install chdir-promise 0.3.0
npm install chdir-promise@0.3.0 pnpm add chdir-promise@0.3.0 yarn add chdir-promise@0.3.0
Runtime dependencies
- check-more-types 1.1.1
- check-types 1.4.0
- debug ^2.3.3
- lazy-ass 0.5.3
- q 1.1.2
- spots 0.4.0
Peer requirements
- None declared
Optional dependencies
- None declared
Resolved dependency graph
This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.
- check-more-types@1.1.1 — direct
- check-types@1.4.0 — direct
- debug@2.6.9 — direct
- lazy-ass@0.5.3 — direct
- ms@2.0.0 — indirect
- q@1.1.2 — direct
- spots@0.4.0 — direct
How to interpret the specifications
Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.
Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.
OpenSSF repository checks
Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.
| Code-Review | 0/10 — Found 0/27 approved changesets -- score normalized to 0 |
|---|---|
| Maintained | 0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
| SAST | 0/10 — no SAST tool detected |
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Fuzzing | 0/10 — project is not fuzzed |
| Security-Policy | 0/10 — security policy file not detected |
| License | 0/10 — license file not detected |
| Branch-Protection | 0/10 — branch protection not enabled on development/release branches |
Evidence and freshness
- https://registry.npmjs.org/chdir-promise/0.3.0 — retrieved 2026-10-29T23:03:43.077Z
- https://api.deps.dev/v3/projects/github.com%2Fbahmutov%2Fchdir-promise — retrieved 2026-10-29T19:41:29.724Z
- https://api.deps.dev/v3/systems/npm/packages/chdir-promise/versions/0.3.0 — retrieved 2026-10-29T23:03:43.600Z
- https://api.deps.dev/v3/systems/npm/packages/chdir-promise/versions/0.3.0:dependencies — retrieved 2026-10-29T23:03:43.620Z