IMPORTANT: No additional bug fixes or documentation updates will be released for this version. For the latest information, see the current release documentation.
« Considerations for basePath Modules and Autoloading »
Elastic Docs ›Kibana Guide [7.6] ›Developer guide ›Core Development

Managing Dependencies

edit

Managing Dependencies

edit

While developing plugins for use in the Kibana front-end environment you will probably want to include a library or two (at least). While that should be simple to do 90% of the time, there are always outliers, and some of those outliers are very popular projects.

Before you can use an external library with Kibana you have to install it. You do that using…​

yarn (preferred method)

edit

Once you’ve found a dependency you want to add, you can install it like so:

yarn add some-neat-library

At the top of a javascript file, just import the library using it’s name:

import someNeatLibrary from 'some-neat-library';

Just like working in node.js, front-end code can require node modules installed by yarn without any additional configuration.

webpackShims

edit

When a library you want to use does use es6 or common.js modules but is not available with yarn, you can copy the source of the library into a webpackShim.

# create a directory for our new library to live
mkdir -p webpackShims/some-neat-library
# download the library you want to use into that directory
curl https://cdnjs.com/some-neat-library/library.js > webpackShims/some-neat-library/index.js

Then include the library in your JavaScript code as you normally would:

import someNeatLibrary from 'some-neat-library';

Shimming third party code

edit

Some JavaScript libraries do not declare their dependencies in a way that tools like webpack can understand. It is also often the case that libraries do not export their provided values, but simply write them to a global variable name (or something to that effect).

When pulling code like this into Kibana we need to write "shims" that will adapt the third party code to work with our application, other libraries, and module system. To do this we can utilize the webpackShims directory.

The easiest way to explain how to write a shim is to show you some. Here is our webpack shim for jQuery:

// webpackShims/jquery.js

module.exports = window.jQuery = window.$ = require('../node_modules/jquery/dist/jquery');
require('ui/jquery/findTestSubject')(window.$);

This shim is loaded up anytime an import 'jquery'; statement is found by webpack, because of the way that webpackShims behaves like node_modules. When that happens, the shim does two things:

  1. Assign the exported value of the actual jQuery module to the window at $ and jQuery, allowing libraries like angular to detect that jQuery is available, and use it as the module’s export value.
  2. Finally, a jQuery plugin that we wrote is included so that every time a file imports jQuery it will get both jQuery and the $.findTestSubject helper function.

Here is what our webpack shim for angular looks like:

// webpackShims/angular.js

require('jquery');
require('../node_modules/angular/angular');
require('../node_modules/angular-elastic/elastic');
require('ui/modules').get('kibana', ['monospaced.elastic']);
module.exports = window.angular;

What this shim does is fairly simple if you go line by line:

  1. makes sure that jQuery is loaded before angular (which actually runs the shim)
  2. load the angular.js file from the node_modules directory
  3. load the angular-elastic plugin, a plugin we want to always be included whenever we import angular
  4. use the ui/modules module to add the module exported by angular-elastic as a dependency to the kibana angular module
  5. finally, export the window.angular variable. This means that writing import angular from 'angular'; will properly set the angular variable to the angular library, rather than undefined which is the default behavior.
« Considerations for basePath Modules and Autoloading »