-
-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dependencies can leak between scenarios #579
Comments
Also described in #451 |
Ya, we need to land the fixes in #451 |
Thanks. If that definitely covers this, we can close this. |
We should leave it open until a PR lands.
…On Wed, Oct 21, 2020 at 1:31 PM Edward Faulkner ***@***.***> wrote:
Thanks. If that definitely covers this, we can close this.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#579 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AADMOOVEFWUCZQVHKASRMXDSL4LGLANCNFSM4S2BYYUQ>
.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If you have a scenario with no
npm
section at all, it seems to work, but it silently uses the NPM deps from the previous scenario.Reproduction:
ember try:each
should show a failure.(I created this test app initially because I was trying to confirm that ember-try can really swap the ember-cli version in use -- it can, thanks!)
This seems related to #81 but not identical to it. That older issue seems to imply that this case would be an explicit error, whereas now it seems to be a tolerated-but-faulty.
The text was updated successfully, but these errors were encountered: