fix(eslint-plugin-reactotron): Fix ESLint Plugin CommonJS Export Compatibility #1578
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.
Please verify the following:
yarn build-and-test:localpassesREADME.md(or relevant documentation) has been updated with your changesDescribe your PR
Fixes: infinitered/ignite#2997
Problem
The eslint-plugin-reactotron v0.1.8 fails with "Definition for rule 'reactotron/no-tron-in-production' was not found". This affects all new Ignite CLI projects and any project using the ESLint plugin.
Root Cause
Migration from Rollup to react-native-builder-bob changed the CommonJS export format. Builder Bob outputs exports.default = plugin (standard Babel behavior), but ESLint expects the plugin to be available directly as the module export, not nested under .default.
Solution
Modified the source code export structure to improve CommonJS compatibility: