When I run eslint on my workspace that has an app that uses Next.js, I get so many errors and warnings coming from the .next folder.
Expected Behavior
.next folder should be ignored by eslint.
Steps to Reproduce
Have a workspace using Nx 14.5.4 with a Next.js application. I'm not sure if this happens to newly created workspaces, it happened to me when updating from a previous version.
The migration did not set the .next folder to be ignored by eslint. I can see that the migration to 14.5.3 adds the .next folder to .gitignore, but it should set the folder to be ignored by eslint as well.
Environment
Node : 16.16.0
OS : darwin arm64
npm : 8.11.0
nx : 14.5.4
@nrwl/angular : Not Found
@nrwl/cypress : 14.5.4
@nrwl/detox : Not Found
@nrwl/devkit : 14.5.4
@nrwl/eslint-plugin-nx : 14.5.4
@nrwl/express : Not Found
@nrwl/jest : 14.5.4
@nrwl/js : 14.5.4
@nrwl/linter : 14.5.4
@nrwl/nest : 14.5.4
@nrwl/next : 14.5.4
@nrwl/node : 14.5.4
@nrwl/nx-cloud : Not Found
@nrwl/nx-plugin : Not Found
@nrwl/react : 14.5.4
@nrwl/react-native : Not Found
@nrwl/schematics : Not Found
@nrwl/storybook : 14.5.4
@nrwl/web : 14.5.4
@nrwl/workspace : 14.5.4
typescript : 4.7.4
---------------------------------------
Community plugins:
Current Behavior
When I run eslint on my workspace that has an app that uses Next.js, I get so many errors and warnings coming from the
.next
folder.Expected Behavior
.next
folder should be ignored by eslint.Steps to Reproduce
Have a workspace using Nx 14.5.4 with a Next.js application. I'm not sure if this happens to newly created workspaces, it happened to me when updating from a previous version.
The migration did not set the
.next
folder to be ignored by eslint. I can see that the migration to 14.5.3 adds the.next
folder to.gitignore
, but it should set the folder to be ignored by eslint as well.Environment