NullVoxPopuli

An idea I had to _help_ with the issue (but not solve it), only helps out auto-import users, where we change the behavior of `autoImport.watchDependencies` to look at a package's...

Made a stackblitz of the above repo if folks don't want to clone: https://stackblitz.com/edit/github-yl7xy1?file=packages%2Faccordion%2Fsrc%2Fcomponents%2Faccordion.gts&file=packages%2Faccordion%2Fdist%2Fcomponents%2Faccordion.js 

resolved by ensuring that `content-tag` in your lockfile is up to date (at least 1.1.2). This'll be fixed shortly with a new minimum `@embroider/addon-dev` version.

yeah, sounds like a bug in their babel plugin -- they have enough knowledge of what they need to do to remove that themselves (babel can't do it, because it's...

> Do you have examples for these type-tests in real addons? ember-resources, ember-modifier, @ember/test-helpers, ember-async-data, ember-qunit, and ember-source (off the top of my head) > And do they qualify as...

The typescript test is using `yarn@v1` which manages dependencies incorrectly, and gives us this error during build: ``` [!] (plugin Typescript) TS2688: Cannot find type definition file for 'ember__test-helpers'. The...

It's likely this problem will go away when the `--typescript` app blueprint uses the built in types. @chriskrycho -- I remember reading you ran in to some issues promoting the...

Moving to draft, as I have some things to explore, and later extract from this PR.

the approach that I've seen used is _bad_, in that we have a one-off build, using that babel plugin you listed, instrumenting all addon code -- which gets you coverage......

is this still an issue? and still an issue with yarn@3+? (ie, can we casually drop / stop-caring about yarn@v1)