Update source-map to version 0.8.0-beta.0 #1030
Closed
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
|
Sorry this got missed. We landed this change in #1164, so this should be fixed with the next release. |
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.
I've been having some issues with
webpackbundling the node version ofsource-mapwith the client-side bundle. Updating the version to0.8.0-beta.0seems to work wonders for me, so I thought I'd try my luck with a PR so that I can avoid using less ideal solutions such as installingnpm-force-resolutions.I would normally not use a beta-package, but
source-mapseems fairly unmaintained with the last update being 3 years ago. I have tested building anextjsproject with terser usingsource-map@0.8.0-beta.0, and everything seems to work fine.