-
-
Notifications
You must be signed in to change notification settings - Fork 35.1k
Closed
Description
Version
v22.3.0
Platform
Microsoft Windows NT 10.0.22631.0 x64
Subsystem
No response
What steps will reproduce the bug?
Honestly no idea. I uninstalled ESLint yesterday and decided to reinstalled it today. This error only showed up today. Even setting it up with config@latest gives out the same error.
How often does it reproduce? Is there a required condition?
I don't think there's a req condition.
What is the expected behavior? Why is that the expected behavior?
ESLint not giving out this error, like yesterday. Because it worked casually.
What do you see instead?
Error [ERR_INTERNAL_ASSERTION]: Code: ERR_MODULE_NOT_FOUND; The provided arguments length (2) does not match the required ones (3).
This is caused by either a bug in Node.js or incorrect usage of Node.js internals.
Please open an issue with this stack trace at https://github.com/nodejs/node/issues
at NodeError (node:internal/errors:406:5)
at assert (node:internal/assert:14:11)
at getMessage (node:internal/errors:452:5)
at new NodeError (node:internal/errors:380:21)
at legacyMainResolve (node:internal/modules/esm/resolve:195:9)
at packageResolve (node:internal/modules/esm/resolve:783:14)
at moduleResolve (node:internal/modules/esm/resolve:845:20)
at defaultResolve (node:internal/modules/esm/resolve:1050:11)
at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:383:12)
at ModuleLoader.resolve (node:internal/modules/esm/loader:352:25)Additional information
No response
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels