NullVoxPopuli
NullVoxPopuli
Some of this will be possible with the Error nodes available in this branch of the parser: https://github.com/glimmerjs/glimmer-vm/pull/1690
not quite, but I have: ```hbs {{format-message "boop"}} ```
> there is an error where @ember/optional-features is required and you also need a config (even though it doesn't make sense in a v2 addon) how did this come up?...
+1 to the browser field. As is, loading content-tag in the browser is currently hinky requires patches/hacks). https://github.com/embroider-build/content-tag/blob/main/package.json#L13
I agree! We need to progress the RFC for scoped styles tho
This may be what you want https://github.com/auditboard/ember-scoped-css
it doesn't seem like it, based on https://github.com/lupomontero/psl/issues/315 if the maintainer wants help or doesn't have the bandwidth, I'm more than happy to lend a hand!
potentially blocked on https://github.com/vitejs/vite/pull/17837 (unless I use a different dependency for testing -- which I probably should, as the problems I'm having here are vite-related, not embroider related)
Can you try upgrading babel-plugin-ember-template-compilation?
tl;dr: content-tag needs to be at least 3.1.2, else you hit the missing `export default` bug -------------- content-tag emits the `export default` for plain templates, but not ones wrapped in...