You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Then run ember b and you will encounter the following error:
Build Error (WaitForTrees)
ENOENT: no such file or directory, open '/private/var/folders/61/n399scw50nq264twrz32ccgr000vkn/T/embroider/b8ef3e/node_modules/@ember/test-helpers/node_modules/@ember/test-waiters/package.json'
Stack Trace and Error Report: /var/folders/61/n399scw50nq264twrz32ccgr000vkn/T/error.dump.5c2dc6c6019426ac6515ab214b869a0d.log
The text was updated successfully, but these errors were encountered:
The OneShot transform consumes a broccoli tree a single time, detaching us permanently from future updates to that tree, which avoids needing to revalidate all the third-party v1-to-v2 addon conversion during rebuilds.
Since OneShot fully consumes a broccoli tree in a separate broccoli pipeline, it's not safe to consume that same tree again in a different pipeline.
But an addon can manipulate cacheKeyForTree such that two distinct copies of an addon emit the same broccoli tree instance as their v2Tree, which we send into OneShot. This fails in a very byzantine way.
It's the source of the problems people have been having with test-waiters (#1056) because that addon aggressively tries to deduplicate itself.
The fix is to not rerun OneShot if we encounter an identical tree a second time.
There seems to be an issue when
yarn why @ember/test-waiters
has multiple versions. highlander code might be a place to investigate.Reproductions steps:
ember new foobar --yarn
yarn add --dev @embroider/core @embroider/compat @embroider/webpack webpack
ember install @ember/test-waiters@2.4.5
Finally add to
ember-cli-build.js
:Result
Then run
ember b
and you will encounter the following error:The text was updated successfully, but these errors were encountered: