why 'npm run lint'(next lint) doesn't find lint issues of the whole codebase

[ManabBala]

Summary

I know i have eslint issues which get caught in the build command. but simply running npx next lint doesn't show any.
Is this expected behaviour? then how am i supposed to run lint check for my whole codebase?
I am also qurious how next lint is ignoring files for lint checking(like node_modules)? I need to ignore a prisma client folder.

// https://www.prisma.io/docs/guides/nextjs
generator client {
  provider = "prisma-client-js"
  output   = "../src/generated/client"
}

No lint issue

npm run lint                                                                                                ✔  took 4s  at 12:16:33 

> neet-and-clear@0.1.0 lint
> next lint

✔ No ESLint warnings or errors

Shows lint issues

npm run build                                                                                            ✔  took 4s  at 12:16:53 

> neet-and-clear@0.1.0 build
> prettier --check . && next build

Checking formatting...
All matched files use Prettier code style!
   ▲ Next.js 15.2.5
   - Environments: .env.local, .env

   Creating an optimized production build ...
 ✓ Compiled successfully
   Linting and checking validity of types  ...Failed to compile.

./prisma/seed.ts:2:3
Type error: Module '"@prisma/client"' has no exported member 'ClassName'.

  1 | import {
> 2 |   ClassName,
    |   ^
  3 |   Difficulty,
  4 |   MainExamType,
  5 |   MCQType,
Next.js build worker exited with code: 1 and signal: null

// eslint.config.mjs

import { FlatCompat } from '@eslint/eslintrc';
import perfectionist from 'eslint-plugin-perfectionist';
import { dirname } from 'path';
import { fileURLToPath } from 'url';

const __filename = fileURLToPath(import.meta.url);
const __dirname = dirname(__filename);

const compat = new FlatCompat({
  baseDirectory: __dirname,
});

const eslintConfig = [
  ...compat.extends(
    'next/core-web-vitals',
    'next/typescript',
    'plugin:prettier/recommended'
  ),
  perfectionist.configs['recommended-natural'],
];

export default eslintConfig;

Example

No response

[ManabBala]

ignoring prisma client output folder for linting:

import { globalIgnores } from 'eslint/config';
// .....................................
const eslintConfig = [
  ...compat.extends(
    'next/core-web-vitals',
    'next/typescript',
    'plugin:prettier/recommended'
  ),
  globalIgnores(['./src/generated/']),
];

[icyJoseph]

Hi,

Type error: Module '"@prisma/client"' has no exported member 'ClassName'.

That's a TypeScript error IIRC. Not a lint issue.

[icyJoseph]

You can do, __NEXT_TEST_MODE=1 npm run build, and that'll print all of the TypeScript errors you have.

[icyJoseph]

Is ClassName really meant to be imported from @prisma/client? Is the model defined? or are we missing some generation step here?

[ManabBala]

Hi,

Type error: Module '"@prisma/client"' has no exported member 'ClassName'.

That's a TypeScript error IIRC. Not a lint issue.

Thanks, it was wroking all along. stupid me couldn't see the forest for the trees.
Atleast out of all this i figured out how to ignore prisma folder with modern eslint.js file.

And for checking for all the typescript error:
#14234 (comment)

[ManabBala]

Is ClassName really meant to be imported from @prisma/client? Is the model defined? or are we missing some generation step here?

acctually prisma now recomends using custom path for the prisma client generator which was previously set to the 'node_modules/prisma/something..' as default. I was just migrating to the new schema and needed to update the imports from @prisma/client to @/generated/client' according to:

generator client {
  provider = "prisma-client-js"
  output   = "../src/generated/client"
}