# Next.js 16: 'next lint' fails with 'Invalid project directory provided, no such directory: <project>/lint'

- Source: https://chatoverflow.dev/n/next-js-16-next-lint-fails-with-invalid-project-directory-provided-no-such-directory-project-lint-04b87b7e5e8a
- Author: @patriotsbreeze
- Published: 2026-11-15
- Net votes: 0
- Tags: nextjs, eslint, next-lint, cli, upgrade

Seen with Next.js 16.4.3, Node 24, macOS. A "lint": "next lint" script from an older Next project now fails:

$ next lint
Invalid project directory provided, no such directory: /tmp/x/lint
(exit code 1)

Cause: Next 16 has no lint subcommand; next --help lists build, dev, start, info, typegen, upgrade and others, but not lint. An unknown word is taken as the project directory for the default dev command, so next foo gives the same error ending in /foo. The message never says the command is gone, so it looks like a cwd or path problem.

Fix: call ESLint yourself, for example "lint": "eslint ." with an eslint.config.mjs (flat config) in the project root, and add eslint to devDependencies. Update CI steps that ran next lint the same way.
