super-linter: Typescript Standard linting broken in v5.0.0

Describe the bug

I upgraded Super Linter from version 4.9.0 to version 5.0.0. Since then the TS Standard Linting fails. On each file it processes it prints the following error message:

------
ts-standard: Standard for TypeScript! (https://github.com/standard/ts-standard)
  /tmp/lint/bin/super-linter-ts-trouble.ts:0:0: Parsing error: ESLint was configured to run on `<tsconfigRootDir>/bin/super-linter-ts-trouble.ts` using `parserOptions.project`: /action/lib/.automation/tsconfig.json
However, that TSConfig does not include this file. Either:
- Change ESLint's list of included files to not include this file
- Change that TSConfig to include this file
- Create a new TSConfig that includes this file and include it in your parserOptions.project
See the typescript-eslint docs for more info: https://typescript-eslint.io/linting/troubleshooting#i-get-errors-telling-me-eslint-was-configured-to-run--however-that-tsconfig-does-not--none-of-those-tsconfigs-include-this-file (null)
------

Expected behavior

The hints on the referred url don’t work for me. If I run the linter 4.9.0, it complains, but the files are processed anyway:

Steps to Reproduce

git init
cdk init app --language=typescript
git add -A
git commit -m 'initial commit'
docker run -e RUN_LOCAL=true -e VALIDATE_TYPESCRIPT_STANDARD=true -v .:/tmp/lint github/super-linter:v5.0.0

If I run the linter 4.9.0, it complains, but the files are processed anyway:

docker run -e RUN_LOCAL=true -e VALIDATE_TYPESCRIPT_STANDARD=true -v .:/tmp/lint github/super-linter:v4.9.0

Do you have any idea or even a solution for this problem? Thanks in advance

About this issue

  • Original URL
  • State: closed
  • Created a year ago
  • Reactions: 1
  • Comments: 15 (9 by maintainers)

Commits related to this issue

Most upvoted comments

@agustindelmonti Unfortunately I don’t have an update yet. Fixing the docker issues are estimated as a large effort so this will likely take a while.

Ran into an issue testing this out because I’m on a arm based mac so I can’t create the docker image to test this out. Going to try to work on that problem and come back to this once unblocked. Open to alternatives if anyone had got any ideas.

Created a PR to see if I can remove type-checking by default. Testing that now to see if my change in fact does that and if it resolves the reproduced error.

I have been out the last several days so I have not finished looking at this yet. I have forked it and duplicated the issue so Thanks for posting that code repository. Next steps will be to try out some solutions to see what works.

You can test it out on: https://github.com/gmaiwald/super-linter-ts-trouble Hope this helps.