Balázs Orbán e7b6b1939d fix: don't use optional chaining in ESLint rule (#38534) ... Fixes #38530 Should we consider adding a build-step to lint rules to be able to use TS/modern JS? ## Bug - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Errors have helpful link attached, see `contributing.md` ## Feature - [ ] Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Documentation added - [ ] Telemetry added. In case of a feature if it's used or not. - [ ] Errors have helpful link attached, see `contributing.md` ## Documentation / Examples - [ ] Make sure the linting passes by running `pnpm lint` - [ ] The examples guidelines are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing.md#adding-examples)		2022-07-11 22:59:33 +00:00
..
rules	fix: don't use optional chaining in ESLint rule (#38534)	2022-07-11 22:59:33 +00:00
utils	Fix typos (#35683)	2022-03-28 22:53:51 -05:00
index.js	Readds missing @next/next/no-assign-module-variable ESLint rule. (#38134)	2022-06-29 02:54:47 +00:00