Compare commits

...

5 Commits

Author SHA1 Message Date
Karl Horky
6022bce106
Merge 6f485d0d11 into 40337cb8f7 2025-03-25 10:10:57 -05:00
fregante
40337cb8f7
Add support for indented eslint output (#1245) 2025-03-24 16:12:02 -05:00
Flo Edelmann
1ccdddc9b8
Make eslint-compact matcher compatible with Stylelint (#98) 2025-03-24 12:48:16 -05:00
Karl Horky
6f485d0d11
Add Caching Caveat note, add check-latest: true to examples 2025-03-06 17:00:28 +01:00
Karl Horky
f454ce2807
Add warning and caveat for NVM syntax 2024-07-27 13:49:33 +02:00
3 changed files with 12 additions and 7 deletions

View File

@ -4,7 +4,7 @@
"owner": "eslint-compact",
"pattern": [
{
"regexp": "^(.+):\\sline\\s(\\d+),\\scol\\s(\\d+),\\s(Error|Warning|Info)\\s-\\s(.+)\\s\\((.+)\\)$",
"regexp": "^(.+):\\sline\\s(\\d+),\\scol\\s(\\d+),\\s([Ee]rror|[Ww]arning|[Ii]nfo)\\s-\\s(.+)\\s\\((.+)\\)$",
"file": 1,
"line": 2,
"column": 3,

View File

@ -4,7 +4,7 @@
"owner": "eslint-stylish",
"pattern": [
{
"regexp": "^([^\\s].*)$",
"regexp": "^\\s*([^\\s].*)$",
"file": 1
},
{

View File

@ -87,6 +87,7 @@ steps:
- uses: actions/setup-node@v4
with:
node-version: 18
check-latest: true
- run: npm ci
- run: npm test
```
@ -103,12 +104,13 @@ The `node-version` input supports the Semantic Versioning Specification, for mor
Examples:
- Specific versions: `10.15`, `16.15.1` , `18.4.0`
- Version ranges (see **Caching Caveat** below)
- Major versions: `18`, `20`
- More specific versions: `10.15`, `16.15.1` , `18.4.0`
- NVM LTS syntax: `lts/erbium`, `lts/fermium`, `lts/*`, `lts/-n`
- Latest release: `*` or `latest`/`current`/`node`
**Note:** Like the other values, `*` will get the latest [locally-cached Node.js version](https://github.com/actions/runner-images/blob/main/images/ubuntu/Ubuntu2204-Readme.md#nodejs), or the latest version from [actions/node-versions](https://github.com/actions/node-versions/blob/main/versions-manifest.json), depending on the [`check-latest`](docs/advanced-usage.md#check-latest-version) input.
**Caching Caveat:** Version ranges may be cached for an indefinite time without the `check-latest: true` option - they may be stale for [durations up to 1 month](https://github.com/actions/setup-node/issues/1236#issuecomment-2704188519)
`current`/`latest`/`node` always resolve to the latest [dist version](https://nodejs.org/dist/index.json).
That version is then downloaded from actions/node-versions if possible, or directly from Node.js if not.
@ -136,6 +138,7 @@ steps:
- uses: actions/setup-node@v4
with:
node-version: 20
check-latest: true
cache: 'npm'
- run: npm ci
- run: npm test
@ -149,6 +152,7 @@ steps:
- uses: actions/setup-node@v4
with:
node-version: 20
check-latest: true
cache: 'npm'
cache-dependency-path: subdir/package-lock.json
- run: npm ci
@ -171,6 +175,7 @@ jobs:
uses: actions/setup-node@v4
with:
node-version: ${{ matrix.node }}
check-latest: true
- run: npm ci
- run: npm test
```