Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Loader versus Plugin?

See original GitHub issue

Is the main use of the loader to be able to choose which files to obfuscate, whereas plugin obfuscates everything except explicitly excluded file names? Are there other uses? Or is there any way to exclude node_modules with the plugin?

Issue Analytics

State:
Created 3 years ago
Comments:6 (3 by maintainers)

Top GitHub Comments

2reactions

sanex3339commented, Feb 23, 2021

The loader runs for each file individually, whereas the plugin runs over the complete bundle.

0reactions

sanex3339commented, May 17, 2021

Obfuscator has an internal minimizer + simplifier (compact: true, simplify: true and identifierNamesGenerator: 'mangled' options. It’s not as good as Terser but it’s ok.

Top Results From Across the Web

WebPack Loader vs Plugin - DEV Community ‍ ‍

Plugins work at bundle or chunk level and usually work at the end of the bundle generation process. · Plugins can deeply integrate...

Webpack Loaders and Plugins - Imran Sayed - Medium

In this blog, we will learn about what are loaders and plugins and how to use them with webpack. ... Loaders enable us...

Webpack explained simply – plugins, loaders and Babel

Work at the end or after of bundle generation; Plugins work at bundle level; Plugins have much more control over the bundle. Babel...

Learn Loaders and Plugins – Webpack 2 Deep Dive

Loaders handle file-specific processing like looking for all CSS files and running them through a SASS processor. Plugins are add-ons that carry out...

Loaders - webpack

Loaders are transformations that are applied to the source code of a module. They allow you to pre-process files as you import or...