ESLint Configuration Problem: Local Development vs. Vercel Deployment

Support Bug Reports
1

:lady_beetle: Clear description of the bug:

ESLint errors that appear during Vercel deployment are not shown in the Cursor editor despite being detectable when running ESLint from the command line.

:counterclockwise_arrows_button: How to reproduce the bug:

  1. Create a Next.js project using ESLint flat config (eslint.config.mjs)

  2. Add specific ESLint rules (like @typescript-eslint/ban-ts-comment)

  3. Create code with violations of these rules (e.g., using @ts-ignore comments)

  4. Open the project in Cursor - no error highlighting appears

  5. When running the same code through eslint via terminal or deploying to Vercel, errors are correctly reported

:laptop: OS and Cursor version:

MacOS
Sequoia 15.4.1.,

Cursor
Version: 0.49.6 (Universal)
VSCode Version: 1.96.2
Commit: 0781e811de386a0c5bcb07ceb259df8ff8246a50
Date: 2025-04-25T04:39:09.213Z (1 wk ago)

Eslint Extension
dbaeumer.vscode-eslint
Version: 3.0.13

:prohibited: Does this issue stop you from using Cursor?:

It causes a disconnect between local development (where errors aren’t shown) and deployment (where builds fail due to ESLint errors), making it difficult to develop with confidence.

Very annoying tbh…

2

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.