true-case-path
npmv2.2.1Given a possibly case-variant version of an existing filesystem path, returns the case-exact, normalized version as stored in the filesystem.
Not recommended for new projects
No — true-case-path should not be adopted for new projects. Last published 2555 days ago.
- AAdoption: grade A, Excellent.
2M downloads per week and 1 known dependents.
- FMaintenance: grade F, Failing.
Last published 2555 days ago.
- AWeight: grade A, Excellent.
Zero runtime dependencies, about 21 KB installed.
- BSupply chain: grade B, Good.
This package has a single maintainer (bus factor of 1).
- ALicense: grade A, Excellent.
Apache-2.0 — 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 true-case-path to a project.
Runtime packages this one declares itself.
Distinct packages in the full runtime tree, deduplicated the way a package manager would.
Unpacked size of this package plus its entire runtime tree.
Longest resolved dependency chain below this package.
Compatibility
- Node.js
- No constraint declared
- Module format
- CommonJS only
- TypeScript
- No bundled types
- Install scripts
- None
Quick start
A usage example from the true-case-path README.
const { trueCasePath, trueCasePathSync } = require('true-case-path')
trueCasePath(<fileSystemPath>)
.then((caseCorrectPath) => {
// ...
})
const caseCorrectPath = trueCasePathSync(<fileSystemPath>)Dependencies
Declared by true-case-path v2.2.1. Runtime dependencies are installed with the package; dev dependencies are not.
Dev (1)
Used by
Popular packages that depend on true-case-path.
Relationship graph
Dependencies (left) and dependents (right) of true-case-path.
Frequently installed together
An AST-based pattern checker for JavaScript.
Opinionated, caching, retrying fetch client
Native Abstractions for Node.js: C++ header for Node 0.8 -> 26 compatibility
Parse sass files and extract a graph of imports
An optionally-asynchronous forEach with an interesting interface.
Lodash modular utilities.
Non-blocking stdout stream
Cross platform child_process#spawn and child_process#spawnSync
the most correct and second fastest glob implementation in JavaScript
A globbing fs.watch wrapper built from the best parts of other fine watch libs.
CLI app helper
Release history
No releases in the last two years, typically about 89 days apart.
| Version | Published | Size | License |
|---|---|---|---|
| 2.2.1latest | 7 years ago | 21 KB | Apache-2.0 |
| 2.2.0 | 7 years ago | 20 KB | Apache-2.0 |
| 2.0.0 | 7 years ago | 16 KB | Apache-2.0 |
| 1.0.3 | 8 years ago | 15 KB | Apache-2.0 |
| 1.0.2 | 10 years ago | — | Apache version 2.0 |
| 1.0.1 | 10 years ago | — | Apache version 2.0 |
| 1.0.0 | 10 years ago | — | Apache version 2.0 |
Overview
true-case-path is an npm package that given a possibly case-variant version of an existing filesystem path, returns the case-exact, normalized version as stored in the filesystem. It is very popular, with about 2M downloads per week and 1 known dependents in the graph. The latest version is 2.2.1, released under the Apache-2.0 license.
Who should use it
Teams working in the npm ecosystem who need given a possibly case-variant version of an existing filesystem path, returns the case-exact, normalized version as stored in the filesystem and value a battle-tested, widely-adopted solution.
When not to use it
Consider an alternative if you need to have first-class TypeScript types out of the box, or if a more actively-maintained option better fits your npm stack.
Pros
- Large, well-established user base (2M weekly downloads).
- Clear open-source license (Apache-2.0).
- Lean dependency tree (1 direct dependencies).
Cons
- No bundled TypeScript types (may require a separate @types package).
Auto-generated from collected registry metadata. No external claims are inferred.
Maintainers
Frequently asked questions
Should I use true-case-path?
No — true-case-path should not be adopted for new projects. Last published 2555 days ago.
How do I install true-case-path?
Run `npm install true-case-path` to add true-case-path to your npm project.
What license is true-case-path released under?
true-case-path is distributed under the Apache-2.0 license.
How popular is true-case-path?
true-case-path has approximately 2,013,892 downloads per week and 1 known dependent packages.
Is true-case-path still maintained?
The most recent release of true-case-path (v2.2.1) was published 7 years ago.
Does true-case-path run install scripts?
No. true-case-path does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.