fix: module resolution #252
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Improves module resolution handling across the framework with better error recovery and support for missing file extensions.
This fix enhances reliability when resolving modules, particularly when handling packages with complex export configurations or missing file extensions. The fallback mechanism ensures that imports work correctly even when the exact specifier isn't immediately resolvable by Node.js.
Adds
oxc-resolveras a module resolver in case of externalized dependencies when running in development mode.Adds a new example that depends on
react-syntax-highlighterto test its intricate module setup.Encapsulates internal Highlight.js usage to not interfere with user-installed Highlight.js.
Related to #251, but provides a generic solution that should apply to a wide range of packages using mixed CommonJS and ES module formats.