Gathering detailed insights and metrics for parcel-resolver-tspaths-lenient
Gathering detailed insights and metrics for parcel-resolver-tspaths-lenient
Gathering detailed insights and metrics for parcel-resolver-tspaths-lenient
Gathering detailed insights and metrics for parcel-resolver-tspaths-lenient
Parcel v2 plugin for using Typescript aliases
npm install parcel-resolver-tspaths-lenient
Typescript
Module System
Min. Node Version
Node Version
NPM Version
18
Supply Chain
25
Quality
74.8
Maintenance
100
Vulnerability
91.3
License
TypeScript (80.88%)
JavaScript (15.75%)
HTML (2.67%)
Shell (0.7%)
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
MIT License
5 Stars
66 Commits
3 Forks
1 Watchers
2 Branches
2 Contributors
Updated on Dec 22, 2022
Latest Version
0.0.93
Package Id
parcel-resolver-tspaths-lenient@0.0.93
Unpacked Size
8.18 kB
Size
3.71 kB
File Count
4
NPM Version
7.15.1
Node Version
16.3.0
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
1
Parcel does not make use of tsconfig.json
to resolve path aliases, and instead uses package.json
(reference). This Parcel v2 plugin enables typescript path alias resolution as you would normally expect with webpack or otherwise. As a bonus, intellisense will continue to provide suggestions from your tsconfig.
This plugin is experimental until Parcel V2 is released. Use in production with heavy caution. Updated for beta 3.1 release.
yarn add -D parcel-resolver-tspaths
or
npm install --save-dev parcel-resolver-tspaths
Ensure all parcel packages are set to minimum version ^2.0.0-beta.2
and that Parcel is configured for Typescript.
In your .parcelrc, be sure to properly extend the default config and add the plugin to your resolvers like so:
1"extends": "@parcel/config-default", 2"resolvers": ["...", "parcel-resolver-tspaths"], 3"transformers": { 4 "*.{ts,tsx}": ["@parcel/transformer-typescript-tsc"] 5}, 6"validators": { 7 "*.{ts,tsx}": ["@parcel/validator-typescript"] 8},
And that's it. Note: the order of resolvers is sequential, and I highly recommend keeping this resolver after the base resolvers.
Hot reloading is broken in files resolved through aliases, because Parcel's HMR implementation does not account for resolvers. You can follow this issue here.
This plugin does not support Typescript aliases while importing non-code assets, but this is being considered for future development.
For example:
1import logo from 'url:@myassets/image/logo.svg';
Clone this repo anywhere, then run yarn && yarn link
in the project root.
In any parcel app, run yarn && yarn link parcel-resolver-tspaths
. Then follow normal build procedures. Real tests coming soon.
If you run into issues viewing debug output, you can see all raw output by running yarn test |& cat
(Mac/Linux users only).
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
license file detected
Details
Reason
Found 1/29 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
security policy file not detected
Details
Reason
branch protection not enabled on development/release branches
Details
Reason
project is not fuzzed
Details
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Reason
29 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