-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Support systems without preexisting nodejs #1287
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hello @a-b, Thank you for creating this issue and we will look into it :) |
Hi @a-b, |
Can you explain what is unreasonable about rewriting it as a shell script to eliminate the dependency on Node? This would allow the installation and configuration of the specified version of Node on a greenfield system. |
@mahabaleshwars please elaborate on what motivated you to consider my request as a spam. |
Hi @a-b, |
jobs: |
Hi @a-b, Thank you for bringing this issue to our attention. To help us investigate and assist you more effectively, could you please elaborate on the problem you're encountering? Specifically, it would be helpful if you could provide additional details regarding your setup and expectations. Additionally, we kindly request that you share relevant workflow runs or logs that demonstrate the issue. These details will allow us to better understand your scenario and identify a suitable resolution. Looking forward to your response! |
Hello @a-b, Just a gentle reminder! Could you please let us know if there are any updates from your side regarding this issue? |
The issue persists; I cannot run this action without Node. |
Hi @a-b, Thank you for your response. To help us investigate this issue further, we kindly request you to provide the following details:
These additional details will allow us to better understand your scenario and identify a resolution. Without this information, it will be challenging for us to proceed with the investigation. Looking forward to your input! |
Hy @pablopicasso111, Thank you for your feedback and for providing the code snippet. The screenshot of the workflow run is given as of below: ![]() We have tried running the workflow from our end using the code you shared, and it executed successfully without any errors. To help us better understand and resolve your issue, could you please provide more details about the problems you are encountering? Specifically, it would be helpful if you could:
This information will help us investigate further and assist you more effectively. Thank you! |
Hi @a-b, This is a friendly reminder that we have not yet received any additional details, relevant workflow runs, or logs from your end, nor have we seen an explanation of the specific problem you’re encountering. Sharing these details would be extremely helpful and allow us to continue our investigation more effectively. Moreover, Rewriting the setup-node action as a shell script might seem like a straightforward solution to remove the dependency on Node.js for initial installation, but there are several reasons why we have chosen to implement it in Node.js. The setup-node action’s advanced features, cross-platform support, maintainability, and integration with the Actions ecosystem make Node.js a more practical and robust choice for this action. Also, If you could provide the above mentioned information at your earliest convenience, we’d be happy to assist further. Thank you! |
Description:
This action is not working if there is no preexisting node on the system
Action version:
v4
Platform:
Runner type:
Repro steps:
Run workflow on the runner without nodejs.
Expected behavior:
Action won't depend on the existing nodejs to install one on the system
Actual behavior:
Getting an error that there is no nodejs.
The text was updated successfully, but these errors were encountered: