fix(nextjs): Add sentry-cli existence check for enabling webpack plugin
#4311
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.
Our nextjs SDK uses
sentry-cli(by way ofSentryWebpackPluginand@sentry/cli) to upload sourcemaps. Because binaries (like thesentry-cliexecutable) need to be compiled differently for different OSs and architectures,@sentry/cliuses a post-install script to download the correct one as part of its install process, rather than ship with all possible binaries at once.Of course, this goes awry if the post-install script isn't run, which is exactly what happens when
@sentry/cliis installed with the--ignore-scriptsoption. The resulting missing binary then causes errors which bubble up to and through our SDK to the nextjs build process, which promptly crashes.This fixes that by checking to make sure they binary has been downloaded before enabling
SentryWebpackPlugin.Fixes getsentry/sentry-cli#1085.