CLI: running -a common@latest throws an error in 1.9.1

[josephjclark]

Investigate, this should be fine!

[doc-han]

Here @josephjclark
Investigated this a bit because my openfn cli just keeps erroring instead of running workflows for me.

Observation

When common@latest is used, during installation, we resolve the version to find the latest version for installation.
Hence, instead of common@latest, we install [email protected].
But then during the linking stage, we seem to forget this process and then try linking common@latest intead of [email protected] which was installed. This issue might exist for all adaptors (probably)

Possible solutions

After resolving a <pkg>@latest to it's version and installing. We can create a symbolic link in the node_modules directory to map <pkg>@latest to <pkg>@version-number

[josephjclark]

Hey @doc-han - no need to symlink anything. Far too complicated. We normally just annotate the metadata object either with the correct version number, or with an explicit path to the adaptor.

I can't provide much guidance right now but there is precedence in the code, although it's a bit messy. Maybe look to see how @next is handled.

Or just have auto install override the version on the workflow when it resolves @latest