-
Notifications
You must be signed in to change notification settings - Fork 457
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: node16 moduleResolution no longer works since 29.2.4 #4552
Comments
Hi, we reverted the change because it caused breaking change. We will introduce a temporarily flag to support this. A suggested flag name is Duplicated with #4198 |
Hi @ahnpnl, |
* feat: nx migrate and angular update * feat: turn off no-unused-expressions * fix: imports formatting in app.module.ts * feat: update mongodb-memory-server, ical-generator and reflect-metadata * fix: use NodeNext moduleResolution * fix(ci): Node version 22 * revert: upgrade mean-stream/nestx * feat: upgrade @mean-stream/nestx * fix: module NodeNext in tsconfig * feat: pnpm 9.12.0 * feat: NodeNext for tsconfig.spec.json * test: Revert ts-jest to 29.2.3 See: kulshekhar/ts-jest#4198 See: kulshekhar/ts-jest#4552 --------- Co-authored-by: Adrian Kunz <[email protected]>
@skrtheboss, how did you solve it? I'm facing the same problem, I've tried the solutions described on the issue mentioned above but nothing worked. I'm at: |
Version
29.2.5
Steps to reproduce
pnpm install
pnpm nx run eslint-rules:test --skip-nx-cache --no-cache
Expected behavior
git checkout fix/ts-jest-29-2-3
orgit checkout fix/ts-jest-29-1-0
pnpm install
pnpm nx run eslint-rules:test --skip-nx-cache --no-cache
Actual behavior
Tests fail since exports field of
@typescript-eslint/utils
package is not taken into consideration while resolution is performedDebug log
Content is too long.
Additional context
As far as I can tell, the commit that breaks this is 70b9530.
Environment
The text was updated successfully, but these errors were encountered: