Move from custom eslint to Next11's eslint-plugin-next

[kalvinwang]

Description

Since we updated to Next 11.1, we now have the ability to make use of eslint-plugin-next and its default configuration to catch common issues with Next.js applications. However, following the documentation here, which is basically:

1. In package.json:

-    "lint": "eslint . --ext .ts,.tsx,.js,.jsx",
+    "lint": "next lint",

2. Adding the @next/eslint-plugin-next package
3. Adding plugin:plugin:@next/next/recommended to the list of extends in .eslintrc.js

Results in the following error while running yarn lint (aka next lint):

TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received undefined

Acceptance Criteria

• Make use of Next's new integrated eslint

[rocketnova]

@kalvinwang Thanks for finding this and making the ticket! Can you clarify the ticket description? I'm not sure what this portion of the description means:

Results in the following error while running yarn lint (aka next lint):
TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received undefined

Is this an example of what expected lint checking is? Or are you saying that you tried to follow the directions and ran into this error and therefore put the work on pause for now?