Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually?

jenkins test this

💔 Build Failed

• continuous-integration/kibana-ci/pull-request

Was that a flaky build?
The react-toggle stopped being used since this PR :-
https://github.com/elastic/kibana/pull/24250/files#diff-9d4d6ec060287056b0636184d20f8dfdL23

@varunsharma27

It looks like the build failed because removing the dependency from package.json affects the yarn.lock file, and CI expects that you've run yarn kbn bootstrap to make the changes to yarn.lock locally and commit those in the branch.

Would you mind merging master once again (your baseline is probably too out of date for a pass to be valid), do the yarn kbn bootstrap, commit the changes to yarn.lock and push them?

https://kibana-ci.elastic.co/job/elastic+kibana+pull-request/3474/JOB=kibana-intake,node=immutable/console

That link will expire in a few days, but here's what I saw when I looked at the first ci group console output:

11:58:28 Bootstrapping completed!
11:58:28 
11:58:28 Done in 266.43s.
11:58:28 
11:58:28 ERROR: 'yarn kbn bootstrap' caused changes to the following files:
11:58:28 
11:58:28 yarn.lock
11:58:28 
11:58:28 runbld>>> <<<<<<<<<<<< SCRIPT EXECUTION END <<<<<<<<<<<<
11:58:28 runbld>>> DURATION: 366113ms
11:58:28 runbld>>> STDOUT: 11167 bytes
11:58:28 runbld>>> STDERR: 843 bytes
11:58:28 runbld>>> WRAPPED PROCESS: FAILURE (1)

jenkins test this

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request

Pinging @elastic/kibana-app