Open living180 opened 3 months ago
I can't seem to reproduce this unfortunately. What version of node and npm are you using?
I'm using the versions from the stable branch of Gentoo Linux:
% node --version
v20.11.0
% npm --version
10.2.4
Gentoo has multiple other versions of nodejs available that I could try if you think that would make a difference.
Something interesting for me. When I restarted my pre-commit environment I see this in my logs:
[INFO] Initializing environment for https://github.com/pre-commit/mirrors-eslint:eslint@v9.0.0-beta.1,@eslint/js@v9.0.0-beta.1,globals.
Maybe 9.0.0-beta.0 was yanked?
Nope, it's still there.
I downgraded to the oldest version of nodejs available in Gentoo:
% node --version
v18.17.1
% npm --version
9.6.7
then ran pre-commit clean
and still had the same issue.
Perhaps merge #1900 to see if the release candidate fixes things?
git commit --no-verify
can be a workaround.
When developing against the
main
branch of DjDT, I can no longer commit changes to JS files due to a failure in pre-commit. If I force a pre-commit run on the tip ofmain
without any changes, I get the following output:If I revert the recent eslint changes from 38d2eea5f8b57f70a4b5bdebd6bdeae8c395d822, pre-commit works without any problems.