Build New Platform Plugins

[spalger]

In order to get closer to only building plugins when running from source we need a tool to build new platform plugins that is totally decoupled from the legacy optimizer, and establishes conventions we want to reuse in the updated developer toolchain @tylersmalley is working on.

My plan is to build a package that just runs a number of webpack compilers and integrates into the existing CLI. Once everything has been migrated to the new platform this tool should be able to build all the front-end assets we need and we should be able to just delete the optimizer.

Planned features:

• support single build and watch modes
• use a webpack config that is as simple as possible
  • sass support
  • no less support
  • minification support
  • automatically setup global externals for React, moment, etc.
  • automatically write default export to window.__kbnBundles__['plugin/${pluginId}']
• produce static assets that the will be loaded by the front-end and shipped with the distributable
• run webpack compilers in separate processes (optionally grouped for machines with fewer CPU cores)
• pause asset requests while builds are running

Related to #42699
Related to #36186
Related to #43290
Related to #53555

[elasticmachine]

Pinging @elastic/kibana-operations (Team:Operations)

[tylersmalley]

@spalger I believe you can close this!

[phinguyen202]

Hi guys,
I'm using kibana 7.7.0 and trying to build plugins with New Platform.
I appreciate to know that can I build/run plugins developed with New Platform at v7.7.0 or I have to upgrade to newer version?