Loaders | webpack

Webpack handles these itself — install a loader only for what is not on this list:
Webpack enables use of loaders to preprocess everything else. This allows you to bundle any static resource way beyond JavaScript. You can easily write your own loaders using Node.js. Loaders are separate packages that extend webpack's capabilities and are maintained within the broader ecosystem. Loaders are activated by using loadername! prefixes in import .. from "mod";/require() statements, or are automatically applied via regex from your webpack configuration – see configuration.
HTML is built in (experiments.html, stable and on by default), so no loader is listed here for plain HTML — the Native HTML guide covers what is built in and how to move an existing setup over. Template engines always keep their loader.
CSS is built in (experiments.css, stable and on by default), so no loader is listed here for plain CSS — the Native CSS guide covers what is built in and how to move an existing setup over. Preprocessors always keep their loader.
For more third-party loaders, see the list from awesome-webpack.
Copyright OpenJS Foundation and webpack contributors. All rights reserved. The OpenJS Foundation has registered trademarks and uses trademarks. For a list of trademarks of the OpenJS Foundation, please see our Trademark Policy and Trademark List. Trademarks and logos not indicated on the list of OpenJS Foundation trademarks are trademarks™ or registered® trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.
The OpenJS Foundation | Terms of Use | Privacy Policy | Bylaws | Code of Conduct | Trademark Policy | Trademark List | Cookie Policy