kibana/webpackShims/angular.js

require('jquery');
require('../node_modules/angular/angular');
module.exports = window.angular;

require('../node_modules/angular-elastic/elastic');

require('ui/modules').get('kibana', ['monospaced.elastic']);
fixed incompatibilities with angular, ace, and gridster 2015-07-22 08:10:32 +02:00			`require('jquery');`
[6.x] Upgrade to webpack 3 (#14315) (#14824) * [timelion] remove last remaining amd modules * [eslint-config-kibana] remove env.amd * [webpack] use absolute loader names * [webpack] remove absolute node_modules/ imports * [webpack] upgrade to webpack 3 * [uiFramework] make webpack build compatible with v3 * [eslint-import-resolver] use https://github.com/elastic/eslint-import-resolver-kibana/pull/21 * [baseOptimizer] don't break when pkg has no dependencies * [optimize] remove unnecessary json-loader * [optimize] remove local references to webpack vars * [eslint] upgrade to eslint-import-resolver-kibana 0.9.0 * [baseOptimizer] comment tweaks * [baseOptimizer] remove loader pinning In webpack 1 the loaders defined here were resolved relative to the file they were going to load, which meant that plugins in other projects could accidentally overwrite the loaders Kibana was trying to use, which is why the aliases were used to enforce proper resolution. In webpack 2 loaders are now resolved relative to the webpackConfig.context, which is set to the root of the Kibana repo. See https://webpack.js.org/configuration/module/#useentry * [webpack] rely on kibana webpack shims before checking node_modules (cherry picked from commit f60639fccb2fa355b44129f940d3841b59dd47a6) 2017-11-07 23:54:48 +01:00			`require('../node_modules/angular/angular');`
fixed incompatibilities with angular, ace, and gridster 2015-07-22 08:10:32 +02:00			`module.exports = window.angular;`
move meta-modules into special embedded plugin, simplify dependency pairs like leaflet 2015-07-22 02:50:33 +02:00
[6.x] Upgrade to webpack 3 (#14315) (#14824) * [timelion] remove last remaining amd modules * [eslint-config-kibana] remove env.amd * [webpack] use absolute loader names * [webpack] remove absolute node_modules/ imports * [webpack] upgrade to webpack 3 * [uiFramework] make webpack build compatible with v3 * [eslint-import-resolver] use https://github.com/elastic/eslint-import-resolver-kibana/pull/21 * [baseOptimizer] don't break when pkg has no dependencies * [optimize] remove unnecessary json-loader * [optimize] remove local references to webpack vars * [eslint] upgrade to eslint-import-resolver-kibana 0.9.0 * [baseOptimizer] comment tweaks * [baseOptimizer] remove loader pinning In webpack 1 the loaders defined here were resolved relative to the file they were going to load, which meant that plugins in other projects could accidentally overwrite the loaders Kibana was trying to use, which is why the aliases were used to enforce proper resolution. In webpack 2 loaders are now resolved relative to the webpackConfig.context, which is set to the root of the Kibana repo. See https://webpack.js.org/configuration/module/#useentry * [webpack] rely on kibana webpack shims before checking node_modules (cherry picked from commit f60639fccb2fa355b44129f940d3841b59dd47a6) 2017-11-07 23:54:48 +01:00			`require('../node_modules/angular-elastic/elastic');`
lean on metaLibs using ui/modules for angular-module injection 2015-07-22 04:40:07 +02:00
Remove angular-translate (#13066) (#16015) * remove angular translate * remove angular-translate deps from yarn.lock 2018-01-27 19:47:35 +01:00			`require('ui/modules').get('kibana', ['monospaced.elastic']);`