Versions 1.6.2 and higher no longer replaces aliases
See original GitHub issueAfter upgrading tsc-alias
to 1.6.2
from 1.6.1
, the tool seemingly no longer works.
I have a single entry in paths
in my tsconfig.json
:
{
"paths": {
"~*": ["./src/*"]
}
}
I build my types with the following command: tsc --emitDeclarationOnly --outDir dist && tsc-alias
Previously it worked without issue. After the upgrade, tilde paths in my .d.ts
files are no longer replaced with relative paths.
I’m happy to provide more info, just let me know what’s needed!
Versions Node - 17.6.0 NPM - 8.5.2 tsc-alias - 1.6.2
Issue Analytics
- State:
- Created 2 years ago
- Comments:13 (8 by maintainers)
Top Results From Across the Web
MacOS - Remove/replace alias files in Electron Framework ...
APP file (built with electron-builder) on Steam, all alias contained in the /Contents/Frameworks folder will be replaced by executable files (no ...
Read more >Migration Guide: SQL, Datasets and DataFrame - Apache Spark
Dataset/DataFrame APIs. In Spark 3.0, the Dataset and DataFrame API unionAll is no longer deprecated. It is an alias for union .
Read more >Aliases API | Elasticsearch Guide [8.5] | Elastic
Aliases APIedit. Performs one or more alias actions in a single atomic operation.
Read more >Compose file versions and upgrading - Docker Documentation
Looking for more detail on Docker and Compose compatibility? ... If no minor version is given, 0 is used by default and not...
Read more >AngularJS: Developer Guide: Migrating from Previous Versions
AngularJS 1.8 is a breaking change release from 1.7 to mitigate a security issue. JqLite no longer turns XHTML-like strings like <div /><span...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Found the problem, pushing fix soon.
It has loaded the config correctly.
~
is loaded into the aliastrie. The problem is probably something with the globPattern and the outPath being relative (../../../dist
)