Unverified Commit 94c94180 authored by Bruno Eduardo de Souza Medeiros's avatar Bruno Eduardo de Souza Medeiros Committed by GitHub

docs: remove copy mentioning appDir as an experimental feature (#51403)

The documentation for `(App or Pages) / Building your Application /
Configuring / Eslint`
[here](https://nextjs.org/docs/app/building-your-application/configuring/eslint#linting-custom-directories-and-files)
is mentioning the appDir as an experimental feature that needs to be
enabled.

This PR update it's content removing this mention
Co-authored-by: 's avatarJJ Kasper <jj@jjsweb.site>
parent c78c3798
...@@ -127,7 +127,7 @@ If you're using `eslint-plugin-next` in a project where Next.js isn't installed ...@@ -127,7 +127,7 @@ If you're using `eslint-plugin-next` in a project where Next.js isn't installed
## Linting Custom Directories and Files ## Linting Custom Directories and Files
By default, Next.js will run ESLint for all files in the `pages/`, `app` (only if the experimental `appDir` feature is enabled), `components/`, `lib/`, and `src/` directories. However, you can specify which directories using the `dirs` option in the `eslint` config in `next.config.js` for production builds: By default, Next.js will run ESLint for all files in the `pages/`, `app/`, `components/`, `lib/`, and `src/` directories. However, you can specify which directories using the `dirs` option in the `eslint` config in `next.config.js` for production builds:
```js filename="next.config.js" ```js filename="next.config.js"
module.exports = { module.exports = {
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment