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
The React Native build tools search through all dependencies and parse the package.json from each. When the package.json is not included in a dependencies
exports
, the build fails, and so currently svgr/webpack cannot be used with React Native.There's thread with a feature request for Node to have special treatment for package.json, but the Node team have stated this isn't likely to happen: nodejs/node#33460
There's an open PR for the React Native tools to add an attempt at a fallback to deal with this, but it's more of a workaround than an actual fix: react-native-community/cli#1648
The actual fix requires any used dependencies to either exclude the
exports
section in their package.json, or to list the package.json as an export. This also fixes #742Test plan
npm run build
).require("@svgr/webpack/package.json");
Without explicitly specifying the package.json in the exports, the
require
fails with:Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './package.json' is not defined by "exports"
.