NullVoxPopuli
NullVoxPopuli
Figured out a work-around. There is a bug with older `@glimmer` (back then it distributed as cjs) that _indeed_ did not include `@glimmer/env`. I've resolved this with pnpm's packageExtensions config...
Why not?: ```hbs ``` semantically, (like, for other attributes), setting multiple times overrides other values. For example, this JSBin: https://jsbin.com/leyizogeli/edit?html,output
Excellent! easy checkbox!
Does skipLibCheck help? Otherwise, glimmer has more bugs we need to fix (all relative imports should always use extensions when using node16, so it shouldn't be too bad of a...
@patricklx would there be any noticeable editor behavior changes with this PR? (or is it "just the same, but using the new parser capabilities"?)
@patricklx new versions published, can you try the .1 release?
ah yeah, we're probably blocked on ember-source _needing_ to actually ship as a `type=module` package.
does changing all of `@types/ember*` to type=module work locally? :thinking:
Ahh, yeah, probably because all the private relative imports need extensions at that point. Hmm
I've added skipLibCheck back. It doesn't seem we can build without it.