NullVoxPopuli
NullVoxPopuli
> This PR literally includes the 3.1.2 version bump and it didn't fix the issue 😅 . apologies. I got too excited :facepalm:
Gonna see if content-tag-utils handles this
So, it seems that because content-tag-utils operates on the tag range, there is no issue: https://github.com/NullVoxPopuli/content-tag-utils/pull/13/files#diff-04471e09412bbfa48026ce0732d9ce4efd6dea7514e80516d583cbe2a11d0233R44
> but here we are using the .parse method to then do something with the result Where does this happen?
> So we need to handle the implicit export default here as well, before handig it off to babel-remove-types. I don't think this is true -- and `parse` can't provide...
Maybe content-tag-utils should have an unprocess method that converts plain js/ts back to gjs/gts. That way strip-babel-types can operate on plain js, and we don't need parse
> unprocess here it is, a way to go from js/ts back to gjs/gts https://github.com/NullVoxPopuli/content-tag-utils/pull/15
So now the code would be: ```js let ts = p.process(gts); let js = stripTypes(ts); let gjs = unprocess(js); ```
Alt: https://github.com/ember-cli/ember-cli/pull/10682
the primary backstory is that we haven't had control over patch vs major when releasing --- it sems the tsconfig/bases repo doesn't do semver in any way. By moving to...