Debugging JavaScript frontend does not work

[iCodeSometime]

Describe the need of your request

When launching our full app for local development with our aspire AppHost, we can debug the dotnet projects, but breakpoints in our JavaScript frontend won’t be hit, even though “with JavaScript debugger” is selected in the aspire run configuration.

Proposed solution

A fronted added with either an esproj or AddNpmApp is debuggable by default with no extra steps, similar to a csproj.

Alternatives you've considered

Some additional manual steps that get JavaScript debugging working, with documentation.

Additional context

No response

[iCodeSometime]

This one is important to me, so I’d be happy to contribute the feature, but it would be my first jetbrains plugin work, so some guidance on where to start looking and what the relevant APIs are would be helpful

[rafaelldi]

@iCodeSometime Hi! I don't have any experience with JavaScript. Could you please create a sample application and describe the steps in detail? I will take a look.

A fronted added with either an esproj or AddNpmApp is debuggable by default with no extra steps, similar to a csproj.

It may be required not from our side but from Aspire itself. Because for a regular csproj it is Aspire that asks the IDE to run it with the debugger. For other types of resources (containers or executables), Aspire handles them on its own. Maybe with esproj projects this will be possible.

[iCodeSometime]

It is run as an executable, but the exe only compiles and runs a simple server. The executable shouldn't be debugged, the generated JavaScript should be, once opened in the browser.

So, I assume it's not really important whether the IDE starts the process or not.

I'll put together a sample.