Muck
Muck copied to clipboard
A command line tool to analyse dependencies in your Swift projects
Modules are currently passed as command-line arguments but better would be to find the modules in a workspace/project.
If all source is under a folder called `Source`, for instance, that should be stripped from names to make them shorter.
Currently SourceKitten appears to ignore Objective-C source files when analysing a module. This means Objective-C that depends on other Objective-C or Swift code is ignored. Furthermore, Swift code that depends...
Current workaround is to generate an Xcode project and run it against that.
The slow part is analysing the source for declarations, but once this is done it is very easy to generate many different reports. It would be useful to be able...