Detect output format from Vite config, not importer format#3
Merged
Conversation
Changes module format detection from importer-based (was it ESM or CJS?) to output-based (what format is Vite building for?). This fixes the bug where CJS files importing native modules in an ESM build output cause "Cannot determine intended module format" errors. Also adds comprehensive test coverage and documentation about multi-format build limitations. 🤖 Generated with Claude Code Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Fix module format detection to use Vite output format instead of importer format. This prevents "Cannot determine intended module format" errors when CommonJS files import native modules in ESM builds.
Changes
rollupOptions.output.formatorlib.formatsin Vite configsyntheticNamedExportstotrue(equivalent to previous change)Test Coverage
All 162 tests pass, including new integration tests for multi-format builds.
🤖 Generated with Claude Code