[Go to site: main page, start]

setup-node

Set up your GitHub Actions workflow with a specific version of node.js (by actions)

Setup-node Alternatives

Similar projects and alternatives to setup-node

  1. pages-gem

    A simple Ruby Gem to bootstrap dependencies for setting up and maintaining a local Jekyll environment in sync with GitHub Pages

  2. SaaSHub

    SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives

    SaaSHub logo
  3. vscodium

    binary releases of VS Code without MS branding/telemetry/licensing

  4. starter-workflows

    Accelerating new GitHub Actions workflows

  5. Jenkins

    Jenkins automation server

  6. act

    Run your GitHub Actions locally 🚀

  7. pyright

    151 setup-node VS pyright

    Static Type Checker for Python

  8. openvsx

    An open-source registry for VS Code extensions

  9. checkout

    88 setup-node VS checkout

    Action for checking out a repo

  10. runner-images

    79 setup-node VS runner-images

    GitHub Actions runner images

  11. virtual-environments

    Discontinued GitHub Actions runner images [Moved to: https://github.com/actions/runner-images]

  12. cache

    48 setup-node VS cache

    Cache dependencies and build outputs in GitHub Actions

  13. actions-gh-pages

    GitHub Actions for GitHub Pages 🚀 Deploy static files and publish your site easily. Static-Site-Generators-friendly.

  14. toolkit

    22 setup-node VS toolkit

    The GitHub ToolKit for developing GitHub Actions.

  15. setup-python

    12 setup-node VS setup-python

    Set up your GitHub Actions workflow with a specific version of Python

  16. setup-java

    12 setup-node VS setup-java

    Set up your GitHub Actions workflow with a specific version of Java

  17. actions-hugo

    11 setup-node VS actions-hugo

    GitHub Actions for Hugo ⚡️ Setup Hugo quickly and build your site fast. Hugo extended, Hugo Modules, Linux (Ubuntu), macOS, and Windows are supported.

  18. setup-buildx-action

    GitHub Action to set up Docker Buildx

  19. setup-go

    6 setup-node VS setup-go

    Set up your GitHub Actions workflow with a specific version of Go

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better setup-node alternative or higher similarity.

setup-node discussion

Log in or Post with

setup-node reviews and mentions

Posts with mentions or reviews of setup-node. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2025-05-16.
  • Run your GitHub Actions locally
    10 projects | news.ycombinator.com | 16 May 2025
    I use this for work - but there are edge cases all over the place that I keep running into (e.g. Yarn being installed on Github-hosted runners, but not self-hosted ones or act - https://github.com/actions/setup-node/issues/182)

    Apart from that it's been quite good!

  • Building Efficient Node.js Workflows in GitHub Actions: Leveraging Caching and Modular Job Structures
    5 projects | dev.to | 8 Nov 2024
    What is actions/checkout and actions/setup-node
  • CI/CI deploy a static website to AWS S3 bucket through Github Actions
    5 projects | dev.to | 22 Dec 2023
    Setup environment with Nodejs and install dependencies with npm install, with Github Actions setup Node
  • VSCodium – Libre Open Source Software Binaries of VS Code
    10 projects | news.ycombinator.com | 4 Sep 2023
    No, PR review isn't the only thing that prevents these from being updated. In the yml it's set to a release branch. So it isn't especially fallible.

    https://github.com/actions/setup-node/tree/releases/v2

  • Disable Annotations in Github Actions
    5 projects | dev.to | 3 Sep 2023
  • A guide to using act with GitHub Actions
    5 projects | dev.to | 23 Mar 2023
    ➜ getting-started-with-act git:(master) act -j build WARN ⚠ You are using Apple M1 chip and you have not specified container architecture, you might encounter issues while running act. If so, try running it with '--container-architecture linux/amd64'. ⚠ [Node.js CI/build] 🚀 Start image=node:16-buster-slim [Node.js CI/build] 🐳 docker pull image=node:16-buster-slim platform= username= forcePull=false [Node.js CI/build] 🐳 docker create image=node:16-buster-slim platform= entrypoint=["tail" "-f" "/dev/null"] cmd=[] [Node.js CI/build] 🐳 docker run image=node:16-buster-slim platform= entrypoint=["tail" "-f" "/dev/null"] cmd=[] [Node.js CI/build] ☁ git clone 'https://github.com/actions/setup-node' # ref=v3 [Node.js CI/build] ☁ git clone 'https://github.com/actions/cache' # ref=v3 [Node.js CI/build] ☁ git clone 'https://github.com/actions/upload-artifact' # ref=v3 [Node.js CI/build] ⭐ Run Main actions/checkout@v3 [Node.js CI/build] 🐳 docker cp src=/Users/andrewevans/Documents/projects/getting-started-with-act/. dst=/Users/andrewevans/Documents/projects/getting-started-with-act [Node.js CI/build] ✅ Success - Main actions/checkout@v3 [Node.js CI/build] ⭐ Run Main Use Node.js 16.x [Node.js CI/build] 🐳 docker cp src=/Users/andrewevans/.cache/act/actions-setup-node@v3/ dst=/var/run/act/actions/actions-setup-node@v3/ [Node.js CI/build] 🐳 docker exec cmd=[node /var/run/act/actions/actions-setup-node@v3/dist/setup/index.js] user= workdir= [Node.js CI/build] 💬 ::debug::isExplicit: [Node.js CI/build] 💬 ::debug::explicit? false
  • Cheap Gatsby/Netlify-style Hosting?
    1 project | /r/gatsbyjs | 8 Oct 2022
    steps: # Check out the current repository code - uses: actions/checkout@v3 # 3. https://github.com/actions/setup-node#usage - name: Setup node and build Gatsby uses: actions/setup-node@v1 with: node-version: '16.x' cache: 'npm' - run: npm install # This triggers `gatsby build` script in "package.json" - run: npm run build # 4. Deploy the gatsby build to Netlify - name: Deploy to netlify uses: netlify/actions/cli@master env: NETLIFY_AUTH_TOKEN: ${{ secrets.NETLIFY_AUTH_TOKEN }} NETLIFY_SITE_ID: ${{ secrets.NETLIFY_SITE_ID }} with: # 5. "gatsby build" creates "public" folder, which is what we are deploying args: deploy --dir=public --prod secrets: '["NETLIFY_AUTH_TOKEN", "NETLIFY_SITE_ID"]'
  • 5 Ways to make development with GitHub Actions more efficient
    2 projects | dev.to | 27 Sep 2022
    If you see repeated build or preparation steps that do not change when your codebase changes, look into caching the results. Here is a straightforward guide to caching, but also be aware caching is built into a lot of marketplace actions anyway, e.g. actions/setup-node can cache npm dependencies.
  • Top 10 GitHub Actions You Should Use to set up your CI/CD Pipeline
    5 projects | dev.to | 12 Sep 2022
    The most popular ones are Node.js, Python, Java JDK, Go, .Net Core SDK.
  • The strongest principle of the blog's growth lies in the human choice to deploy it
    14 projects | dev.to | 3 Sep 2022
  • A note from our sponsor - SaaSHub
    www.saashub.com | 20 Jun 2026
    SaaSHub helps you find the best software and product alternatives Learn more →

Stats

Basic setup-node repo stats
26
4,837
7.4
11 days ago

Sponsored
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com

Did you know that TypeScript is
the 2nd most popular programming language
based on number of references?