[kbn/optimizer] meta issue

[spalger]

This is a high level overview of what I'm planning/working on with regards to the @kbn/optimizer

low hanging fruit

• auto bootstrap when you run yarn start
• yarn kbn bootstrap should automatically run yarn --force when the branch in package.json changes since the last bootstrap, add --force flag, add --brute-force flag to delete node_modules before bootstrap
• Remove yarn kbn clean

plan

• "focus" mode
• Collect performance metrics from optimizer
• Remove usage of extraPublicDirs [kbn/optimizer] Remove usage of extraPublicDir #69461
• Over allocate workers when module count exceeds a threshold
• POC - Building Sass outside of webpack, sass is the slowest part of each bundle and could be built separately like in the legacy system, but hopefully without creating hundreds of new files to be served on each page load
• POC - Improve allocation algorithm so that bundles which include similar files are allocated to the same worker

maybe someday

• POC - Use a tool other than webpack
• POC - distributed cache [kbn/optimizer] stable/predictable cache key #74918

merged

• Only allow refs to bundles described in kibana.json [kbn/optimizer] Only allow refs to bundles described in kibana.json #69458
• Only build specified themes [kbn/optimizer] only build specified themes #70389
• Sharing bundles validate performance improvement
• trim down bootstrap logging

[elasticmachine]

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

[tylersmalley]

@spalger should we close this now that we're not focused on migrating kbn/optimizer to Bazel?

[spalger]

👍