You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
> @npmcli/template-oss@4.18.0 lint
> eslint "**/*.js"
Oops! Something went wrong! :(
ESLint: 8.49.0
Error: ESLint configuration in test\apply\tap-testdir-files-snapshots-turn-off-specific-files\.eslintrc.yml is invalid:
- Property "" is the wrong type (expected object but got `"exists"`).
at ConfigValidator.validateConfigSchema (C:\Users\dan\Source\template-oss\node_modules\@eslint\eslintrc\dist\eslintrc.cjs:2168:19)
at ConfigArrayFactory._normalizeConfigData (C:\Users\dan\Source\template-oss\node_modules\@eslint\eslintrc\dist\eslintrc.cjs:3010:19)
at ConfigArrayFactory.loadInDirectory (C:\Users\dan\Source\template-oss\node_modules\@eslint\eslintrc\dist\eslintrc.cjs:2878:33)
at CascadingConfigArrayFactory._loadConfigInAncestors (C:\Users\dan\Source\template-oss\node_modules\@eslint\eslintrc\dist\eslintrc.cjs:3860:46)
at CascadingConfigArrayFactory.getConfigArrayForFile (C:\Users\dan\Source\template-oss\node_modules\@eslint\eslintrc\dist\eslintrc.cjs:3781:18)
at FileEnumerator._iterateFilesRecursive (C:\Users\dan\Source\template-oss\node_modules\eslint\lib\cli-engine\file-enumerator.js:450:49)
at _iterateFilesRecursive.next (<anonymous>)
at FileEnumerator._iterateFilesRecursive (C:\Users\dan\Source\template-oss\node_modules\eslint\lib\cli-engine\file-enumerator.js:497:33)
at _iterateFilesRecursive.next (<anonymous>)
at FileEnumerator._iterateFilesRecursive (C:\Users\dan\Source\template-oss\node_modules\eslint\lib\cli-engine\file-enumerator.js:497:33)
Expected Behavior
No response
Steps To Reproduce
In this environment...
With this config...
Run '...'
See error...
Environment
npm:
Node:
OS: Windows 11
platform:
The text was updated successfully, but these errors were encountered:
Running tests causes a lot of file churn. Although (usually) ephemeral,
these files cause high CPU usage and can make developer tools difficult
to use. These files also make linting fail.
Now the files will be ignored by git and by eslint.
## References
Fixes#348Fixes#359
This is a rebase of #350 since it had yet another conflict.
---------
Authored-by: Dan <DanOfTheRoses@gmail.com>
Is there an existing issue for this?
Current Behavior
npm run lint
Expected Behavior
No response
Steps To Reproduce
Environment
The text was updated successfully, but these errors were encountered: