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.

Sign up for GitHub

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

Jump to bottom

Misleading debugging information: "Node.js and the Chrome need to be run on the same platform" #6853

Open
june07 opened this issue Jun 20, 2024 · 2 comments · May be fixed by #6855
Open

Misleading debugging information: "Node.js and the Chrome need to be run on the same platform" #6853

june07 opened this issue Jun 20, 2024 · 2 comments · May be fixed by #6855
Labels
bug

Comments

@june07
Copy link
Contributor

june07 commented Jun 20, 2024

URL:

https://nodejs.org/en/learn/getting-started/debugging

Browser Name:

Chrome

Browser Version:

126.0.6478.62

Operating System:

Windows

How to reproduce the issue:

Screenshot 2024-06-20 154224

Since when has this been the case?!

The requirement that Node.js and Chrome need to be run on the same platform is not accurate in the context of debugging. Cross-platform debugging using Chrome DevTools is a standard practice and works seamlessly due to the underlying network and WebSocket protocols that facilitate communication between Node.js and DevTools. The documentation should ideally clarify this to avoid confusion.

I have no idea why this was added in the first place...
15774e7
@june07 june07 added the bug label Jun 20, 2024
@ovflowd
Copy link
Member

ovflowd commented Jun 21, 2024

Please feel free to open a PR to fix this; I also have no record of why this was merged/added. This was before my time on the project.

@Wellitsabhi
Copy link

should i just remove that portion ??
will that be it.

@Wellitsabhi Wellitsabhi linked a pull request Jun 21, 2024 that will close this issue
Open
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: Removed misleading info Wellitsabhi/nodejs.org-fork
3 participants
@june07 @ovflowd @Wellitsabhi