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
I have created a new project using the Angular CLI (v.8) and imported Wallaby from our other Angular 7 apps (using the legacy core-js package). This app we updated to 3.1.3 and updated our polyfills to use import 'core-js/es/reflect';
On running Wallaby however most of the tests fail with the following errors: Error: Can’t resolve all parameters for ApplicationModule: (?).
Note: your example Angular v7 app also uses the legacy package "core-js": "^2.5.4"
/*************************************************************************************************** * BROWSER POLYFILLS *//** IE10 and IE11 requires the following for NgClass support on SVG elements */// import 'classlist.js'; // Run `npm install --save classlist.js`./** Safari 7 & 8, IE10 & 11, Android 4.1+ requires the following. */import'core-js/es';// IE Support for Object.matchesif(!Element.prototype.matches){Element.prototype.matches=(<any>Element.prototype).msMatchesSelector||Element.prototype.webkitMatchesSelector;}/** * Web Animations `@angular/platform-browser/animations` * Only required if AnimationBuilder is used within the application and using IE/Edge or Safari. * Standard animation support in Angular DOES NOT require any polyfills (as of Angular 6.0). */// import 'web-animations-js'; // Run `npm install --save web-animations-js`./** * By default, zone.js will patch all possible macroTask and DomEvents * user can disable parts of macroTask/DomEvents patch by setting following flags * because those flags need to be set before `zone.js` being loaded, and webpack * will put import in the top of bundle, so user need to create a separate file * in this directory (for example: zone-flags.ts), and put the following flags * into that file, and then add the following code before importing zone.js. * import './zone-flags.ts'; * * The flags allowed in zone-flags.ts are listed here. * * The following flags will work for all browsers. * * (window as any).__Zone_disable_requestAnimationFrame = true; // disable patch requestAnimationFrame * (window as any).__Zone_disable_on_property = true; // disable patch onProperty such as onclick * (window as any).__zone_symbol__UNPATCHED_EVENTS = ['scroll', 'mousemove']; // disable patch specified eventNames * * in IE/Edge developer tools, the addEventListener will also be wrapped by zone.js * with the following flag, it will bypass `zone.js` patch for IE/Edge * * (window as any).__Zone_enable_cross_context_check = true; * *//*************************************************************************************************** * Zone JS is required by default for Angular itself. */import'zone.js/dist/zone';// Included with Angular CLI./*************************************************************************************************** * APPLICATION IMPORTS */// Angular Material https://material.angular.io/guide/getting-started#step-5-gesture-supportimport'hammerjs';
Code editor or IDE name and version
Visual Studio Code v1.34.0
OS name and version
OSX 10.14.5
The text was updated successfully, but these errors were encountered:
michael-letcher
changed the title
Tests fail in Angular 8 w/ latest core-js
ISSUE: Tests fail in Angular 8 w/ latest core-js
Jun 3, 2019
michael-letcher
changed the title
ISSUE: Tests fail in Angular 8 w/ latest core-js
[BUG] Tests fail in Angular 8 w/ latest core-js
Jun 3, 2019
Issue description or question
I have created a new project using the Angular CLI (v.8) and imported Wallaby from our other Angular 7 apps (using the legacy core-js package). This app we updated to 3.1.3 and updated our polyfills to use
import 'core-js/es/reflect';
On running Wallaby however most of the tests fail with the following errors:
Error: Can’t resolve all parameters for ApplicationModule: (?).
Note: your example Angular v7 app also uses the legacy package
"core-js": "^2.5.4"
Similar issue #1900
To fix this if we downgrade, to v2 of core-js it seems to go away. Seems to be an issue with wallaby and core-js's v3 of
reflect
Wallaby.js configuration file
Package.json
wallabyTest.ts
polyfills.ts
Code editor or IDE name and version
Visual Studio Code v1.34.0
OS name and version
OSX 10.14.5
The text was updated successfully, but these errors were encountered: