ES2017 support for protractor
See original GitHub issueHey, when I try to use ES2017 with protactor (in angular v5.0.1 unit-tests using karma) I get this error:
TypeError: undefined is not a function (evaluating 'Object.values(
Trying to add babel/register
to the config file did not help.
Is there a way to use ES2017 syntax with protactor and karma in angular v5 unit-tests?
Thanks.
- Versions -
- Node Version: 7.1.0
- Protractor Version: 2.1.7
- Angular Version: 5.0.1
- Operating System and Version Linux (Ubuntu)
Issue Analytics
- State:
- Created 6 years ago
- Comments:5
Top Results From Across the Web
Future of Angular E2E & Plans for Protractor #5502 - GitHub
Since Protractor was initially designed to support AngularJS, many of its features like locators and mock modules are specific to AngularJS.
Read more >How to Set up Visual Studio Code for Protractor Typescript?
This covers the complete set up of a Protractor Typescript project with the Visual Studio Code and installation of all the node modules...
Read more >Protractor is going to be Deprecated in 2022 - Katalon Studio
The Angular team plans to end development of Protractor at the end of 2022 (in conjunction with Angular v15). github.com/angular/protractor ...
Read more >Browser Support - Protractor - end-to-end testing for AngularJS
Driver Support Known Issues
ChromeDriver Yes Link
FirefoxDriver* Yes Link
SafariDriver Yes Link
Read more >10 Advanced Protractor topics - Testing Angular Applications
We've collected our best tips for working with Protractor in this chapter to help you get the most out of your end-to-end tests!...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@BarrMan , thanks for doing a follow-up. Would you like to close this issue?
@BarrMan I see that you are using typescript If you getting this error in runtime - you can try to set compiler target to “ES2016”, “ES2017” or “ESNext”, maybe that would allow you not to include polyfills.