How to write a plugin

[pksjce]

From @IngwiePhoenix on April 23, 2015 22:2

I just noticed, that the "How to write a plugin" page was not linked yet, having me guess it wasn't done just yet. So I thought I'd give in a few questions that I, as a user/developer, would have when asking about how this is done:

• Which phases of the compiler can we tap into?
• What can we manipulate and how?
• Can we inject loaders? This would be helpful, so that we only need to have the user add a plugin, and it will register a loader if a specific file is found.
• How to manipulate the source (adding scripts, injecting scripts into other chunks, actually adding stuff to the head or bottom) and at which compile steps?
• Which phases are recomended to tap into?
• What values are available in this and does it change during the compilation steps?

I am very much interested in source manipulation at the moment, so it would be nice to hear about how this works. :)

Kind regards, Ingwie

Copied from original issue: webpack/webpack#1003

[pksjce]

From @mtscout6 on April 24, 2015 1:16

👍

[pksjce]

From @sokra on April 24, 2015 6:48

There is a some information here: http://webpack.github.io/docs/plugins.html but propably a bit out-of date

[pksjce]

From @lemmy- on April 27, 2015 8:56

👍

[pksjce]

From @IngwiePhoenix on May 5, 2015 18:55

Bump o.o

[pksjce]

This issue was moved to #99

[skipjack]

It seems this is done between the How to write a plugin doc and the plugin api docs. @IngwiePhoenix closing but definitely let us know if anything is missing from that documentation and maybe create a more targeted issue or pr detailing what needs changing or what questions still need answers.