-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Is protractor no longer working when using Angular 13? #5544
Comments
I think this question should be addressed in angular/angular project. |
Hi @Heines1983, Here's an example:
Or you can see the file in my project with Angular 13 and Protractor : |
The issue is that you are trying to use an ES Module lib but you are running protractor with CommonJS which does not support it. I had the same problem updating to ang13. Our libs no longer generate UMD modules and we can no longer run protractor with them. Need to build our libs with a different tool than ng-packagr that still support UMD. |
@rbirkgit Yes, cannot import Angular libs for Protractor tests after Angular 13. |
@rbirkgit did you manage to find a fix? |
I changed to build our lib with rollup which supports CommonJS/UMD |
Could you give some references? I have the same issue and I haven't found a solution yet. |
Just in case somebody else has the same issue. Protractor and cucumber worked quite fine for me, but I haven't realized that in one of my steps, I was using angular libraries which indeed have a problem with protractor, as libraries in angular are esm, while in protractor commonjs. I had to replace some functions with pure typescript, js libraries, e.g. HTTP client for API calls, with request from nodejs, or axios library. |
I'm using protractor and recently upgraded from Angular 12 to Angular 13. I now get an error while starting the e2e tests.
Error: Error [ERR_REQUIRE_ESM]: require() of ES Module C:\git\ClientApp\node_modules@angular\cdk\fesm2015\testing.mjs not supported. Instead change the require of C:\git\ClientApp\node_modules@angular\cdk\fesm2015\testing.mjs to a dynamic import() which is available in all CommonJS modules.
Is this something caused by protractor, angular/cdk or something else?
The text was updated successfully, but these errors were encountered: