Jason Platts

Yeah, I agree. It seems like it might be better as an extension. Nova offers tasks, https://docs.nova.app/extensions/run-configurations/.

> As @lukepistrol said, we implement API for extensions to provide targets, tests and so on. So, NodeJS extension reads `package.json` and creates `npm start` target and anything else using...

# Overview The Task Provider should allow extension developers to define external tools that can be run from a CodeEdit menu option and the command palette. These tasks should be...

That's an interesting option @henryhchchc. I think at this point we are probably best sticking with Swift and/or JavaScript as our primary focus. In my opinion, considering the large VS...

To the Swift developers, @pkasila, @MarcoCarnevali, @underthestars-zhy, and any others, how could we go about writing this API in Swift and then packaging/compiling/submitting the extensions in an approachable way? Please...

Awesome @pkasila!

> ## Compiling and packaging extension > Extensions should be compiled as dynamic libraries (`dylib`s). > > The minimal extension's package structure should be as follows: > > ``` >...

> ## Submitting extensions > * both extensions' manifests and packages are submitted by the developer and stored by us I am in favor of this option if we can...

Thanks @pkasila. Sounds to me like a solid starting point. I know there will be details to figure out and a lot of trial and error as we go.

Yeah, thanks @FezVrasta. This is great. I'd never heard of it before.