ESlint not working in vscodium same way as eslint in visual studio code

[ivanafanasyeu]

Describe the bug
ESlint not working

Please confirm that this problem is VSCodium-specific

• This bug doesn't happen if I use Microsoft's Visual Studio Code. It only happens in VSCodium.

Please confirm that the issue/resolution isn't already documented

• I checked the Docs page and the Troubleshooting page and my issue is not mentioned there.

To Reproduce
Steps to reproduce the behavior:

1. any ts files or tsx
2. have eslint configuration in the project
3. have installed eslint and prettier dependecies
4. visual studio code shows and highlights error, while vscodium doesn't

Expected behavior
behave same as visual studio code

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: Mac OS
• Architecture arm, m1
• Version 15.6.1
• App Manager homebrew

Additional context
Add any other context about the problem here.

[daiyam]

What the logs? Menu View/Output then ESLint.

[ivanafanasyeu]

What the logs? Menu View/Output then ESLint.

[Info  - 10:33:27] ESLint library loaded from: /Users/user/dev/company/app-frontend/node_modules/.pnpm/eslint@9.38.0_jiti@2.6.1/node_modules/eslint/lib/api.js
[Error - 10:33:28] Calculating config file for file:///Users/user/dev/company/app-frontend/apps/appname/src/pages/entityParent/%5Bid%5D/entityChild/entityChild-form/action.spec.ts) failed.
TypeError: Unexpected array.
    at flatTraverse (/Users/user/dev/company/app-frontend/node_modules/.pnpm/@eslint+config-array@0.21.1/node_modules/@eslint/config-array/dist/cjs/index.cjs:567:12)
    at flatTraverse.next (<anonymous>)
    at normalize (/Users/user/dev/company/app-frontend/node_modules/.pnpm/@eslint+config-array@0.21.1/node_modules/@eslint/config-array/dist/cjs/index.cjs:587:19)
    at async FlatConfigArray.normalize (/Users/user/dev/company/app-frontend/node_modules/.pnpm/@eslint+config-array@0.21.1/node_modules/@eslint/config-array/dist/cjs/index.cjs:1089:30)
    at async ConfigLoader.calculateConfigArray (/Users/user/dev/company/app-frontend/node_modules/.pnpm/eslint@9.38.0_jiti@2.6.1/node_modules/eslint/lib/config/config-loader.js:663:3)
    at async #calculateConfigArray (/Users/user/dev/company/app-frontend/node_modules/.pnpm/eslint@9.38.0_jiti@2.6.1/node_modules/eslint/lib/config/config-loader.js:743:23)
    at async ESLint.calculateConfigForFile (/Users/user/dev/company/app-frontend/node_modules/.pnpm/eslint@9.38.0_jiti@2.6.1/node_modules/eslint/lib/eslint/eslint.js:1283:4)
    at async /Users/user/.vscode-oss/extensions/dbaeumer.vscode-eslint-2.4.4-universal/server/out/eslintServer.js:1:22546
    at async Object.E [as withClass] (/Users/user/.vscode-oss/extensions/dbaeumer.vscode-eslint-2.4.4-universal/server/out/eslintServer.js:1:19114)
    at async T.then.g.validate (/Users/user/.vscode-oss/extensions/dbaeumer.vscode-eslint-2.4.4-universal/server/out/eslintServer.js:1:22506)

but having same logs in vscode as well, and there is working and highlighting

[daiyam]

Ok, I think it mostly due to microsoft/vscode-eslint#2050
On OpenVSX, it's still the 3.0.16 while it should have the 3.0.19 available.
I've made on issue on OpenVSX: eclipse/openvsx#1404

[daiyam]

Move to EclipseFdn/publish-extensions#1041