Better way to remove frontend map files #1380
Merged
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
HFO4
requested changes
Jul 7, 2022
…o avoid generating map files.
I'm done, please check. |
HFO4
approved these changes
Jul 12, 2022
|
Merged, Thanks! |
|
horayyyy! my first pull request has been merged! |
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.
Create-React-App uses the
GENERATE_SOURCEMAPvariable to control whether to generate map files, the default istrue.We can set it to
falseto avoid the generation of map files and the presence of map files in js files, which can avoid many warning events generated by the browser console because the map file cannot be found.