Skip to content

Commit

Permalink
chore: use current LTS node version adn add to ci tests
Browse files Browse the repository at this point in the history
  • Loading branch information
ernscht committed Oct 29, 2021
1 parent b79a546 commit af5279c
Show file tree
Hide file tree
Showing 3 changed files with 6 additions and 6 deletions.
2 changes: 1 addition & 1 deletion .github/workflows/ci.yml
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ jobs:
name: Test - ${{ matrix.platform }} - Node v${{ matrix.node-version }}
strategy:
matrix:
node-version: [10.x, 12.x, 14.x]
node-version: [10.x, 12.x, 14.x, 16.x]
platform: [ubuntu-latest, windows-latest]
runs-on: ${{ matrix.platform }}
steps:
Expand Down
2 changes: 1 addition & 1 deletion .node-version
Original file line number Diff line number Diff line change
@@ -1 +1 @@
14.17.5
16.13.0
8 changes: 4 additions & 4 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,8 +18,8 @@ Feel free to use env-linter in any way that makes sense for your project. Here i

```json
{
"postinstall": "env-linter -s -se -d -vs 'node=14.x.x,npm=7.x.x'",
"prestart": "env-linter -h -vs 'node=14.x.x,npm=7.x.x'",
"postinstall": "env-linter -s -se -d -vs 'node=16.x.x,npm=8.x.x'",
"prestart": "env-linter -h -vs 'node=16.x.x,npm=8.x.x'",
"lint-staged": {
"**/package.json": ["env-linter -s -d"]
}
Expand All @@ -34,7 +34,7 @@ You can skip all env-linter checks by using the environment variable `ENV_LINTER
const { api } = require('env-linter');

await api({
versions: 'node=14.x.x,npm=7.x.x',
versions: 'node=16.x.x,npm=8.x.x',
hooksInstalled: true,
saveExact: true,
dependenciesExactVersion: true,
Expand All @@ -48,7 +48,7 @@ await api({
### -vs, --versions [string]

Checks the installed versions of global packages or programs like node, npm, yo, etc. against a required version.
For example calling `env-linter --versions 'node=14.x.x'` will ensure that version 14 of node is being used. Multiple versions can be checked by separating them with a comma (eg. `--versions 'node=14.x.x,npm=7.x.x,yo=4.x.x'`).
For example calling `env-linter --versions 'node=16.x.x'` will ensure that version 16 of node is being used. Multiple versions can be checked by separating them with a comma (eg. `--versions 'node=16.x.x,npm=8.x.x,yo=4.x.x'`).
env-linter will stop any further process-execution if a package or program does not satisfy the required version.

Calling env-linter with `--versions` but without any arguments will compare the installed node-version with the node-version from the `.node-version` file.
Expand Down

0 comments on commit af5279c

Please sign in to comment.