"ReferenceError: axe is not defined" when upgrading to 0.2.0
abought opened this issue · comments
Summary
When upgrading an app from ember-a11y-testing 0.1.6 to 0.2.0, I get a JS console error ReferenceError: axe is not defined
when running ember server
.
When I run unit tests (ember test --server
), I do not get these errors and unit tests behave as expected. App uses Ember 2.8 (the newest LTS).
Steps to reproduce / test case
See pull request demonstrating changes:
CenterForOpenScience/demo-ember-osf#6
Attempted fixes
Also attempted to make package.json and bower.json changes to bring project in line with changes made here.
#58
Got the same result both before and after 08238ff
.
Reran blueprint and tried with a fresh install of node_modules and bower_components.
Tried in Chrome 56 and FF 51, Mac OS.
Let me know if you'd like me to try additional things to help track down the cause; I'm happy to do more spadework as suggested. Thanks for the work on the new release!
I believe this is the same issue as #61, can you double check and confirm?
I believe this is the same issue as #61, can you double check and confirm?
This is issue 61, so, um...
Do you mean #60 ? A bit surprised if that's the case; this chart claims the newest FF and Chrome versions support Promises natively. Then again, this could be one of those days where I learn something new.
EDIT: Added more error message info. The error seems to be about axe, not promises.
Uncaught ReferenceError: axe is not defined
at Class.audit (axe-component.js:138)
at invoke (ember.debug.js:990)
at Queue.flush (ember.debug.js:1054)
at DeferredActionQueues.flush (ember.debug.js:862)
at Backburner.end (ember.debug.js:176)
at Backburner.run (ember.debug.js:298)
at Backburner.join (ember.debug.js:318)
at Function.run.join (ember.debug.js:23770)
at HTMLDocument.<anonymous> (ember.debug.js:23833)
at fire (jquery.js:3232)
at Object.fireWith [as resolveWith] (jquery.js:3362)
at Function.ready (jquery.js:3582)
at HTMLDocument.completed (jquery.js:3617)
This is issue 61, so, um...
LOL, whoops! Yes, I was talking about #60 (sorry about that).
Ah, forgot that axe-core
needs to be included in development mode as well as in testing. I'll have a fix shortly.