@ember/test-helpers 2.8.0 breaks embroider-optimized scenario
See original GitHub issue2.8.0 causes following issue:
ERROR in …/node_modules/@ember/test-helpers/setup-rendering-context.js Module build failed (from …/…/…/…/home/runner/work/tracked-built-ins/tracked-built-ins/node_modules/thread-loader/dist/cjs.js): Thread Loader (Worker 0) $TMPDIR/embroider/f71d26/node_modules/@ember/test-helpers/setup-rendering-context.js: Unsafe dynamic component: this.ProvidedComponent in $TMPDIR/embroider/f71d26/node_modules/@ember/test-helpers/setup-rendering-context.js
Can be seen in https://github.com/tracked-tools/tracked-built-ins/runs/6480181579?check_suite_focus=true
I believe Embroider complaints about this line:
Due to complexity of the setup, this does not seem straightforward fix to me.
Seem like one of the options is to configure packageRules
, but seem not possible from the addon.
cc @chriskrycho
Issue Analytics
- State:
- Created a year ago
- Reactions:3
- Comments:6 (6 by maintainers)
Top GitHub Comments
That fix landed and was released in 2.8.1
FWIW, I noticed that 2.8.0 already added
@embroider/macros@1
(which had the Node version issue that I mentioned above), so I just submitted https://github.com/emberjs/ember-test-helpers/pull/1221 to just use@embroider/util
. It doesn’t make things worse and so far no one has raised an issue RE: Node 10 support being dropped.https://github.com/emberjs/ember-test-helpers/pull/1221 should unblock folks leveraging Embroider optimized builds, if we get folks raising issues RE: Node 10 we can fix by inlining the
ensureSafeComponent
code. I just don’t want to proactively do all that work (just to throw it away) if no one actually cares. 😩