Was this outputTo attribute removed during the namespace update from task > taskfile?

[netopsengineer]

Hello @pd93 - after receiving the message to update my settings.json, I noticed that task is no longer using the terminal when set to outputTo: "terminal", and since this seems to invoke task in a normal terminal as if I had opened it up inside VS Code, the behaviors match what any other terminal session feels like, i.e. venv's activated and such. Without this attribute, the way task invokes the terminal now, it does not have the same access to the environment as the previous setting allowed, which is causing several of my tasks across many projects to no longer work. Was it mistakenly left off, or gone for good?

[pd93]

Hi @netopsengineer, it's not necessarily gone forever. However, the change was intentional. The hope was that the built in Task runner from vscode would take some of the maintenance burden off us as it is already well established and used for a lot of other Task runners. In many ways, it also combined the best of both worlds from the two previous output types and fixed a number of open issues.

If it doesn't work for you, please open an issue with a reproducible example of something that previously worked that now doesn't. I will take a look to see what can be done.

[beholdr]

My use case: some tasks are long-running, like npm run dev that starts a server. And if you start a new task, when previous task is running, it does nothing while current terminal runs previous task. Opening each task in a new terminal helps here.