Fix issue with importing CheckBoxTree component#9973
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
WalkthroughWebpack configuration is updated to explicitly alias ChangesWebpack Alias Configuration
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ 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 |
Resolves issue #9972
What does this PR do?
The react-checkbox-tree v2 release added "type": "module" to its package.json, which made webpack treat its UMD bundle (lib/index.js) as ESM and ignore the module.exports assignment. This means that importing the component yielded undefined and crashed the tree views. Aliasing the package to its true ESM entry (lib/index.esm.js) makes webpack read the proper export statements and restores the component.
Summary of changes
add forced routing to underlying esm module declaration when importing from
react-checkbox-treeSummary by CodeRabbit