Closed dannys42 closed 8 months ago
Hey @dannys42, thanks for the report.
So, for local packages, it actually does not rely on the v
argument, but rather runs the analyzes on top of the current state of the local repo. So it might be failing to decode the package content, where some bits of the Package.swift
are attempted to be decoded as TSCUtility.Version
.
Could you please share more about your case? What's the output when running with --verbose
, and how does your Package.swift
looks like (if that's something you can share).
Hey @dannys42, did you manage to solve it?
When supplying a local path, I get the following error:
This occurs whether I specify a tagged version,
main
, or do not specify-v
.