Fix glint
cli build tests, parity with vue-tsc
#740
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 usingglint
for 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.glint
binary 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.