DevExpress / DevExpress/testcafe-browser-tools

Uses deprecated core-js version 2.6.11

Open
#207 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

STATE: Need clarification
Dominant language
C++
Stars
30
Forks
32
PR merge metrics
No merged PRs in 30d

Description

Hi, testcafe looks really cool so I wanted to try it. As soon as I yarn added it though, I got these messages:

warning testcafe > babel-runtime > core-js@2.6.11: core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
warning testcafe > testcafe-legacy-api > babel-runtime > core-js@1.2.7: core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
warning testcafe > babel-core > babel-register > core-js@2.6.11: core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.

I knew something would be broken and indeed my app no longer compiles. As soon as I install testcafe I start getting a bunch of errors like this:

ERROR in ./app/App.js
Module not found: Error: Can't resolve 'core-js/modules/es.array.concat' in '/Users/xxx/Sites/xxx/app'
 @ ./app/App.js 4:0-41
 @ ./app/main.js
 @ multi ./app/main.js

This is happening because testcafe requires core-js@2.6.11 that's no longer maintained and my app is setup to use the most up to date core-js@3.6.5.

I really wanted to use testcafe since it looks very nice. Hope this issue can be addressed soon.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the dependency warnings with yarn add testcafe and inspect the dependency chain through babel-runtime, testcafe-legacy-api, and babel-core. Check the reported failure in app/App.js and app/main.js; done means TestCafe no longer forces incompatible core-js versions and the application compiles successfully.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.