Skip to content

Conversation

@Zaubeerer
Copy link

Just adding a launch configuration for convenience to start both frontend and backend with a single command.

"url": "http://localhost:5173",
"webRoot": "${workspaceFolder}/frontend"
"webRoot": "${workspaceFolder}/frontend",
// "runtimeExecutable": "/usr/bin/google-chrome"
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As described in #729, I am having trouble running the debug session on WSL.
I added this comment in case others encounter similar errors.

However, it did not solve my problem, so we could as well delete the comment and create a new PR to tackle #729.

],
"compounds": [
{
"name": "Debug Fullstack",
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am pretty sure this should work, but was not able to test it yet, due to #729.

@alejsdev alejsdev changed the title Add debug launch config "Debug Fullstack" 🔧 Add debug launch config "Debug Fullstack" Apr 3, 2024
@tiangolo
Copy link
Member

Thanks! I would prefer to keep the two commands, so that people can start the debugger for the component they want to work on (frontend or backend), and if they want both, to opt-in doing it explicitly by running both. So, for now I'll pass on this one, but thanks for the effort! 🍰

@tiangolo tiangolo closed this Sep 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants