Remove source-map from browser build #1571
Merged
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.
Since
path
is false in browsers build thesource-map
package is actually not in use*.This PR adds
"source-map": false
to thepackage.json
also added explicit protection for the existence of thesource-map
API's.Now if one will want to use postcss in browser and support source maps he will need to include
path
andsource-map
packagesThis will decreased the bundle size of postcss by ~27% (from 29KB to 21KB)
(*) There is only one feature that I wasn't sure what to do with related to
fromJSON
. It is using thePreviousMap
(no problem there) andPreviousMap
uses thesource-map
package and I wasn't sure how to fallback. It might be a super edge case for browsers.