typescript-transform-paths 3.4.11

Transforms module resolution paths using TypeScript path mapping and/or custom paths

typescript-transform-paths@3.4.11 was published on 2024-08-16. Its manifest declares 1 runtime dependency and 1 peer requirement. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

All typescript-transform-paths versions · Permanent reference to 3.4.11 · Latest release

Package specifications

Version3.4.11
License declarationMIT
Published2024-08-16T00:49:02.453Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count1
Peer requirement count1
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size137.13 KiB
Published file count66
Package typeNot declared
ES module entryNot declared
Default entrydist/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies4
Repository stars496
Repository forks32

Install typescript-transform-paths 3.4.11

npm install typescript-transform-paths@3.4.11
pnpm add typescript-transform-paths@3.4.11
yarn add typescript-transform-paths@3.4.11

Runtime dependencies

Peer requirements

Optional dependencies

  • None declared

Resolved dependency graph

This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.

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-Review1/10 — Found 2/18 approved changesets -- score normalized to 1
Maintained10/10 — 12 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Binary-Artifacts10/10 — no binaries found in the repo
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
Pinned-Dependencies0/10 — dependency not pinned by hash detected -- score normalized to 0
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Security-Policy0/10 — security policy file not detected
Fuzzing0/10 — project is not fuzzed
License10/10 — license file detected
Branch-Protection0/10 — branch protection not enabled on development/release branches
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness