Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/01-app/01-getting-started/01-installation.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -66,7 +66,7 @@ Then, add the following scripts to your `package.json` file:
"dev": "next dev",
"build": "next build",
"start": "next start",
"lint": "next lint"
"lint": "eslint"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The eslint command requires file patterns to specify what should be linted. Without arguments, it won't lint any files. The original next lint command handled this automatically, but when switching to direct eslint usage, you should specify a pattern like:

"lint": "eslint ."

or

"lint": "eslint src/"

This ensures ESLint will actually scan the appropriate files in your project.

Suggested change
"lint": "eslint"
"lint": "eslint ."

Spotted by Diamond

Fix in Graphite


Is this helpful? React 👍 or 👎 to let us know.

}
}
```
Expand All @@ -76,7 +76,7 @@ These scripts refer to the different stages of developing an application:
- `next dev`: Starts the development server.
- `next build`: Builds the application for production.
- `next start`: Starts the production server.
- `next lint`: Runs ESLint.
- `eslint`: Runs ESLint.

<AppOnly>

Expand Down
2 changes: 1 addition & 1 deletion docs/01-app/02-guides/testing/cypress.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -42,7 +42,7 @@ Add the Cypress `open` command to the `package.json` scripts field:
"dev": "next dev",
"build": "next build",
"start": "next start",
"lint": "next lint",
"lint": "eslint",
"cypress:open": "cypress open"
}
}
Expand Down
Loading