Bug: Error highlight doesn't work on vscode

[shifoc]

this is an example of the project I have

https://stackblitz.com/edit/vitejs-vite-tnwys5ak?file=src%2Fmain.tsx

[dbaeumer]

How would I reproduce this in VS Code? Can you please provide me with a GitHub repository I can clone with a minimal setup that demos this.

[shifoc]

https://github.com/shifoc/vite-eslint

[dbaeumer]

Here is what I see after cloning the repository

Is there anything error releated in the ESLint output channel

[shifoc]

Nothing is highlighted for me, it looks to be working for you

…

On Fri, Mar 14, 2025, 9:08 AM Dirk Bäumer ***@***.***> wrote: Here is what I see after cloning the repository image.png (view on web) <https://github.com/user-attachments/assets/7686ccd1-121d-4bdf-8725-bdebf4dc550f> Is there anything error releated in the ESLint output channel — Reply to this email directly, view it on GitHub <#1992 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AH2MHX7E45BRDKVV6AYHKJL2UJ56VAVCNFSM6AAAAABY6AKK36VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMRTHAZDMOBZGM> . You are receiving this because you authored the thread.Message ID: ***@***.***> [image: dbaeumer]*dbaeumer* left a comment (microsoft/vscode-eslint#1992) <#1992 (comment)> Here is what I see after cloning the repository image.png (view on web) <https://github.com/user-attachments/assets/7686ccd1-121d-4bdf-8725-bdebf4dc550f> Is there anything error releated in the ESLint output channel — Reply to this email directly, view it on GitHub <#1992 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AH2MHX7E45BRDKVV6AYHKJL2UJ56VAVCNFSM6AAAAABY6AKK36VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMRTHAZDMOBZGM> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[dbaeumer]

Is there anything in the ESLint output channel?

[skitscha]

@dbaeumer Nothing is highlighting for me either and I'm getting the error:

[Error - 2:47:58 PM] Error [ERR_INTERNAL_ASSERTION]: Code: ERR_MODULE_NOT_FOUND; The provided arguments length (2) does not match the required ones (3).
This is caused by either a bug in Node.js or incorrect usage of Node.js internals.
Please open an issue with this stack trace at https://github.com/nodejs/node/issues

    at assert (node:internal/assert:14:11)
    at getMessage (node:internal/errors:594:5)
    at new NodeError (node:internal/errors:471:20)
    at legacyMainResolve (node:internal/modules/esm/resolve:221:9)
    at packageResolve (node:internal/modules/esm/resolve:848:14)
    at moduleResolve (node:internal/modules/esm/resolve:934:18)
    at defaultResolve (node:internal/modules/esm/resolve:1176:11)
    at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:542:12)
    at ModuleLoader.resolve (node:internal/modules/esm/loader:510:25)
    at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:239:38)

[dbaeumer]

@skitscha this might be caused by a eslint plugin. Without being able to reproduce this via a GitHub repository I can clone that demos this in a minimal setup it is very hard to say what is going wrong.

[skitscha]

I reproduced that using the example project the other person posted.

[gyzerok]

For me no highlights are being displayed in the following repo: https://github.com/gyzerok/svelte-eslint-bug, even though npm run lint shows some errors.

ESLint output does not show any signs of errors.

[Info  - 16:07:21] ESLint server is starting.
[Info  - 16:07:21] ESLint server running in node v20.18.2
[Info  - 16:07:21] ESLint server is running.