-
-
Notifications
You must be signed in to change notification settings - Fork 25
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
switch-exhaustiveness-check
config mismatch?
#83
Comments
I resolved with this in the project's package.json (not the config) "overrides": {
"@typescript-eslint/eslint-plugin": "7.0.2"
}, |
This was referenced Feb 24, 2024
It started resolving correctly after mocking around 🤷♂️ I had already Mysteries of npm |
Reopening since this still happens. It had disappeared because this sequence updates the lockfile, fixing the issue (presumably until a future update of the lockfile):
|
fregante
added a commit
to pixiebrix/pixiebrix-extension
that referenced
this issue
Feb 25, 2024
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have the latest dependencies in
eslint-config-pixiebrix
and I'm seeing this issue, but I don't understand why. The peer deps are not being resolved correctly according to npm:The text was updated successfully, but these errors were encountered: