Astro Info
Astro v6.1.7
Node v25.9.0
System macOS (arm64)
Package Manager pnpm
Output static
Adapter none
Integrations none
If this issue only occurs in one browser, which browser is a problem?
No response
Describe the Bug
I noticed this warning when I installed Astro via pnpm install or pnpm update, I then investigated it and found that it was due to tsconfck being deprecated soon.
.
└─┬ astro 6.1.7
└─┬ tsconfck 3.1.6
└── ✕ unmet peer typescript@^5.0.0: found 6.0.3
. | +7 -173 +-----------------
Progress: resolved 1431, reused 159, downloaded 2, added 7, done
Done in 12.6s using pnpm v10.33.0
The original author is discontinuing the project dominikg/tsconfck#240
The author recommended switching to https://github.com/privatenumber/get-tsconfig, get-tsconfig might have some differences in behavior so it is worth investigating further, as far as I can tell the differences between both pacakges is minimal.
There is also a chance we can utilize rolldown built-in utilities for this vitejs/vite#21577
Doing my own research I think get-tsconfig is the best balance here, while avoiding potential future edge cases and/or behaviour drift. If we're fine with behaviour drift then the rolldown utility would be the most convinent solution here.
You can check out my research here: https://chatgpt.com/share/69e2fed1-7c98-83ea-92c0-0a7870287001
What's the expected result?
tbh using an alternative that doesn't output warnings.
Link to Minimal Reproducible Example
https://stackblitz.com/~/github.com/okikio/astro-tsconfck-outdated-repro
Participation
Astro Info
If this issue only occurs in one browser, which browser is a problem?
No response
Describe the Bug
I noticed this warning when I installed Astro via
pnpm installorpnpm update, I then investigated it and found that it was due totsconfckbeing deprecated soon.The original author is discontinuing the project dominikg/tsconfck#240
The author recommended switching to https://github.com/privatenumber/get-tsconfig,
get-tsconfigmight have some differences in behavior so it is worth investigating further, as far as I can tell the differences between both pacakges is minimal.There is also a chance we can utilize rolldown built-in utilities for this vitejs/vite#21577
Doing my own research I think
get-tsconfigis the best balance here, while avoiding potential future edge cases and/or behaviour drift. If we're fine with behaviour drift then the rolldown utility would be the most convinent solution here.You can check out my research here: https://chatgpt.com/share/69e2fed1-7c98-83ea-92c0-0a7870287001
What's the expected result?
tbh using an alternative that doesn't output warnings.
Link to Minimal Reproducible Example
https://stackblitz.com/~/github.com/okikio/astro-tsconfck-outdated-repro
Participation