Fix Node debugging by catching warning #724

New Issue

fergalmoran · 2025-08-09T17:17:26Z

fergalmoran commented

2025-08-09 17:17:26 +00:00

Originally created by @novascreen on 5/24/2017

Following up on #804

Fixes the debugger which causes the .NET Core app to crash due to a Node warning.

Unfortunately it's hard to make this really future proof, because the wording and structure of the warnings regarding debugging could easily change in future versions. I still think it would be nice to be able to treat all warnings from Node differently from errors, but no idea how to approach that. Cause for a separate discussion I suppose.

*Originally created by @novascreen on 5/24/2017* Following up on #804 Fixes the debugger which causes the .NET Core app to crash due to a Node warning. Unfortunately it's hard to make this really future proof, because the wording and structure of the warnings regarding debugging could easily change in future versions. I still think it would be nice to be able to treat all warnings from Node differently from errors, but no idea how to approach that. Cause for a separate discussion I suppose.

fergalmoran closed this issue

2025-08-09 17:17:26 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/JavaScriptServices#724