tsconfig-paths-webpack-plugin 3.4.0

Load modules according to tsconfig paths in webpack.

tsconfig-paths-webpack-plugin@3.4.0 was published on 2021-03-12. Its manifest declares 3 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

All tsconfig-paths-webpack-plugin versions · Permanent reference to 3.4.0 · Latest release

Package specifications

Version3.4.0
License declarationMIT
Published2021-03-12T22:41:38.134Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count3
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size43.48 KiB
Published file count24
Package typeNot declared
ES module entryNot declared
Default entrylib/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies14
Repository stars621
Repository forks50

Install tsconfig-paths-webpack-plugin 3.4.0

npm install tsconfig-paths-webpack-plugin@3.4.0
pnpm add tsconfig-paths-webpack-plugin@3.4.0
yarn add tsconfig-paths-webpack-plugin@3.4.0

Runtime dependencies

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.

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.

Maintained0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
Code-Review3/10 — Found 10/30 approved changesets -- score normalized to 3
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Binary-Artifacts10/10 — no binaries found in the repo
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
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness