#19643 (comment) added the ability for plugins to generate css files from sass included in plugins.
What we'll also need need is a way to generate a core (across every kibana page) css file (from a scss file) that is included on every Kibana page.
As an example... here is what the load order of css on a random app within kibana should look like:
eui_theme_k6.dark.css (hard import from EUI, loaded on all pages, this already works)
kibana.css (compiled from SCSS, loaded on all pages, regardless of routing, this is done in styles.js now)
named_plugin.css (compiled from SCSS, loaded only on routes of that plugin)
Right now the equivalent of kibana.css lives in src/ui/public/styles Less files and is generated in styles.js
I don't think this would ever require something complicated, so it could be a hardcoded src/public/index.scss file if we wanted. The sass watcher would just need to generate a css file from that location and then reference itself in Kibana's chrome.
#19643 (comment) added the ability for plugins to generate css files from sass included in plugins.
What we'll also need need is a way to generate a core (across every kibana page) css file (from a scss file) that is included on every Kibana page.
As an example... here is what the load order of css on a random app within kibana should look like:
Right now the equivalent of kibana.css lives in
src/ui/public/stylesLess files and is generated instyles.jsI don't think this would ever require something complicated, so it could be a hardcoded
src/public/index.scssfile if we wanted. The sass watcher would just need to generate a css file from that location and then reference itself in Kibana's chrome.