It’s expensive & time-consuming to automatically attach debuggers to every child process when using a task runner like yarn. We don’t need to attach to the yarn process, but can end up getting a large chain of attached debuggers, when we only want to debug the leaf process.
We can fix this in the integrated terminal only by configuring like so:
{
"debug.javascript.autoAttachFilter": "smart",
"debug.javascript.autoAttachSmartPattern": ["<PATH_TO_DESIRED_PROGRAM>"]
}
This prevents attaching to everything except the leaf processes that you specify, which greatly improves startup time.
However, this functionality is only enabled in the integrated terminal—nowhere else supports autoAttachSmartPattern.
I think that we should enable autoAttachSmartPattern in the launch.json options and it would function the same way.
Apologies if I’m missing something—I pored over the docs but I couldn’t find a different way to make this work.
It’s expensive & time-consuming to automatically attach debuggers to every child process when using a task runner like
yarn. We don’t need to attach to theyarnprocess, but can end up getting a large chain of attached debuggers, when we only want to debug the leaf process.We can fix this in the integrated terminal only by configuring like so:
{ "debug.javascript.autoAttachFilter": "smart", "debug.javascript.autoAttachSmartPattern": ["<PATH_TO_DESIRED_PROGRAM>"] }This prevents attaching to everything except the leaf processes that you specify, which greatly improves startup time.
However, this functionality is only enabled in the integrated terminal—nowhere else supports
autoAttachSmartPattern.I think that we should enable
autoAttachSmartPatternin thelaunch.jsonoptions and it would function the same way.Apologies if I’m missing something—I pored over the docs but I couldn’t find a different way to make this work.