Open kbujold opened 1 month ago
Pinging @elastic/kibana-operations (Team:Operations)
How to fix the issue of browser. I keep getting even if i have installed with npx/yarn
ERROR Browserslist: caniuse-lite is outdated. Please run:
│ info stopping @kbn/optimizer
@ankita-mehta-bsn you can run this command npx update-browserslist-db@latest
@kbujold This npx update-browserslist-db@latest
didnt help. There is more to it than just updating browserslist.
@kbujold This
npx update-browserslist-db@latest
didnt help. There is more to it than just updating browserslist.
This is true for me as well - should we open a new issue or is this an easy fix (I'm very new to plugin dev...)?
@kbujold This
npx update-browserslist-db@latest
didnt help. There is more to it than just updating browserslist.This is true for me as well - should we open a new issue or is this an easy fix (I'm very new to plugin dev...)?
I'm answering my own question - if you run npx update-browserslist-db@latest
in the main kibana directory it will update that dependency correctly and "free up" the plugin build.
Kibana version: Seen in ELK 8.11.1 and up
Elasticsearch version:
Seen in ELK 8.11.1 and up
Server OS version: NA
Browser version: NA
Browser OS version: NA
Original install method (e.g. download page, yum, from source, etc.):
Describe the bug:
The Kibana script "scripts/plugin_helpers" returns 0 even when failure is encountered. This is not optimal has we want our build to fail if there is an error.
To fix this issue I think there should be a process.exit(1); here after the log.
Steps to reproduce: Create a kibana plugin. Cause a failure See the
plugin-helpers
return successExpected behavior: The Plugin's
yarn build
should return an error if it encounters oneScreenshots (if relevant):
Errors in browser console (if relevant):
Provide logs and/or server output (if relevant):
Any additional context: Forum post regarding this issue https://discuss.elastic.co/t/kibana-script-plugin-helpers-returns-0-even-when-failure-is-encountered/364701