Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
System version of node has priority over manually installed version
See original GitHub issueDescription:
After using actions/setup-node to install a specific node version, the system installed one apparently still has priority over manually installed version.
Couple of hours ago, my builds started to fail since one of the build tools uses /usr/local/bin/node, which is in version 16.13.2, while the one installed by setup-node is located at /opt/hostedtoolcache/node/14.18.3/x64
I presume that setup-node does not place the version it installed in path correctly, so the build tool finds the system version of node instead the manually installed one.
Action version: v2
Platform:
- Ubuntu
- macOS
- Windows
Runner type:
- Hosted
- Self-hosted
Tools version: Node 14 Yarn 1.22.17
Repro steps:
https://github.com/netgen-layouts/layouts-ezplatform/runs/5110578290?check_suite_focus=true
Expected behavior: I expected for the system to use Node version I installed manually.
Actual behavior: System uses preinstalled node version instead.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:2
- Comments:9
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
In our workflow only setup-php was updated.
It does not seem likely to me that this would or should impact setup-node.
However, running setup-php first and then setup-node actions fixed it for us.
So this looks like it’s an issue with
setup-phprather than this action, no?