1/2 Lets say one has a repo that acts as a quick way to launch an #environment that consists of multiple other repos (think full stack - e.g., it might include a node.js app for frontend, a C# backend API, PostgreSQL for the db, redis for message queueing, and so on...).
Each of those child repos might have a .vscode folder with a launch.json file.
Ideally, if one opens the "quick launch" repo
[#]question #code #coding #programming
=> More informations about this toot | More toots from davidshq@hachyderm.io
2/2 in #vscode or #cursor the #debug tab would show the child launch configs as well as any in the top-level quickstart repo.
Unfortunately, it doesn't. From what I've read there isn't a way to aggregate launch.json files in such a setup. The only solution I've seen is to recreate the same launch configs in the quick start repo.
Curious if anyone knows of a way to bypass this? Maybe a vscode #extension ?
[#]question #code #coding #programming
=> More informations about this toot | More toots from davidshq@hachyderm.io
@davidshq monorepo is out of the question?
I think you could hack together a few utila and generators with nx and keep all the projects as subfolders of your nx "monorepo", but I don't think it would work out of the box.
=> More informations about this toot | More toots from zlatko@social.zlatko.dev
@zlatko yeah, not in my control - I also have little experience with monorepos.
=> More informations about this toot | More toots from davidshq@hachyderm.io This content has been proxied by September (3851b).Proxy Information
text/gemini