@devoncarew I added code to print Logging events, though I'm not sure how spammy this is going to be (we have no good way to filter it in VS Code here, so if lots of libraries write a lot of output, it's going to fill the users debug console).

I could write the output all to another pane (an Output channel), though we don't have any ability to link to source code in there (though I don't know that matters for these?).

I think having it in-line with the other output makes sense. If things do get too verbose, we may want to add ways to toggle on and off specific channels, or hide the output altogether.

I was thinking that if a user pulls in some dependency that is really chatty and we don't already have some filter, their own output could get lost. There's no great way for us to build a UI to let them filter out sources (the best we can do right now is probably in the Workspace Settings JSON, excluding them by name). I have no idea how many people use dart:developer's log function though. If it's practically nobody, then it's less urgent (if it's used a lot, I think we probably need some sort of filter before we ship this).