Is protractor no longer working when using Angular 13?

Question

Is protractor no longer working when using Angular 13?

Heines1983 opened this issue 2 years ago · comments

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?

Stanislav Kharchenko · Answer 1 · Fri Jan 14 2022 20:14:24 GMT+0800 (China Standard Time)

I think this question should be addressed in angular/angular project.

André de Sousa · Answer 2 · Wed Jan 19 2022 05:18:37 GMT+0800 (China Standard Time)

Hi @Heines1983,
I think this must be a problem with your e2e/tsconfig.json file.
Please check the module attribute in your configuration.

Here's an example:

{ "extends": "../tsconfig.json", "compilerOptions": { "outDir": "../out-tsc/e2e", "module": "commonjs", "types": [ "jasmine", "node" ] } }

Or you can see the file in my project with Angular 13 and Protractor :
https://github.com/andredesousa/angular-linters/blob/main/e2e/tsconfig.json

Ron Birk · Answer 3 · Sat Mar 26 2022 04:03:22 GMT+0800 (China Standard Time)

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.

André de Sousa · Answer 4 · Sat Mar 26 2022 09:10:00 GMT+0800 (China Standard Time)

@rbirkgit Yes, cannot import Angular libs for Protractor tests after Angular 13.

robertIsaac · Answer 5 · Fri Jun 10 2022 21:39:18 GMT+0800 (China Standard Time)

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 did you manage to find a fix?

Ron Birk · Answer 6 · Fri Jun 10 2022 21:42:10 GMT+0800 (China Standard Time)

I changed to build our lib with rollup which supports CommonJS/UMD