Map Preprocessed Code to Provider Code For You Personally
Maintain your client-side rule debuggable and readable even with you have combined, minified or compiled it. Utilize supply maps to map your source rule to your put together rule.
Get started doing preprocessors
Work with a supported preprocessor
You should utilize a minifier that is with the capacity of creating maps that are source. For the many popular options, see our preprocessor help area. For the extensive view, understand supply maps: languages, tools as well as other information wiki page.
The next types of preprocessors can be utilized in combination with Source Maps:
Supply Maps in DevTools Sources panel
Source Maps from preprocessors cause DevTools to load your original files along with your ones that are minified. Afterward you use the originals to create breakpoints and move through rule. Meanwhile, Chrome is obviously operating your minified rule. This provides you the impression of owning a development web web site in manufacturing.
Enable Source Maps in settings
Debugging with Source Maps
Whenever debugging your rule and Source Maps enabled, Source Maps will show in 2 places:
@sourceURL and displayName
The@sourceURL allows you to make development much easier when working with evals while not part of the source Map spec. This helper appears quite similar in to the //# sourceMappingURL property and it is really mentioned into the Source Map V3 specifications.
By like the after special comment in your rule, which is evaled, you can easily name evals and inline scripts and designs so they really appear as more rational names in your DevTools.
Navigate to the demo, then: