Hello,
I following the discussion in #5381.
In the discussion, it was mentioned that TypeScript 7.1 support is still on the roadmap, and that the upstream Content Mappers work may eventually allow tsc to check .vue files directly through a Vue content mapper. It was also mentioned that Vue Language Tools may migrate to that architecture where possible and deprecate overlapping solutions such as vue-tsc.
I noticed that microsoft/typescript-go#4712 has now been merged. Does this change or clarify the expected future direction of vue-tsc?
If possible, I would appreciate any high-level information about:
- Whether a Vue Content Mapper is currently planned or already being explored;
I understand that the implementation details and timeline may still depend on the TypeScript 7.1 release, so I am not expecting a firm schedule. I would simply like to better understand the long-term direction of the project as a vue-tsc user.
Thank you for your time and for maintaining Vue Language Tools.
Hello,
I following the discussion in #5381.
In the discussion, it was mentioned that TypeScript 7.1 support is still on the roadmap, and that the upstream Content Mappers work may eventually allow
tscto check.vuefiles directly through a Vue content mapper. It was also mentioned that Vue Language Tools may migrate to that architecture where possible and deprecate overlapping solutions such asvue-tsc.I noticed that microsoft/typescript-go#4712 has now been merged. Does this change or clarify the expected future direction of
vue-tsc?If possible, I would appreciate any high-level information about:
I understand that the implementation details and timeline may still depend on the TypeScript 7.1 release, so I am not expecting a firm schedule. I would simply like to better understand the long-term direction of the project as a
vue-tscuser.Thank you for your time and for maintaining Vue Language Tools.