Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
Adds SCSS support for plugins #19643
The same is for external plugins, However
For core plugins, I would suggest modifying one to use SCSS.
When in development mode, a message will be logged when we transpile the SCSS into CSS.
Errors are expected to be logged. Removing one of the brackets in the example will cause this.
During development, the CSS file will be generated with source-maps when an SCSS file is modified and served when the plugin is active. This CSS file is in addition to the plugins CSS file created by the optimizer, however, that will be phased out as we migrate to SCSS.
When building a plugin outside of Kibana, you need to also set
For testing of external plugins,
Still working on figuring out how we should trigger transpiring the SCSS when running a build for both Kibana and individual plugins. During the plugin build process, we currently don't have a way of accessing the Kibana Plugin options. We might need to resort to calling the index file with babel register.