c83f94cf8b
Readds `@next/next/no-assign-module-variable` ESLint rule that was inadvertently removed in #34335 during the resolution of many merge conflicts. This PR will get us back to a good / working state. I'll see if I can add a test to ensure all rule are accounted for in a separate PR. Fixes #34335. ## Bug - [x] Related issues linked using `fixes #number` - [x] Integration tests added - [x] Errors have helpful link attached, see `contributing.md` ## Documentation / Examples - [x] Make sure the linting passes by running `pnpm lint` - [x] The examples guidelines are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing.md#adding-examples)
366 B
366 B
No assign module variable
Prevent assignment to the
modulevariable.
Why This Error Occurred
A value is being assigned to the module variable. The module variable is already used and it is highly likely that assigning to this variable will cause errors.
Possible Ways to Fix It
Use a different variable name:
let myModule = {...}