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

Can't use console to debug plugins run with "nodeVersion" : "system" #5587

Closed
Talii123 opened this issue Nov 3, 2019 · 4 comments
Closed
Labels
stage: needs investigating Someone from Cypress needs to look at this stale no activity on this issue for a long period

Comments

@Talii123
Copy link

Talii123 commented Nov 3, 2019

Current behavior:

console.log(..) and console.error(..) statements in plugins do NOT produce output in the console used to open cypress if the {nodeVersion: "system"} setting is used.

All works as expected if:

  • using Cypress v3.4
  • using Cypress v3.5, v3.6 provided that {nodeVersion: "system"} is not used.

Desired behavior:

We should be able to continue to use console.log/error to print messages to the console as part of our debugging approach when running plugins with our system's node.

Steps to reproduce: (app code and test code)

In your cypress.json, include:
"nodeVersion": "system"

In your plugin file, include:

console.log('You can't see me!')

Versions

Cypress v3.5 and 3.6
OS: Windows 10
Browser: N/A

Related: #4432

@brian-mann
Copy link
Member

Haven't looked into this, but we should be inheriting the stdio streams from the child process so they should log out. We'll look at it and see what's up. Should be an easy fix if that's the case.

@brian-mann brian-mann added the stage: needs investigating Someone from Cypress needs to look at this label Nov 3, 2019
@Talii123
Copy link
Author

Talii123 commented Nov 4, 2019

Yeah I figured as much. Thanks @brian-mann

@cypress-app-bot
Copy link
Collaborator

This issue has not had any activity in 180 days. Cypress evolves quickly and the reported behavior should be tested on the latest version of Cypress to verify the behavior is still occurring. It will be closed in 14 days if no updates are provided.

@cypress-app-bot cypress-app-bot added the stale no activity on this issue for a long period label May 17, 2023
@cypress-app-bot
Copy link
Collaborator

This issue has been closed due to inactivity.

@cypress-app-bot cypress-app-bot closed this as not planned Won't fix, can't repro, duplicate, stale Jun 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stage: needs investigating Someone from Cypress needs to look at this stale no activity on this issue for a long period
Projects
None yet
Development

No branches or pull requests

3 participants