fix: add default exports condition for pnpm v10 compatibility#279
fix: add default exports condition for pnpm v10 compatibility#279
Conversation
Fixes ERR_PACKAGE_PATH_NOT_EXPORTED when installing with pnpm v10. The exports field only had an "import" condition, causing CJS resolution to fail during `nuxt module add`.
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 21 minutes and 24 seconds. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
commit: |
1 participant
Summary
"default"fallback condition to thepackage.jsonexportsfield, fixingERR_PACKAGE_PATH_NOT_EXPORTEDwhen installing with pnpm v10Root cause
The
exportsfield only had an"import"condition. Whennuxt module addperforms a CJS-stylerequire.resolve()check after installation, pnpm v10's strict module resolution (which ignores themainfield whenexportsis present) fails because there's no matching CJS condition. Adding"default"provides a catch-all fallback that works for both ESM and CJS resolution.Closes #274