Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update stack-chain to 2.0.0 #2107

Closed
rquellh opened this issue Feb 7, 2018 · 3 comments
Closed

Update stack-chain to 2.0.0 #2107

rquellh opened this issue Feb 7, 2018 · 3 comments
Labels
STATE: Auto-locked An issue has been automatically locked by the Lock bot. TYPE: enhancement The accepted proposal for future implementation.
Milestone

Comments

@rquellh
Copy link

rquellh commented Feb 7, 2018

Are you requesting a feature or reporting a bug?

Feature

What is the current behavior?

TestCafe uses an earlier version of stack-chain. When TestCafe is integrated with the latest version of CucumberJS (4.0.0) there is an error "Conflicting version of stack-chain found."

What is the expected behavior?

Updated stack-chain to 2.0.0. I manually updated TestCafe to stack-chain version 2.0.0 and TestCafe seems to function normally, but there might be some outlying conditions that would cause errors.

How would you reproduce the current behavior (if this is a bug)?

See my repo and just install; don't do the extra steps.

Provide the test code and the tested page URL (if applicable)

See my repo and just install; don't do the extra steps.

Specify your

  • operating system: Windows 10
  • testcafe version: 0.18.6
  • node.js version: 8.9.3
@AlexanderMoskovkin AlexanderMoskovkin added the TYPE: enhancement The accepted proposal for future implementation. label Feb 8, 2018
@AlexanderMoskovkin AlexanderMoskovkin added this to the Sprint #10 milestone Feb 8, 2018
@AlexanderMoskovkin
Copy link
Contributor

Hi @rquellh,

Thanks for pointing this out, we'll check it soon!

@AlexanderMoskovkin AlexanderMoskovkin self-assigned this Feb 8, 2018
@AlexanderMoskovkin
Copy link
Contributor

The issue is fixed in #2113. Will be included to the next release. I guess we can publish a dev build the next week

@lock
Copy link

lock bot commented Mar 28, 2019

This thread has been automatically locked since it is closed and there has not been any recent activity. Please open a new issue for related bugs or feature requests. We recommend you ask TestCafe API, usage and configuration inquiries on StackOverflow.

@lock lock bot added the STATE: Auto-locked An issue has been automatically locked by the Lock bot. label Mar 28, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Mar 28, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
STATE: Auto-locked An issue has been automatically locked by the Lock bot. TYPE: enhancement The accepted proposal for future implementation.
Projects
None yet
Development

No branches or pull requests

2 participants