eslint-action icon indicating copy to clipboard operation
eslint-action copied to clipboard

Unhelpful error when running action

Open daniel-vc opened this issue 4 years ago • 7 comments

Hi, I'm trying to use your linting action but even though i've followed your set up steps, and running eslint locally, I get the below message. Any ideas?

Screenshot 2020-03-11 at 16 16 44

daniel-vc avatar Mar 11 '20 16:03 daniel-vc

hey @daniel-vc

Looks like it's a problem with your tests themselves regarding promise chaining.

Just to clarify: does it reproduce locally?

stefanoeb avatar Mar 19 '20 09:03 stefanoeb

Hi, I have the same issue, and no, it is only in the actions. I don't have those messages locally. For me, it comes from your action! You can see it right here: https://github.com/Skript-MC/Swan/runs/533285405?check_suite_focus=true

noftaly avatar Mar 28 '20 11:03 noftaly

Hi there, I can confirm I'm getting the same warning.

gslama-akqa avatar Apr 30 '20 13:04 gslama-akqa

@stefanoeb

I also experienced this issue and found that it is caused by this issue https://npm.community/t/npm-ci-produces-a-tonn-of-excess-warnings-on-install/3261.

This can be fixed by upgrading the nodejs image used in the docker file. I tested using nodejs 12 (current LTS) and this issue went away. I Opened up #10 to help resolve the issue.

abmusse avatar May 14 '20 05:05 abmusse

I had to remove this action from the workflow due to the same error. I'll be watching this issue to verify it's fixed with proposed solution (node upgrade)

rdzak avatar Jun 02 '20 09:06 rdzak

I would actually recommend running ESLint without this action, because out of the box the ubuntu runtime of Github Action has everything we need now, like so:

name: CI
on: push
jobs:
  build:
    runs-on: ubuntu-latest
    steps:
    - uses: actions/checkout@v2
    - name: Install modules
      run: yarn
    - name: Lint
      run: eslint .

stefanoeb avatar Jun 07 '20 10:06 stefanoeb

Now in the end, all this action is doing is running eslint inside a docker container. I'd say that we would be better off just not using docker at all and run eslint inside the normal runtime (which I hope is regularly updated)

stefanoeb avatar Jun 07 '20 10:06 stefanoeb