GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — GitHub - pkgjs/action: Github Actions tooling for testing Node.js packages

BranchesTags
Open more actions menu

Latest commit

 

History

138 Commits
138 Commits

Folders and files

NameName
Last commit message
Last commit date
.github
.github
 
 
docs
docs
 
 
.gitignore
.gitignore
 
 
.npmrc
.npmrc
 
 
CODE_OF_CONDUCT.md
CODE_OF_CONDUCT.md
 
 
CONTRIBUTING.md
CONTRIBUTING.md
 
 
LICENSE
LICENSE
 
 
README.md
README.md
 
 
eslint.config.js
eslint.config.js
 
 
package.json
package.json
 
 
renovate.json
renovate.json
 
 

Repository files navigation

pkgjs/action

Use the pkgjs/action workflow to automatically add new versions of Node.js to your test matrix.

Basic usage

  1. Define a miminum supported Node.js version in your package.json, e.g.
{
  "engines": {
    "node": "^16 || ^14 || ^12"
  }
}
  1. Create a file (e.g. ci.yaml) in your .github/workflows/ folder:
on:
  push:
    branches:
    - main
  pull_request:

jobs:
  test:
    uses: pkgjs/action/.github/workflows/node-test.yaml@v0
    with:
      upgrade-policy: lts           # optional

With the above configuration, a test matrix will be created with all the Node.js LTS versions starting from v12. In January, 2022, the above example would yield the following versions: 16, 14, 12 (LTS releases which will not be removed from the matrix), as well as 17 (current non-LTS release - will be removed from the matrix when the support ends).

By default, the test script will check out your repository, execute npm install and then execute an npm test using the latest Node.js version in every release line in the test matrix.

Further reading

  • See detailed documentation for alternative upgrade policies and other settings.
  • Read more about Node.js release support process.
  • Choosing the Node.js versions for your CI tests (hint: use LTS)

  • This repository is managed by the Package Maintenance Working Group, see Governance.
  • Code of Conduct
  • Contributing

About

Github Actions tooling for testing Node.js packages

Resources

Readme
MIT license

Code of conduct

Code of conduct

Contributing

Contributing

Security policy

Security policy
Activity
Custom properties

Stars

12 stars

Watchers

8 watching

Forks

3 forks
Report repository

Releases

Packages

Used by

Contributors

Languages

You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.