Only mangling characteristics one bring about an underscore was a good heuristic as normal JS code does not normally have identifiers like that. If you wish to prevent mangling labels such as for instance __defineGetter__ you can contemplate using a far more state-of-the-art typical phrase instance [^_]_$ (i.elizabeth. must bring about a non-underscore followed closely by an emphasize).
That is a special setting rather than getting a portion of the minify means since it is a harmful conversion process that does not functions to the arbitrary JavaScript code. It just functions if your given regular phrase suits all of the newest characteristics that you like mangled and won’t fits people of one’s services that you do not wanted mangled. In addition, it simply functions if you do not less than any things site a beneficial mangled assets indirectly. Such, it indicates you cannot explore obj[prop] to reference property in which prop are a series which has brand new assets name. Specifically another sentence structure constructs would be the only of these qualified to receive possessions mangling:
While using this feature, remember that possessions brands are just continuously mangled in this just one esbuild API call yet not across the esbuild API calls. For each and every esbuild API phone call do an independent assets mangling procedure therefore productivity data files generated by a couple of additional API calls parece, that’ll result in the resulting password to behave incorrectly.
#Quoted qualities
By default, esbuild doesn’t modify the contents of string literals. This means you can avoid property mangling for an individual property by quoting it as a string. However, you must consistently use quotes or no quotes for a given property everywhere for this to work. For example, print(< foo_:>.foo_) will be mangled into print(< a:>.a) while print(< 'foo_':>[‘foo_’]) will not be mangled.
If you like to own esbuild to help you including mangle the fresh new content material of string literals, you could clearly enable that behavior such as this:
#Stopping renaming
If you need to help you exclude particular qualities of mangling, you could put aside all of them with an extra form. Instance, so it spends the standard expression ^__.*__$ so you can set-aside most of the services you to initiate and you may stop which have a few underscores, like __foo__ :
#Persisting renaming behavior
Advanced usage of the home mangling ability relates to space new mapping of new title to help you mangled term in a chronic cache. When let, most of the mangled property renamings is recorded about cache in the very first create. Next stimulates reuse the fresh renamings kept in new cache and you can create most renamings the recently-added qualities. This has several effects:
New cache functions as a summary of all of the functions which were mangled. You’ll check always it to see if you will find people unforeseen possessions renamings.
You could eliminate mangling having personal properties by mode the fresh rebranded value in order to not the case instead of to a sequence. This will be Wilmington escort just as the set-aside props setting however, to the a great per-possessions basis.
You might be certain that uniform renaming ranging from produces (age.g. a central-bond file and you can an internet staff, otherwise a collection and you will a plugin). As opposed to this feature, each generate should do a separate renaming operation as well as the mangled assets brands probably would not be uniform.
Whenever we wanted customRenaming_ becoming renamed to cR_ so we do not want disabledRenaming_ become renamed after all, we could solution the following mangle cache JSON so you can esbuild:
#Metafile
That one tells esbuild to produce certain metadata concerning the make when you look at the JSON style. The following example throws brand new metadata for the a document called meta.json :
This data may then be examined of the other products. For example, package friend can also be consume esbuild’s metadata format and you can creates a good treemap visualization of one’s segments on your package and how much room each one uses up.