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

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 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 2022-09-27.
  • 5 Ways to make development with GitHub Actions more efficient
    2 projects | | 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 | | 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 | | 3 Sep 2022
    diff --git a/.github/workflows/gh-pages.yaml b/.github/workflows/gh-pages.yaml index 401fd33..3ddf6dd 100644 --- a/.github/workflows/gh-pages.yaml +++ b/.github/workflows/gh-pages.yaml @@ -11,42 +11,48 @@ on: jobs: deploy: - runs-on: ubuntu-20.04 + runs-on: ubuntu-22.04 + # Ensure that only a single job or workflow + # concurrency: + # workflow - The name of the workflow. + # ref - The branch or tag ref that triggered the workflow run. group: ${{ github.workflow }}-${{ github.ref }} steps: - uses: actions/[email protected] with: - submodules: true # Fetch Hugo themes (true OR recursive) fetch-depth: 0 # Fetch all history for .GitInfo and .Lastmod + # - name: Setup Hugo uses: peaceiris/[email protected] with: - hugo-version: '0.91.2' - # extended: true + hugo-version: '0.101.0' + # - name: Setup Node uses: actions/[email protected] with: - node-version: '14' - - - name: Cache dependencies - uses: actions/[email protected] - with: - path: ~/.npm - key: ${{ runner.os }}-node-${{ hashFiles('**/package-lock.json') }} - restore-keys: | - ${{ runner.os }}-node- - - - run: npm ci + node-version: '18.7.0' + cache: npm + # The action defaults to search for the dependency file (package-lock.json, + # npm-shrinkwrap.json or yarn.lock) in the repository root, and uses its + # hash as a part of the cache key. + # + cache-dependency-path: ./blog/package-lock.json + + - name: Install npm dependencies + working-directory: ./blog/ + run: npm ci - name: Build - run: hugo --minify + working-directory: ./blog/ + run: npm run build + # - name: Deploy uses: peaceiris/[email protected] if: ${{ github.ref == 'refs/heads/main' }} with: github_token: ${{ secrets.GITHUB_TOKEN }} - publish_dir: ./public + publish_dir: ./blog/src/public
  • How Fastly manages its software with GitHub Actions
    15 projects | | 31 Aug 2022
    Well, let’s consider the scenario we had with the DevHub. We were using the third-party action setup-node to install and configure the Node.js programming language. This action lets you specify the node version to install but it can’t be a dynamically acquired value. You either have to hardcode it or interpolate the value.
  • GitHub Actions Is Down
    5 projects | | 13 Jun 2022
    This is hitting workflows that use caching [1][2].

    - [1]

    - [2]

    As of now (11:28 UTC) the status page has been updated.

  • Getting started with GitHub Actions and workflows
    4 projects | | 3 Apr 2022
    You can also use the setup-node action to configure any Node.js version you like to use:
  • Nick Fury Comes to the Console via Github Actions
    8 projects | | 7 Feb 2022
    This YAML is pretty straightforward. We are only going to run this on the Ubuntu VM, and only for version NodeJS 10.x. Therefore, we do not need the matrix variables that we declared in the previous YAML file. We make use of two actions provided by GitHub, setup-node and checkout. In the third step, we run yarn build – a custom command that we registered in our package.json file. The last step, we use the npm-publish action provided by JS-DevTools. This has an input parameter called token. The token is the value that NPM gives you as an authorization key. Notice that this has the variable syntax that we encountered earlier.
  • Use NodeJS v16 as runtime for JavaScript actions
    5 projects | | 29 Dec 2021
    If you use actions/setup-node to specify the version of NodeJS, you need to update the node-version config in the workflow definitions. Or if you have a configuration file like .node-version and .nvmrc, you can use the node-version-file config supported from v2.5.0.
  • Semantic release to npm and/or ghcr without any tooling
    21 projects | | 7 Dec 2021
    actions/[email protected] - we use it to set the node version to 16
  • 🤷‍♂️ How to build and deploy angular application to surge using github actions
    2 projects | | 24 Oct 2021
    Read it here
  • A note from our sponsor - SonarQube | 27 Sep 2022
    Your projects are multi-language. So is SonarQube analysis. Find Bugs, Vulnerabilities, Security Hotspots, and Code Smells so you can release quality code every time. Get started analyzing your projects today for free. Learn more →


Basic setup-node repo stats
5 days ago

actions/setup-node is an open source project licensed under MIT License which is an OSI approved license.

Static code analysis for 29 languages.
Your projects are multi-language. So is SonarQube analysis. Find Bugs, Vulnerabilities, Security Hotspots, and Code Smells so you can release quality code every time. Get started analyzing your projects today for free.
Find remote jobs at our new job board There are 5 new remote jobs listed recently.
Are you hiring? Post a new remote job listing for free.