-
-
Notifications
You must be signed in to change notification settings - Fork 773
perf!: remove nodeModulesDirs
#3798
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
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
6625aad to
ebd447e
Compare
f1b95df to
63ee2d0
Compare
📝 WalkthroughWalkthroughThe PR removes the Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes
Pre-merge checks and finishing touches❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✨ Finishing touches
🧪 Generate unit tests (beta)
📜 Recent review detailsConfiguration used: CodeRabbit UI Review profile: CHILL Plan: Pro 📒 Files selected for processing (6)
💤 Files with no reviewable changes (3)
🧰 Additional context used🧠 Learnings (1)📚 Learning: 2025-12-03T19:09:13.905ZApplied to files:
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)
🔇 Additional comments (3)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
nodeModulesDirsnodeModulesDirs
We were adding several
node_moduledirs (including workspace) to all resolutions, a requirement inherited from Nuxt to allow modules with non-hoisted dependencies to work.Removing extra
node_modulescan significantly help to reduce resolution times and also avoid wrong behaviors like picking dependencies from directories outside.The config is removed altogether. Implicit resolutions only happen from
rootDir