You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
asdf only has *nix support but sometimes we use asdf to build tools for all platforms. When it comes to writting tests for unsupported platforms, namely Windows, we have to resort to doubling up our workflow tool installation.
Note the hardcoded node-version in the Windows section.
solution
If asdf were to output the contents of the .tool-versions file as an object, this could be referenced in later steps in the CI pipeline, removing the need for hard-coded values when supporting other OSs.
problem
asdf
only has *nix support but sometimes we useasdf
to build tools for all platforms. When it comes to writting tests for unsupported platforms, namely Windows, we have to resort to doubling up our workflow tool installation.An example from
svelte-adapter-firebase
CI pipeline:Note the hardcoded
node-version
in the Windows section.solution
If
asdf
were to output the contents of the.tool-versions
file as an object, this could be referenced in later steps in the CI pipeline, removing the need for hard-coded values when supporting other OSs.EG:
This seems relatively simple to implement and give a more flexible solution to this problem than currently available.
alternatives
I have yet to explore running WSL in the Action Windows runner, which might prove a more useful solution.
The text was updated successfully, but these errors were encountered: