Upgrading from 1.6.4 to 1.6.5 breaks
See original GitHub issueHi, thank you so much for this amazing lib 😃
Everything works fine when using 1.6.4 I get tsc-alias info: 94 files were affected!
But when I switch to 1.6.5 I get tsc-alias info: 0 files were affected!
(I don’t get any errors)
It seems like this commit broke my config https://github.com/justkey007/tsc-alias/commit/0abf049bc8021518bd5e1e6afc63dcc077a0f885
My tsconfig is
{
"extends": "../../tsconfig.packages.json",
"compilerOptions": {
"rootDir": "./src",
"outDir": "./dist",
"baseUrl": "../..",
"paths": {
"@utils/*": [
"packages/server/src/utils/*"
],
"@generated/*": [
"packages/server/src/generated/*"
],
"@resolvers/*": [
"packages/server/src/resolvers/*"
],
"@gqlTypes/*": [
"packages/server/src/types/*"
],
"@context": [
"packages/server/src/context.ts"
],
"@c4f-platform/*": [
"packages/*/"
]
},
"allowJs": false,
"target": "ES6",
"moduleResolution": "node",
"allowSyntheticDefaultImports": true,
"module": "commonjs",
"sourceMap": true,
"listEmittedFiles": false,
"alwaysStrict": true,
"esModuleInterop": true,
"resolveJsonModule": true,
"skipLibCheck": true,
"strictNullChecks": true,
"lib": [
"esnext"
],
"composite": true,
"declaration": true,
"declarationMap": true
},
"include": [
"lib/**/*",
"bin/*",
"tests/*.test.*",
"src/**/*",
"src/**/*.json"
],
"exclude": [
"node_modules"
],
"references": []
}
I don’t understand why the changes broke the compilation based on my config. Let me know if you need more info on my config 😃
Have a nice day
Issue Analytics
- State:
- Created a year ago
- Reactions:2
- Comments:12 (4 by maintainers)
Top Results From Across the Web
AngularJS: Developer Guide: Migrating from Previous Versions
Generally updating to 1.8.0 from 1.7.x should be a straightforward process and is highly recommended. AngularJS 1.8 is a breaking change release from...
Read more >Upgrading to Vault 1.6.0 - Guides - HashiCorp Developer
This page contains the list of deprecations and important or breaking changes for Vault 1.6.0 compared to 1.5. Please read it carefully.
Read more >Upgrade Guidance - 1.6.3 to 1.9.2 - Temporal
Meaning, do I need to upgrade via Helm from 1.6.3 to 1.6.4 to 1.6.5 to 1.6.6, all the way up to 1.9.2, in...
Read more >How to Downgrade Skyrim SE to Fix SKSE64 & Mods (2021)
Skyrim Anniversary Edition Update released today and has broken SKSE64 and mods that require it. In this video, I show you how to...
Read more >NEW Patch BREAKS Mods, SKSE64 Issues, VITAL Fixes!
Skyrim's NEW 7GB has once again broken mods... let's talk about that! ... Skyrim Update 1.6.629 0:41 - SKSE64 & Other Mods Broken...
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 FreeTop 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
Top GitHub Comments
Yes indeed, here you go: not-working.txt working.txt
Thank you @raouldeheer for the quick answer 😃 Here’s a sample of each console output.
Working version
Non-working