The gradle plugin assumes that the local node_modules for an Android project are always in the same location, which works fine for the default case. However, if a user puts them in a different directory then the plugin would not be able to run the bugsnag-source-maps command, or find bugsnag-android’s AARs bundled in the react-native node_module.
This changeset supports this scenario by exposing a configuration option on the bugsnag plugin extension which allows users to override the default location of the node_modules.
Testing
Added E2E scenario to verify that setting the nodeModulesDir to a custom location works.
Goal
The gradle plugin assumes that the local
node_modulesfor an Android project are always in the same location, which works fine for the default case. However, if a user puts them in a different directory then the plugin would not be able to run thebugsnag-source-mapscommand, or find bugsnag-android’s AARs bundled in the react-native node_module.This changeset supports this scenario by exposing a configuration option on the bugsnag plugin extension which allows users to override the default location of the node_modules.
Testing
Added E2E scenario to verify that setting the
nodeModulesDirto a custom location works.