Gathering detailed insights and metrics for tscpaths
Gathering detailed insights and metrics for tscpaths
Gathering detailed insights and metrics for tscpaths
Gathering detailed insights and metrics for tscpaths
serverless-tscpaths
Replace absolute paths to relative paths after typescript compilation
@herbcaudill/tscpaths
Replace absolute paths to relative paths after typescript compilation
@devjacob/tscpaths
A simple logger package
@modii/tscpaths
Replace absolute paths to relative paths after typescript compilation
Replace absolute paths to relative paths after typescript compilation
npm install tscpaths
Typescript
Module System
TypeScript (91.42%)
JavaScript (8.58%)
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
MIT License
268 Stars
24 Commits
49 Forks
6 Watchers
13 Branches
2 Contributors
Updated on May 23, 2025
Latest Version
0.0.9
Package Id
tscpaths@0.0.9
Size
8.78 kB
Published on
May 09, 2019
Cumulative downloads
Total Downloads
Last Day
0%
NaN
Compared to previous day
Last Week
0%
NaN
Compared to previous week
Last Month
0%
NaN
Compared to previous month
Last Year
0%
NaN
Compared to previous year
Replace absolute paths to relative paths after typescript compilation (tsc) during compile-time.
+ Compile time (no runtime dependencies)
First, install tscpaths as devDependency using npm or yarn.
1npm install --save-dev tscpaths 2# or 3yarn add -D tscpaths
1"scripts": { 2 "build": "tsc --project tsconfig.json && tscpaths -p tsconfig.json -s ./src -o ./out", 3}
flag | description |
---|---|
-p --project | project configuration file (tsconfig.json) |
-s --src | source code root directory |
-o --out | output directory of transpiled code (tsc --outDir) |
You need to provide -s (--src) and -o (--out), because it's hard to predict source and output paths based on tsconfig.json.
I've tried a little and failed. :(
tsc
does some magic to determine source and output paths and I haven't dived too deep to mimic it.
For now, it's simpler to provide the paths manually.
If you know how, Pull Requests are welcome!
This is not a mature project yet.
It works for my setup so far.
It may not work correctly if your setup is too complicated, so please do some testing before pushing it to production!!!
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
license file detected
Details
Reason
Found 2/22 approved changesets -- score normalized to 0
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
project is not fuzzed
Details
Reason
security policy file not detected
Details
Reason
branch protection not enabled on development/release branches
Details
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Reason
54 existing vulnerabilities detected
Details
Score
Last Scanned on 2025-07-07
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More