determine API / usage for plugins

[thescientist13]

Type of Change

• New Feature Request
• Documentation / Website
• Improvement / Suggestion
• Bug
• Other (please clarify below)

Summary

Coming out of conversations in #17 an initial implementation for plugins was captured and documented for the website in #187.

module.exports = {
  title: 'My Project',

  ...

  plugins: [{
    type: 'hook|webpack|data|lifecycle|transform',  // @string required, no default
    provider: (compilation) => { /* do stuff here */ } // @function required (@return depends on type), no default
  }]

There was also a PR opening this up for further discussion in #179 .

Details

The goal of this ticket is to close the loop on possible APIs for this as part of the upcoming RFCs around data sources (#115 / #21 ) and so would be good to finalize what we should do for this.

• Class based? Or just functions?
• What access to Greenwood's API should it have access? (read only?)
• How to get data in / out
• etc

[thescientist13]

This is happening now as part of #185

[thescientist13]

Documentation established in #466