fix: source_map_support: false disables source maps
#5989
Conversation
This file contains hidden or 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
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.
Hey @Unitech
disable_source_map_support: true, this will correctly disable source mapssource_map_support: false, this has no effect - source maps will still be detected.source_map_support: falsecorrectly disables source maps, so that it has the same behavior as settingdisable_source_map_support: truepm2-runtime#5003. I had similar issues getting Sentry to work correctly because pm2 was detecting source map files even though I had already setsource_map_support: false. This fix prevents that issue from happening again with other people using pm2 with ecosystem files.