-
Notifications
You must be signed in to change notification settings - Fork 142
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
Embroider safe tests hang for all addons #827
Comments
Maybe the same issue? |
Ah, yes, perhaps. Will wait for a fix to land and see. |
Your tests don't seem to be failing due to ^ any longer, rather some other issue that at first glance seems like it may not be an issue in embroider rather embroider appears to be providing actionable resolution steps:
I am going to close this issue, but feel free to reopen if I have closed in error. |
@stefanpenner my tests still fail with |
Here is the error still occurring https://github.com/shipshapecode/ember-shepherd/pull/779/checks?check_run_id=2759690063#step:5:295 Should it be fixed in Ember 3.27.3 or just in canary or how do I test it out? |
@rwwagner90 should have been fixed with ember-source@3.27.3, and tarballs from release + beta + canary channels |
@rwwagner90 - The last link you shared was not anything to do with
Which is due to a double transpilation of See https://github.com/shipshapecode/ember-meta/pull/28/files#r646644689 for details. |
@rwjblue Thanks for the help with ember-meta! I am still experiencing |
Ya, I am still debugging that one. It does look like it is using ember-source@3.27.3 (on initial review), so trying to see if it is actually using an old Ember or if somethign else is wrong... |
FYI, I still get
With:
And this code: const { maybeEmbroider } = require('@embroider/test-setup');
return maybeEmbroider(app, {
skipBabel: [{ package: 'qunit' }],
}); |
@mydea - Have you debugged? What is importing qunit when the error is thrown? |
I get this error when installing latest embroider/core & compat & webpack & webpack, run
Not sure if that helps? |
@mydea - Ya, I'm mostly asking what code is actually trying to get |
As far as I can tell it is this line in the (default?) import * as QUnit from 'qunit'; |
Huh, that worked! I removed ember-auto-import from the dev dependencies as I was not aware it was being used by something in the default blueprint. And since the regular tests worked, I thought that was all good. Weird that this would only fail in embroider then, but in in a regular build 🤔 but thanks a lot for the help! |
also related to ember-auto-import - embroider-build/ember-auto-import#404 (comment) |
in short, updating addon blueprint with ember-auto-import v2 may cause a lot of issues for addon authors. |
OK, sorry folks. I'm going to close this issue for now. I think there are still valid / active problems that folks are working through, but this issue thread has become a dumping ground of a bunch of different and unrelated (other than that they cause issues) things. For anyone that is still having issues, please open a new issue dedicated to the specific problem that you are facing. Make sure to include reproduction steps, and a high level summary of your problem. Again, I'm sorry, but I can't triage all the various problems in the same issue 😞. |
@rwjblue I seem to still be getting Ember is not defined here https://github.com/shipshapecode/ember-math-helpers/runs/2851158494?check_suite_focus=true |
@rwwagner90 that is most likely due to #862 |
@ef4 I don't think I am using |
@rwwagner90 one of your addons probably is. It looks like this project is using ember-cli-addon-docs, which pulls in quite a lot of stuff. The CI failure you linked to says
|
I am not sure if this is due to something like ember-cli-addon-docs or what is causing all my addons to hang when I try to add the embroider ember-try scenarios, but I always get
Global error: Uncaught ReferenceError: Ember is not defined
.Here are a couple builds:
RobbieTheWagner/ember-math-helpers#509
RobbieTheWagner/ember-shepherd#779
@ef4 any ideas here?
The text was updated successfully, but these errors were encountered: