Skip to content

Migrate lint script for Next.js 16#19

Open
tongshu2023 wants to merge 1 commit into
Nutlope:mainfrom
tongshu2023:fix-next-16-eslint-lint
Open

Migrate lint script for Next.js 16#19
tongshu2023 wants to merge 1 commit into
Nutlope:mainfrom
tongshu2023:fix-next-16-eslint-lint

Conversation

@tongshu2023

Copy link
Copy Markdown

Summary:

  • Replace the removed Next.js lint command with the ESLint CLI.
  • Move the project to ESLint flat config for the existing Next.js 16 ESLint config package.
  • Upgrade ESLint to v9 to satisfy eslint-config-next 16 peer requirements.
  • Replace internal home-page anchor links in Header and Footer with Next Link so the migrated lint command passes.

Why:
The project uses Next.js 16, where next lint has been removed. Running the existing lint script currently treats lint as a project directory and fails before ESLint can run. eslint-config-next 16 also declares ESLint 9 as its peer requirement, while the project still had ESLint 8.

Verification:

  • .\node_modules\.bin\next.cmd lint fails with Invalid project directory provided, no such directory: ...\llamatutor\lint before this change.
  • .\node_modules\.bin\eslint.cmd . passes after this change.
  • git diff --check passed.

@vercel

vercel Bot commented Jun 4, 2026

Copy link
Copy Markdown
Contributor

@tongshu2023 is attempting to deploy a commit to the Together AI Team on Vercel.

A member of the Team first needs to authorize it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant