Ugnius

@sschuberth Could you please take a look? Closes #723

Hey @tsteenbe ! First of all, thank you for your time and for reviewing my PR. The idea of this PR is to parse dependencies from iOS/macOS app projects that...

@tsteenbe I just noticed that when running `swift package show-dependencies --format json` inside a directory with a `Package.swift` file present. `Package.resolved` file automatically gets created and it contains the whole...

Awesome, so I will override `beforeResolution` method to perform `swift package show-dependencies --format json` if `allowDynamicVersions` configuration option is set to true. Fix the README and rebase my changes.

@tsteenbe @sschuberth I have added the conditional conversion of `Package.swift` to `Package.resolved` file inside `mapDefinitionFiles` override. This seemed like a better place to implement this rather than `beforeResolution` since we...

> > I just noticed that when running `swift package show-dependencies --format json` inside a directory with a `Package.swift` file present. `Package.resolved` file automatically gets created and it contains the...

> > So it could also be bootstrapped or included in the Docker image. > > Then I'd prefer to have it added to the Docker image as part of...

@sschuberth @MarcelBochtler I have updated the Dockerfile and Licenses. Also, the SPM analyzer now associates parent-child dependencies whenever parsing `Package.swift`. I have also provided the required test coverage. The [Package.swift](https://github.com/vapor/vapor/blob/main/Package.swift)...

@sschuberth @MarcelBochtler Any updates?

@MarcelBochtler I have updated the behavior when analyzing `Package.swift` without `allowDynamicVersions` set to true to throw `IllegalArgumentException` (just like NPM does). I have also written an additional test case for...