The way it works: the plug-in forks a KobaltServer...
# kobalt
c
The way it works: the plug-in forks a KobaltServer then asks it the dependencies of the current build file. The server returns these dependencies in JSON form and then the plug-in modifies the project structure (libraries and modules) with that information.