DevExpress / DevExpress/testcafe

@testcafe uses deprecated package p-finally

Open
#8,494 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

STATE: Issue accepted TYPE: bug
Dominant language
JavaScript
Stars
9.9k
Forks
676
PR merge metrics
No merged PRs in 30d

Description

What is your Scenario?

└─┬ testcafe@3.7.4
└─┬ testcafe-browser-tools@2.0.26
└─┬ execa@3.4.0
└── p-finally@2.0.1

What is the Current behavior?

https://www.npmjs.com/package/p-finally?activeTab=readme
p-finally package has been deprecated

Solution -
execa(9.6.1) is no longer using 'p-finally'

testcafe should adopt latest execa(9.6.1) version i.e. to get rid of p-finally from BOM

What is the Expected behavior?

see current BOM where deprecated version is used

What is the public URL of the test page? (attach your complete example)

https://cloud.sw.siemens.com/nx

What is your TestCafe test code?

Vue 3 application

Your complete configuration file

No response

Your complete test report

No response

Screenshots

No response

Steps to Reproduce
  1. include package testcafe@3.7.4
TestCafe version

3.7.4

Node.js version

v22.22.0

Command-line arguments

npm ls p-finally

Browser name(s) and version(s)

No response

Platform(s) and version(s)

No response

Other

No response

Contributor guide

Open the contributing guide

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

Start by inspecting TestCafe's dependency declarations and the reported chain through testcafe-browser-tools and execa. Run npm ls p-finally against the current release, then assess whether the proposed execa 9.6.1 upgrade is compatible. Done means the dependency tree no longer includes deprecated p-finally and TestCafe's existing checks still pass.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, node.js
Domain
testing-qa, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.