The following example is a slight variation through the V3 spec instance.
Above you can view that a supply map can be an object containing that is literal of juicy information:
- Variation quantity that the origin map is situated off
- The file title for the code that is generatedYour minifed/combined manufacturing file)
- sourceRoot enables you to prepend the sources by having a folder structure – this is certainly additionally a place preserving strategy
- sources contains all of the file names which were combined
- names contains all names that are variable/method appear through your rule.
- Finally the mappings home is when the magic takes place Base64 that is using VLQ. The genuine room preserving is completed right right right here.
Base64 VLQ and keeping the supply map tiny
Initially the origin map spec had an extremely verbose production of the many mappings and triggered the sourcemap being about 10 times how big the generated rule. Version two paid down that by around 50 version and% three paid off it once again by another 50%, therefore for a 133kB file you get by having a
300kB supply map. Just how did they lessen the size while still keeping the mappings that are complex?