Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🛠 Repo: Windows fails to run npm test #5220

Closed
5 tasks done
mark-wiemer opened this issue Sep 29, 2024 · 0 comments · Fixed by #5219
Closed
5 tasks done

🛠 Repo: Windows fails to run npm test #5220

mark-wiemer opened this issue Sep 29, 2024 · 0 comments · Fixed by #5219
Labels
area: repository tooling concerning ease of contribution status: in triage a maintainer should (re-)triage (review) this issue

Comments

@mark-wiemer
Copy link
Contributor

Tooling Suggestion Checklist

Overview

When installing on Windows, npm test gives the following error:

~/repos/mocha (main)
$ npm test

> mocha@10.7.3 test
> run-s lint test-node test-browser

... cut for GitHub ...

> mocha@10.7.3 lint:markdown
> markdownlint '*.md' 'docs/**/*.md' '.github/*.md' 'lib/**/*.md' 'test/**/*.md' 'example/**/*.md' -i CHANGELOG.md

Usage: markdownlint [options] <files|directories|globs>

MarkdownLint Command Line Interface

Options:
  -V, --version                               output the version number
... cut for GitHub ...
  -h, --help                                  display help for command

Oops! Something went wrong! :(

ESLint: 8.56.0

No files matching the pattern "'bin/*'" were found.
Please check for typing mistakes in the pattern.

ERROR: "lint:code" exited with 2.
ERROR: "lint" exited with 1.

This is because of the single quotes. Removing them resolves the issue, but it's unclear if that affects other OS-es

Additional Info

No response

@mark-wiemer mark-wiemer added area: repository tooling concerning ease of contribution status: in triage a maintainer should (re-)triage (review) this issue labels Sep 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: repository tooling concerning ease of contribution status: in triage a maintainer should (re-)triage (review) this issue
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant