</>PackageGraphPackageGraph

true-case-path

npmv2.2.1

Given 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 2604 days ago.

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

    No download data reported for this package yet.

  • FMaintenance: grade F, Failing.

    Last published 2604 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.

0
Direct dependencies

Runtime packages this one declares itself.

0
Total installed

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

21 KB
Install size

Unpacked size of this package plus its entire runtime tree.

—
Tree depth

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.

typescriptFull 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)

standard-version ^6.0.1

Used by

Popular packages that depend on true-case-path.

node-sassnpm

Wrapper around libsass

↓ 888.4K/wk◈ 0 dependents⚖ MITdeprecated

Relationship graph

Dependencies (left) and dependents (right) of true-case-path.

node-sasstrue-case-path
true-case-path dependencies dependents

Frequently installed together

lodashnpm

Lodash modular utilities.

↓ 147.8M/wk◈ 20 dependents⚖ MIT
eslintnpm

An AST-based pattern checker for JavaScript.

↓ 138.4M/wk◈ 279 dependents⚖ MITTS
meownpm

CLI app helper

↓ 36.7M/wk◈ 1 dependents⚖ MIT
make-fetch-happennpm

Opinionated, caching, retrying fetch client

↓ 22.8M/wk◈ 1 dependents⚖ ISC
gazenpm

A globbing fs.watch wrapper built from the best parts of other fine watch libs.

↓ 2M/wk◈ 1 dependents⚖ MIT
async-foreachnpm

An optionally-asynchronous forEach with an interesting interface.

↓ 643.2K/wk◈ 1 dependents
stdout-streamnpm

Non-blocking stdout stream

↓ 0/wk◈ 1 dependents⚖ MIT
cross-spawnnpm

Cross platform child_process#spawn and child_process#spawnSync

↓ 0/wk◈ 9 dependents⚖ MIT
globnpm

the most correct and second fastest glob implementation in JavaScript

↓ 0/wk◈ 35 dependents⚖ BlueOak-1.0.0TS
nannpm

Native Abstractions for Node.js: C++ header for Node 0.8 -> 26 compatibility

↓ 0/wk◈ 2 dependents⚖ MIT
sass-graphnpm

Parse sass files and extract a graph of imports

↓ 0/wk◈ 1 dependents⚖ MIT

Release history

No releases in the last two years, typically about 89 days apart.

Recent versions of true-case-path
VersionPublishedSizeLicense
2.2.1latest7 years ago21 KBApache-2.0
2.2.07 years ago20 KBApache-2.0
2.0.07 years ago16 KBApache-2.0
1.0.38 years ago15 KBApache-2.0
1.0.210 years ago—Apache version 2.0
1.0.110 years ago—Apache version 2.0
1.0.010 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 has 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 focused 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

  • 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

barsh

Frequently asked questions

Should I use true-case-path?

No — true-case-path should not be adopted for new projects. Last published 2604 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?

npm does not publish download counts. Within PackageGraph's crawl, 1 known packages depend on true-case-path.

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.