[react] Node 16->18, @sentry/webpack-plugin 2.4.0->2.15.0 #422
Conversation
This file contains 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
realkosty
force-pushed
the
react-upgrade-node-js-and-sentry-webpack-plugin
branch
from
21b11bd to
29d5bdc
Compare
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.
Google is deprecating Node 16 in App Engine Standard. This fixes the following deployment error:
Webpack plugin updated in an attempt to fix sourcemaps in non-production, turned out it was a different issue, kept because why not.
Testing
tested together with 2 other PRs in #417