Per discussions in Discord, I'm pushing Glint v2's cli tools to behave as closely as possible to vue-tsc, which itself behaves much more closely to vanilla tsc. This means breaking changes for people using glint for type-checking as a CLI task, but here are a few reasons this is desirable / forgivable:
The closer we are to Vue's tooling in general, the more we can tap into their larger community, e.g. there might be a confusion about glint that can be well explained by a closed issue in vue-tsc, rather than having this obscured by glint's behind-the-scenes flag-switching before shelling out to vanilla tsc.
Perhaps glint v2 can remove the glint binary and introduce a new one called ember-tsc; this will be a much more loud and obvious breaking change such that anyone searching it can find the correct args to use rather than getting confused between existing and new documentation for glint v1 vs v2.
Per discussions in Discord, I'm pushing Glint v2's cli tools to behave as closely as possible to vue-tsc, which itself behaves much more closely to vanilla
tsc. This means breaking changes for people usingglintfor type-checking as a CLI task, but here are a few reasons this is desirable / forgivable:vue-tsc, rather than having this obscured by glint's behind-the-scenes flag-switching before shelling out to vanilla tsc.glintbinary and introduce a new one calledember-tsc; this will be a much more loud and obvious breaking change such that anyone searching it can find the correct args to use rather than getting confused between existing and new documentation for glint v1 vs v2.