maybe also a rule for where global css imports are allowed?

I would love to work on this @leerob. Can you please assign this to me?

@Patil2099 Which one specifically would you like to work on first?

@leerob I'll work on Using document or other browser APIs outside of useEffect

Just to confirm, are you looking to include these interfaces as well https://developer.mozilla.org/en-US/docs/Web/API#interfaces ?

Forgetting to await an async function inside an API route, works fine locally but does out of band work which will cause issues if there’s multiple requests.

I'm not sure how you were planning on detecting API/promises, but if it is typescript based it can probably either defer to this existing rule or extend it somehow if necessary:
https://github.com/typescript-eslint/typescript-eslint/blob/v4.28.3/packages/eslint-plugin/docs/rules/no-floating-promises.md

Not sure if its a super-common issue, but an integrated ESLint rule to catch #27134 would be nice to have.

I'll submit a PR for this soon! PR here: #27179

Another one: throw an error if using fs or other node packages on the client side.

https://twitter.com/leeerob/status/1417818534026022912?s=21

File name casing (e.g. myFile.js vs MyFile.js). This could potentially be solved with linting if import statement diffs from the actual file path? Not sure.

We enforce to be kebab-case file name, no more case sensitive vs not issues. Worth reading a bit more here: https://github.com/straw-hat-team/adr/tree/master/adrs/3122196229

I think the problem begins by adopting things that cause more harm than good in the long run with little to no value IMO. I don't remember anymore how many times I had to fix CI by telling people to fix the casing situation and reminds them to use git mv

I would discourage the usage of camelCase or PascalCase and stick to kebab-case as NodeJS used to be until we diverged.

:2cents:

@yordis I'm not saying Next.js ESLint should have a preference on how you do casing – that's a bit to stylistic to determine at the framework level. I'm talking about when you import a file MyFile.js but the actual file name is cased different, like myFile.js.

Oh like, check for those errors?! Sorry, I misunderstood

Hello everyone! I'm Keen and I just joined Google's WebSDK (Aurora) team this week 😃
I'd like to tackle the third item in Lee's issue as a starter project:

Forgetting to await an async function inside an API route, works fine locally but does out of band work which will cause issues if there’s multiple requests.

Please let me know if you have any concerns, otherwise I'll get started!

hi all! @leerob I would like to try to implement this rule:
Another one: throw an error if using fs or other node packages on the client side.

Just to clarify, the rule should not allow using node built-in modules inside the react components, but will allow inside the other files like ex. utils, API routes and inside the data fetching functionsgetStaticProps, getStaticPaths, getServerSideProps is that correct?