maxmustermann/kibana
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity
kibana/package.json

347 lines
11 KiB
JSON
Raw Normal View History

initial commit
2014-02-07 00:29:19 +01:00
{
Add grunt plugin to build K4 as a plugin
2014-06-17 01:52:19 +02:00
"name": "kibana",
Update package.json (#20353) * Update package.json * skip root before resolving
2018-09-17 18:46:03 +02:00
"description": "Kibana is a browser based analytics and search dashboard for Elasticsearch. Kibana is a snap to setup and start using. Kibana strives to be easy to get started with, while also being flexible and powerful, just like Elasticsearch.",
Consolidating package.json adding JSON logger
2015-01-07 21:48:58 +01:00
"keywords": [
"kibana",
"elasticsearch",
"logstash",
"analytics",
"visualizations",
"dashboards",
"dashboarding"
],
Update package.json (#20353) * Update package.json * skip root before resolving
2018-09-17 18:46:03 +02:00
"private": true,
Revert "override version until elastic/elasticsearch#25876 is merged" (#13196) This reverts commit ce8333b70f6034735afc08c4c6792bb1bbc22e89.
2017-08-02 02:43:42 +02:00
"version": "7.0.0-alpha1",
Change the way dynamic doc links are built so they work in dev and pre-release builds (#11913) * Change the way dynamic doc links are built so they work even in dev and pre-release builds * update test
2017-05-23 21:46:54 +02:00
"branch": "master",
Merge branch 'master' of github.com:elastic/kibana into apps/home
2015-07-29 22:11:04 +02:00
"build": {
bump version to 4.2.0-snapshot
2015-08-31 20:14:09 +02:00
"number": 8467,
"sha": "6cb7fec4e154faa0a4a3fee4b33dfef91b9870d9"
Merge branch 'master' of github.com:elastic/kibana into apps/home
2015-07-29 22:11:04 +02:00
},
[Docs, Links] Changed all of the relevant links and occurences of the string elasticsearch to take into consideration the rebranding during elasitcon and keynote
2015-03-17 02:18:50 +01:00
"homepage": "https://www.elastic.co/products/kibana",
Closes #2377 - Migrate config from > GA - Closes #2377 - Added testing framework for server side tests - Fixed jshint - Added config migration - Added framework for server initialization
2015-01-23 19:34:29 +01:00
"bugs": {
[cleanup] Fixed some missed changes, or hyper ones i made
2015-03-17 02:32:09 +01:00
"url": "http://github.com/elastic/kibana/issues"
Closes #2377 - Migrate config from > GA - Closes #2377 - Added testing framework for server side tests - Fixed jshint - Added config migration - Added framework for server initialization
2015-01-23 19:34:29 +01:00
},
[Docs, Links] Changed all of the relevant links and occurences of the string elasticsearch to take into consideration the rebranding during elasitcon and keynote
2015-03-17 02:18:50 +01:00
"author": "Rashid Khan <rashid.khan@elastic.co>",
Consolidating package.json adding JSON logger
2015-01-07 21:48:58 +01:00
"scripts": {
Preinstall check that mentions 'yarn kbn' (#16572)
2018-02-08 13:40:57 +01:00
"preinstall": "node ./preinstall_check",
Kibana build tool (#15055) * Introduce `kbn`, the Kibana build tool * yarn kbn * Make all deps devDeps * Exclude __fixtures__ folder from Jest to avoid warnings * Review fixes * Update readme * Use 'yarn kbn' * Consistent rootPath * Link to kbn tool * Unsupported URL 'debug help' in contributing guide
2018-01-24 10:34:52 +01:00
"kbn": "node scripts/kbn",
[kbn-es] Package for managing Elasticsearch during dev and testing (#17168) Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co>
2018-03-20 16:30:15 +01:00
"es": "node scripts/es",
"elasticsearch": "echo 'use `yarn es snapshot -E path.data=../data/`'",
Remove test:visualRegression from test npm script. - Add it to end of test grunt task.
2016-06-21 20:23:40 +02:00
"test": "grunt test",
[grunt] broke test task into chunks, linked from package.json
2015-08-18 23:51:31 +02:00
"test:dev": "grunt test:dev",
"test:quick": "grunt test:quick",
"test:browser": "grunt test:browser",
Deprecate test:ui commands (#21092) * Deprecate test:ui commands
2018-07-23 21:48:27 +02:00
"test:ui": "echo 'use `node scripts/functional_tests`' && false",
"test:ui:server": "echo 'use `node scripts/functional_tests_server`' && false",
Convert makelogs and mocha npm scripts (#11665) * [scripts] convert `npm run makelogs` to script * [scripts] convert `npm run mocha` to script * [scripts] add warning to `test:ui:runner` npm script * [script] fix location of scripts in warnings
2017-05-09 19:53:10 +02:00
"test:ui:runner": "echo 'use `node scripts/functional_test_runner`' && false",
[grunt] broke test task into chunks, linked from package.json
2015-08-18 23:51:31 +02:00
"test:server": "grunt test:server",
generate the test coverage
2015-08-25 02:10:21 +02:00
"test:coverage": "grunt test:coverage",
chore(19502): change license checker and generator behaviour to only add dev dependencies with --dev flag. (#19626)
2018-06-12 16:56:10 +02:00
"checkLicenses": "grunt licenses --dev",
Migrate x-pack-kibana source to kibana
2018-04-20 21:13:37 +02:00
"build": "node scripts/build",
Create separate startup scripts for development and production (#13806) * Use separate startup scripts for development and production * build kibana directly * [build] Use downloaded node when pre-optimizing * clearer variable name * Add breaking changes docs
2017-11-22 19:49:37 +01:00
"start": "node scripts/kibana --dev",
Do not break on startup in debug mode (#19219) Starting up the server in debug mode should not interrupt by default.
2018-05-18 21:15:05 +02:00
"debug": "node --nolazy --inspect scripts/kibana --dev",
"debug-break": "node --nolazy --inspect-brk scripts/kibana --dev",
[precommit hook] add dev script (#14890) * [precommitHook] move to dev script * [eslint] fix lint error * [dev/eslint] do simply boolean checks first * [dev] use shared REPO_ROOT constant * [dev/File] precompute relative/ext of path * [dev/eslint] fix relative import * [dev/eslint] fix typos * [grunt] remove unused run:eslintStaged config * [dev/run] only create log if we are going to use it * [dev/run/isFailError] ensure return value is Boolean * [dev/precommitHook] use less intermediate vars
2017-11-20 22:22:24 +01:00
"precommit": "node scripts/precommit_hook",
[npm] added es script for running elasticsearch with esvm
2015-08-29 06:42:21 +02:00
"karma": "karma start",
[tslint] lint typescript code (#19105) * [tslint] lint typescript code * [tslint] filter projects when running specific project * [dev/ts] use more explicit types * [dev/ts] add note about why using glob * [dev/ts] rely on ts, use fewer getters
2018-05-22 23:00:02 +02:00
"lint": "echo 'use `node scripts/eslint` and/or `node scripts/tslint`' && false",
"lintroller": "echo 'use `node scripts/eslint --fix` and/or `node scripts/tslint --fix`' && false",
Convert makelogs and mocha npm scripts (#11665) * [scripts] convert `npm run makelogs` to script * [scripts] convert `npm run mocha` to script * [scripts] add warning to `test:ui:runner` npm script * [script] fix location of scripts in warnings
2017-05-09 19:53:10 +02:00
"makelogs": "echo 'use `node scripts/makelogs`' && false",
"mocha": "echo 'use `node scripts/mocha`' && false",
Migrate UI Framework source into Kibana. (#9192) Migrate UI Framework source into Kibana. - Add dependencies to package.json. - Add task for building UI Framework docs and serving locally. - Import UI Framework scss from autoload/styles.js instead of importing the CSS in base.less. - Refactor UI Framework directory structure. - Remove babel-polyfill. - Include SCSS synchronously.
2016-12-13 02:54:56 +01:00
"sterilize": "grunt sterilize",
[@kbn/ui-framework] move ui-framework to a package (#17085) * [@kbn/ui-framework] move ui-framework to a package * [@kbn/ui-framework] restore doc_site index.html and fix build task names * [jest] always ignore modules in target dirs
2018-03-13 18:43:39 +01:00
"uiFramework:start": "cd packages/kbn-ui-framework && yarn docSiteStart",
"uiFramework:build": "cd packages/kbn-ui-framework && yarn docSiteBuild",
"uiFramework:createComponent": "cd packages/kbn-ui-framework && yarn createComponent",
[kbn-pm] Implement `kbn watch`. (#16892)
2018-03-26 17:54:40 +02:00
"uiFramework:documentComponent": "cd packages/kbn-ui-framework && yarn documentComponent",
"kbn:watch": "node scripts/kibana --dev --logging.json=false"
Consolidating package.json adding JSON logger
2015-01-07 21:48:58 +01:00
},
"repository": {
"type": "git",
[Docs, Links] Changed all of the relevant links and occurences of the string elasticsearch to take into consideration the rebranding during elasitcon and keynote
2015-03-17 02:18:50 +01:00
"url": "https://github.com/elastic/kibana.git"
Consolidating package.json adding JSON logger
2015-01-07 21:48:58 +01:00
},
"dependencies": {
EUI 4.0.1 (#23009)
2018-09-14 01:14:17 +02:00
"@elastic/eui": "4.0.1",
[npm] move personal forks into elastic org (#13410)
2017-08-09 21:31:30 +02:00
"@elastic/filesaver": "1.1.2",
update numeral-js dependency - elastic fork (#17508)
2018-04-03 18:15:59 +02:00
"@elastic/numeral": "2.3.2",
[npm] move personal forks into elastic org (#13410)
2017-08-09 21:31:30 +02:00
"@elastic/ui-ace": "0.2.3",
Prettier + ESLint setup (#16514) * Move .eslintrc (yaml) to .eslintrc.js (js) * Add Prettier setup to ESLint * Run Prettier on @kbn/build * Update style guide with Prettier
2018-02-05 18:18:43 +01:00
"@kbn/babel-preset": "link:packages/kbn-babel-preset",
Production package example: datemath (#16531)
2018-02-13 21:49:55 +01:00
"@kbn/datemath": "link:packages/kbn-datemath",
Add draft implementation of I18n engine (#19555) * Add draft implementation of I18n engine * Add i18n loader * kbn-i18n refactoring * Fix react i18n context and update doc * i18n engine refactoring * Fix locales data loading and add more jsdoc comments * Fix verify_translations task * I18n tests refactoring * Add build scripts to kbn-i18n package * Fix some bugs * Move uiI18nMixin into ui_i18n folder * Add 'browser' field to kbn-i18n package.json * Get rid of "showError" method * Make i18n and i18nLoader a singleton object * Add default locale as fallback if translation files were not registered * Update yarn.lock * kbn-i18n fix * Add default formats * Try to fix build * Add more examples into kbn-i18n/README.md * kbn-i18n fix * Fix app_bootstrap tests * Add links to issues in TODO comments
2018-06-28 11:38:39 +02:00
"@kbn/i18n": "link:packages/kbn-i18n",
[Management] Source filters table in React (#16649) * Source filters table * Updates * Handle no source filters * PR feedback * Fix merge issues * PR feedback * PR feedback * PR feedback * Upgrade to 3.3.0 which allows us to use Fragments in enzyme tests * Use EuiInMemoryTable instead * Remove dead code and simplify some tests * Dynamically update the matches as the user edits the filter * Apparently, this has been using the wrong parameter name * Restructure to stop storing computed data and add reselect helper * Reselect is tiny, just use that * PR feedback * Fix merge issues * PR feedback
2018-03-09 23:20:00 +01:00
"@kbn/pm": "link:packages/kbn-pm",
Add test-subj-selector module to packages dir. (#16623) * Add test-subj-selector module to packages dir. * Rename to @kbn/test-subj-selector. * Simplify rejectRejFiles Grunt task and ignore nested node_modules. * Update jenkins_unit script to use yarn kbn CLI.
2018-02-13 19:34:47 +01:00
"@kbn/test-subj-selector": "link:packages/kbn-test-subj-selector",
[@kbn/ui-framework] move ui-framework to a package (#17085) * [@kbn/ui-framework] move ui-framework to a package * [@kbn/ui-framework] restore doc_site index.html and fix build task names * [jest] always ignore modules in target dirs
2018-03-13 18:43:39 +01:00
"@kbn/ui-framework": "link:packages/kbn-ui-framework",
Add ability to abort a kfetch call. (#20700) * Split kfetch module into kfetch and kfetchAbortable sub-modules. * Add abortcontroller-polyfill.
2018-07-13 01:11:24 +02:00
"abortcontroller-polyfill": "^1.1.9",
bump angular to 1.6.9 (#17677)
2018-04-12 17:42:45 +02:00
"angular": "1.6.9",
[Accessibility] Load angular-aria for kibana module (#14969) * Load angular-aria for kibana module * Fix indentation * Add documentation
2017-11-17 09:33:11 +01:00
"angular-aria": "1.6.6",
remove bower, nice people matter
2015-07-28 02:13:45 +02:00
"angular-elastic": "2.5.0",
[angular-recursion] use angular-recursion module from npm (#17584)
2018-04-05 22:58:06 +02:00
"angular-recursion": "^1.0.5",
Merge branch 'master' into angularUpgrade
2015-10-15 15:32:20 +02:00
"angular-route": "1.4.7",
Bump marked
2016-07-21 20:44:47 +02:00
"angular-sanitize": "1.5.7",
[webpack] fix loader query string usage (#9497) * [webpack] pin to fork with fixed loader aliases * [optimizer] upgrade to postcss+autoprefixer * [timelion] convert uiExports.modules -> webpackShims * [uiExports] remove implementation-leaking and unused uiExport types * [optimizer] remove unused imports * [uiBundlerEnv] add a method for exporting global import aliases for special cases
2016-12-16 00:11:42 +01:00
"angular-sortable-view": "0.0.15",
[scss] Adds autoprefixer support and improves watcher (#21656) This adds support for autoprefixer which we have been using in Webpack. Additionally, we have improved the watching functionality and now update builds based directly on their dependencies an not an assumption that the files are children. Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co>
2018-08-10 23:24:14 +02:00
"autoprefixer": "^9.1.0",
babel 6 upgrade (#9702) * [npm] upgrade babel The upgrade to babel 6 requires an upgrade to all of the associated modules, which meant that a few other things changed at the same time. The most notable is the way that we handle our babel-options, which is now done with an npm module and includes using the babel-loader's "presets" query string param. This meant changes to the babel_options.js module and extending it to help setting up the "babel-register" module, which was previously copy-pasted in several places. * [mtodules] upgrade to support babel6 module semantics * [eslint] fix lint errors * [babel] ignoer massive fixture files * [cli/errors] use Object.setPrototypeOf since subclassing Error is broken * [babel] Upgrading core babel libraries [babel] Use WIP babel-6-fix branch of babel-preset-kibana * Fix broken test * [babel] Reverse unnecessary module.exports changes * Fix notifier * Use babel presets and plugins directly * [babel/options] resolve preset/plugins paths for better plugin compatibility * [babel/options] use babel-preset-env for correct node settings * [babel] cache babel compilation in webpack like we thought we were
2017-02-09 22:48:55 +01:00
"babel-core": "6.21.0",
Upgrade to webpack 3 (#14315) * [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
2017-11-01 00:31:22 +01:00
"babel-loader": "7.1.2",
babel 6 upgrade (#9702) * [npm] upgrade babel The upgrade to babel 6 requires an upgrade to all of the associated modules, which meant that a few other things changed at the same time. The most notable is the way that we handle our babel-options, which is now done with an npm module and includes using the babel-loader's "presets" query string param. This meant changes to the babel_options.js module and extending it to help setting up the "babel-register" module, which was previously copy-pasted in several places. * [mtodules] upgrade to support babel6 module semantics * [eslint] fix lint errors * [babel] ignoer massive fixture files * [cli/errors] use Object.setPrototypeOf since subclassing Error is broken * [babel] Upgrading core babel libraries [babel] Use WIP babel-6-fix branch of babel-preset-kibana * Fix broken test * [babel] Reverse unnecessary module.exports changes * Fix notifier * Use babel presets and plugins directly * [babel/options] resolve preset/plugins paths for better plugin compatibility * [babel/options] use babel-preset-env for correct node settings * [babel] cache babel compilation in webpack like we thought we were
2017-02-09 22:48:55 +01:00
"babel-polyfill": "6.20.0",
"babel-register": "6.18.0",
[npm] remove package ranges Fixes #4866 As recently discussed in https://github.com/elastic/kibana/issues/4824 we have had a fair number of challenges with dependencies shipping breaking changes or broken code within the semver ranges which should prevent them. Nobody is perfect, we don't expect that, but as Kibana grows the number of modules does too. The output of npm ls is currently over 1100 lines, meaning we are very exposed to the semver ranges specified. While we may actually use a shrinkwrap file at some point, or implement something like uber's custom shrinkwrap utility, the only issues we have faced have been caused by top level dependencies (especially the very fast-moving ones).
2015-09-05 10:49:36 +02:00
"bluebird": "2.9.34",
[fix/UiSettings] ignore certain errors (#13079) * [SavedObjectClient] emit detectable errors * [uiSettingsService] consume new SavedObjectsClient errors * [SavedObjectsClient] expose errorTypeHelpers as such * [elasticsearch/tests] recreate error for each test * [http] wait for elasticsearch plugin to be ready * [shortUrl/tests] ensure that create request responds with 200 * [shortUrl] use errorTypeHelpers to filter errors * [uiSettings/savedObjectsClientStub] stub errorTypeHelpers * [SavedObjectsClient/errors] expose error module so tests can make errors * [shortUrl/tests] use actual SavedObjectsClient errors * [uiSettings/savedObjectsClientStub] use actual errors lib * [SavedObjectsClient] use decorate instead of "wrap" * [server/routes/uiSettings] refactor routes to forward Boom errors from uiSettings * [uiSettings] colocate routes and service * [testUtils/esTestCluster] use more standard api style * [testUtils/es] add createCallCluster util * [testUtils/esTestCluster] add getters for client/callCluster * [es/healthcheck] ensure that healtcheck stops when server is stopped * [uiSettings/routes] add param/payload validation * [uiSettings/routes] add tests that verify error behaviors
2017-08-09 02:55:36 +02:00
"boom": "5.2.0",
upping ace version to the latest (#19067)
2018-05-15 22:31:26 +02:00
"brace": "0.11.1",
Upgrade to webpack 3 (#14315) * [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
2017-11-01 00:31:22 +01:00
"cache-loader": "1.0.3",
Match chalk dependency version on kibana with the one used on x-pack (#20621) * chore(NA): match chalk dependency version on kibana with x-pack to ^2.3.2. * chore(NA): bump chalk version dependencies and update lock files.
2018-07-13 01:26:57 +02:00
"chalk": "^2.4.1",
Time Series Metric Visualizations (#9725) * Initial import * updating the editor width to match the new specs * Adding tribe node support * Adding tests for server libs * removing bluebird * removing extra cruft * Fixing the font sizes * Fixed the updating code * Adding brushing * Fixing linting issues * Adding global filters * Adding missing packages * Default gauge style to half circle * Fixing the markdown css bug * Adding tests for the get_vis_data api * Adding time offset * Adding time offset to each type * fixing bugs from time offset * adding index pattern option to series * Adding index pattern overrides * Adding index pattern overrides * Fixing tests * Fixing brushing in the vis editor * Changing the label * Change the behavior of selecting a pipeline agg when only one exists. * Refactoring series a bit * Changing series options to just options * Making sure we honor the toaster container height * Adding first tests * renaming vis_config to panel_config * renaming vis_config to panel_config * Adding more tests * adding more tests * removing api subdirectory * refactoring get_vis_data (breaking it up and removing unused imports) * reorganizing the visualization directory * Re-organizing directory layouts and moving things to more logical places * Refactoring React compontents to use ES6 syntax and adding propTypes for each. Also refactored out splats as much as possible. * Adding serial differencing * Refactored gauge to use 2 components instead of 4 * Finishing react refactor on visualizations. Consolidated legned funtionality * Refactoring series config and removing a bunch of duplicate code * fixing series config name * Fixing numbers and strings (doesnt matter which it is); Fixing classname * Changing the way the dark theme works * Adding new vis into list for test * Adding empty bucket check * Fixing the index patterns in the aggs * Fixing typo * Refactoring vis_data * Fixing std_metric * Fixing refresh-hack * Adding tests for get_splits, get_last_metric, map_bucket * Fixing the error handing * removing restrictions * Sometimes values are strings or numbers... it doesn't matter * Adding new color options for splits * Fixing colors * fixing size * Adding support for fitlers agg * Fixing tests * Fixing splits for filters * Fixing Top N to work better with fitlers * Adding annotation editor * initial work for annotations * Finalizing annotations * Fixing label * making it expandable * Fixing hacks fixed by #10175 * Fixing bars to use the same stacking options as lines * Getting rid of align by colons * removing unused depends * removing unused depends * Changing to readable lodash function * Adding missing parens * refactoring custom color picker * Removing string refs and converting uncontrolled components * Fixing the controlled components where value maybe null; converting error to css * refactoring styles from components * fixing the refresh behavoir borked by fullEditor * Adding the executor service * Fixing the test directories * fixing save * Adding filter ratios * Fixing controlled components * Trying to fix the weird typing * Fixing offset bug with days * Adding percentile rank * Fixing yaxis updates; fixing percentile rank layout; adding steps to line chart * removing unused depends * Fixed a bug with the index patterns updating; fixed bug with charts rendering too much * Fixing tests * Commenting out React tests because the ENV must have change and they are no longer working * Moving bucket transform * moving calculate auto * Moving calculate_indices * moving extended_stats_types && get_agg_value * moving get_buckets_path * moving get_sibling_agg_value * moving parse_settings * moving series_agg * Moving unit_to_seconds * Fixing tests * Fixing per PR * Renaming vars to make it more clear what's happening * Changing the way testible functions are exported * fixing tests * removing unused imports; fixing typos; fixing package name * Name has to match the plugin path * Fixing typos; removing unused imports * fixing tests * rearanging and removing unused imports * Fixing a bug with unque names for radio buttons on the same form * Fixing filter ratio to use a metric instead of just count * fixing a bug with the new filter ratios * Fixing the file path from the #8 * Fixing renderComplete trigger; Fixing embedded mode; Changing names for Timelion and Time Series Visual Builder * Fixing name * Fixing docs * Fixing a typo for the field select for terms splits * Fixing tests
2017-03-02 21:07:28 +01:00
"color": "1.0.3",
[npm] remove package ranges Fixes #4866 As recently discussed in https://github.com/elastic/kibana/issues/4824 we have had a fair number of challenges with dependencies shipping breaking changes or broken code within the semver ranges which should prevent them. Nobody is perfect, we don't expect that, but as Kibana grows the number of modules does too. The output of npm ls is currently over 1100 lines, meaning we are very exposed to the semver ranges specified. While we may actually use a shrinkwrap file at some point, or implement something like uber's custom shrinkwrap utility, the only issues we have faced have been caused by top level dependencies (especially the very fast-moving ones).
2015-09-05 10:49:36 +02:00
"commander": "2.8.1",
Migrating vega_vis from plugin (#15014) Large PR to migrate Vega plugin into the core. https://github.com/nyurik/kibana-vega-vis The code underwent a large number of changes and reviews discussed in the PR thread: https://github.com/elastic/kibana/pull/15014
2018-01-13 21:14:04 +01:00
"compare-versions": "3.1.0",
Upgrade to webpack 3 (#14315) * [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
2017-11-01 00:31:22 +01:00
"css-loader": "0.28.7",
Adding CustomEvent polyfill for IE11 support (#16275) * Adding CustomEvent polyfill for IE11 support * Fixed version * Fixed version in the yarn.lock as well * Back to ^
2018-01-25 15:38:16 +01:00
"custom-event-polyfill": "^0.3.0",
[npm] remove package ranges Fixes #4866 As recently discussed in https://github.com/elastic/kibana/issues/4824 we have had a fair number of challenges with dependencies shipping breaking changes or broken code within the semver ranges which should prevent them. Nobody is perfect, we don't expect that, but as Kibana grows the number of modules does too. The output of npm ls is currently over 1100 lines, meaning we are very exposed to the semver ranges specified. While we may actually use a shrinkwrap file at some point, or implement something like uber's custom shrinkwrap utility, the only issues we have faced have been caused by top level dependencies (especially the very fast-moving ones).
2015-09-05 10:49:36 +02:00
"d3": "3.5.6",
Add Tag Cloud Visualization A tag cloud visualization is a visual representation of text data, typically used to visualize free form text. Tags are usually single words. The font size of word corresponds with its importance.
2016-11-21 23:03:25 +01:00
"d3-cloud": "1.2.1",
Move del to dependencies (#20921)
2018-07-18 13:55:23 +02:00
"del": "^3.0.0",
[test] Added draggable container, item, and handles tests.
2016-05-12 11:46:34 +02:00
"dragula": "3.7.0",
bump elasticsearch (#21786)
2018-09-17 18:48:30 +02:00
"elasticsearch": "^15.1.1",
"elasticsearch-browser": "^15.1.1",
[state/unhashUrl] use encode-uri-query to generate cleanly encoded urls By default, the url.format function stringifies the query object and encodes each parameter with `encodeURIComponent()`. This is effective, but does not match the native browser behavior, which is to only encode the non-`pchar` characters as defined by [rfc3986][1]. Because of this, angular's `$location.search()` function uses a function internally called `encodeUriQuery()` to mimic the browser behavior before updating `location.href`. To bring the same funtionality to the `unhashUrl()` function, the `encodeUriQuery()` was extracted into it's own package and used as the escape handler for `querystring.stringify()` [1]: https://www.ietf.org/rfc/rfc3986.txt
2016-09-10 00:39:57 +02:00
"encode-uri-query": "1.0.0",
[dep] Bump even-better to 7.0.2 fixing potential memory leak issues.
2016-06-01 22:26:09 +02:00
"even-better": "7.0.2",
[plugins] Ensures X-Pack is available during plugin install (#19426) For the default distribution, we were not including X-Pack during plugin installation. This broke plugin installation which relied on X-Pack interfaces. Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co>
2018-05-25 20:57:40 +02:00
"execa": "^0.10.0",
[npm] remove package ranges Fixes #4866 As recently discussed in https://github.com/elastic/kibana/issues/4824 we have had a fair number of challenges with dependencies shipping breaking changes or broken code within the semver ranges which should prevent them. Nobody is perfect, we don't expect that, but as Kibana grows the number of modules does too. The output of npm ls is currently over 1100 lines, meaning we are very exposed to the semver ranges specified. While we may actually use a shrinkwrap file at some point, or implement something like uber's custom shrinkwrap utility, the only issues we have faced have been caused by top level dependencies (especially the very fast-moving ones).
2015-09-05 10:49:36 +02:00
"expiry-js": "0.1.7",
Upgrade to webpack 3 (#14315) * [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
2017-11-01 00:31:22 +01:00
"extract-text-webpack-plugin": "3.0.1",
"file-loader": "1.1.4",
[functionalTestRunner] replace intern (#10910) * [functional_test_runner] replace functional testing tools with custom/pluggable solution * [functional_test_runner] Convert unit tests to commonjs format * [functional_test_runner] Fix dashboard test in wrong mode * [functional_test_runner] Add dashboardLandingPage test subject * [functional_test_runner] Get Visualize page object * [functional_test_runner] Fix outdated references * [functional_test_runner] Fix more outdated refs * [functional_test_runner] Remove duplicate tests * [functional_test_runner] Improve test readability * [functional_test_runner] :disappointed: So many duplicate methods * [functional_test_runner] Move mgmt `before` outside toplevel describe * [functional_test_runner] Settings page obj missing methods * [functional_test_runner] Add improvements from @gammon * [functional_test_runner] Fix return statements in async funcs * [functional_test_runner] Move before() to correct scope * [functional_test_runner] Add after() hooks to remove index patterns * [functional_test_runner] Attempt to fix vertical bar chart tests * [functional_test_runner] Clean up * [functional_test_runner] Reinstate unit tests * [functional_test_runner] Set default loglevel back to info * [functional_test_runner] Replace `context`s with `describe`s * [functional_test_runner] Better error handling * [functional_test_runner] Add in new Tile Map tests * Incorporate changes from master * [functional_test_runner] validate that every test file has a single top-level suite * Update contributing doc with link to full doc * [docs] Spelling and grammar fixes * docs: writing and running functional tests * [docs] Move plugin doc to plugin area * [docs] Housekeeping. Doc in wrong place * [docs] Remove dup doc file * [grunt] Only run mocha_setup when running tests, not every grunt task
2017-04-12 00:01:06 +02:00
"font-awesome": "4.4.0",
Updating minimatch (#21050)
2018-07-27 13:30:17 +02:00
"glob": "^7.1.2",
"glob-all": "^3.1.0",
[npm] remove package ranges Fixes #4866 As recently discussed in https://github.com/elastic/kibana/issues/4824 we have had a fair number of challenges with dependencies shipping breaking changes or broken code within the semver ranges which should prevent them. Nobody is perfect, we don't expect that, but as Kibana grows the number of modules does too. The output of npm ls is currently over 1100 lines, meaning we are very exposed to the semver ranges specified. While we may actually use a shrinkwrap file at some point, or implement something like uber's custom shrinkwrap utility, the only issues we have faced have been caused by top level dependencies (especially the very fast-moving ones).
2015-09-05 10:49:36 +02:00
"good-squeeze": "2.1.0",
Upgrades Hapi to 14.2.0 As of Node 6, crypto.pbkdf emits a deprecation warning when the digest isn't explicily set. Under certain conditions we are seeing this warning from Hapi's dependency Iron. Iron resolved this issue as of 4.0.4, which was introduced into Hapi as of 14.0.0. Node deprecation: https://github.com/nodejs/node/pull/4047/commits/8e8959d3ee0bfe48b5f4d239e7f031a1a27708f0 Iron's resolution: https://github.com/hueniverse/iron/pull/43/commits/9e0a1ef5927c707fc79c5f2fa8c69a4b956897a4 As of Hapi v9, they have removed three build-in plugins from the core which we rely on inert (files and directories), vision (view templates), and h2o2 (proxy). https://github.com/hapijs/hapi/issues/2682 Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co>
2016-09-13 21:20:22 +02:00
"h2o2": "5.1.1",
Integrate new platform (core) server side into Kibana (#18951) Co-authored-by: Kim Joar Bekkelund <kjbekkelund@gmail.com> Co-authored-by: archana <archanid@users.noreply.github.com> Co-authored-by: Spencer <spalger@users.noreply.github.com> Co-authored-by: Court Ewing <court@epixa.com>
2018-07-11 10:19:35 +02:00
"h2o2-latest": "npm:h2o2@8.1.2",
Moving handlebars from a devDependency to a dependency (#10801)
2017-03-20 14:06:12 +01:00
"handlebars": "4.0.5",
Upgrades Hapi to 14.2.0 As of Node 6, crypto.pbkdf emits a deprecation warning when the digest isn't explicily set. Under certain conditions we are seeing this warning from Hapi's dependency Iron. Iron resolved this issue as of 4.0.4, which was introduced into Hapi as of 14.0.0. Node deprecation: https://github.com/nodejs/node/pull/4047/commits/8e8959d3ee0bfe48b5f4d239e7f031a1a27708f0 Iron's resolution: https://github.com/hueniverse/iron/pull/43/commits/9e0a1ef5927c707fc79c5f2fa8c69a4b956897a4 As of Hapi v9, they have removed three build-in plugins from the core which we rely on inert (files and directories), vision (view templates), and h2o2 (proxy). https://github.com/hapijs/hapi/issues/2682 Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co>
2016-09-13 21:20:22 +02:00
"hapi": "14.2.0",
Integrate new platform (core) server side into Kibana (#18951) Co-authored-by: Kim Joar Bekkelund <kjbekkelund@gmail.com> Co-authored-by: archana <archanid@users.noreply.github.com> Co-authored-by: Spencer <spalger@users.noreply.github.com> Co-authored-by: Court Ewing <court@epixa.com>
2018-07-11 10:19:35 +02:00
"hapi-latest": "npm:hapi@17.5.0",
Migrating vega_vis from plugin (#15014) Large PR to migrate Vega plugin into the core. https://github.com/nyurik/kibana-vega-vis The code underwent a large number of changes and reviews discussed in the PR thread: https://github.com/elastic/kibana/pull/15014
2018-01-13 21:14:04 +01:00
"hjson": "3.1.0",
Bump http-proxy-agent (#17840)
2018-05-01 22:52:55 +02:00
"http-proxy-agent": "^2.1.0",
"https-proxy-agent": "^2.2.1",
Upgrades Hapi to 14.2.0 As of Node 6, crypto.pbkdf emits a deprecation warning when the digest isn't explicily set. Under certain conditions we are seeing this warning from Hapi's dependency Iron. Iron resolved this issue as of 4.0.4, which was introduced into Hapi as of 14.0.0. Node deprecation: https://github.com/nodejs/node/pull/4047/commits/8e8959d3ee0bfe48b5f4d239e7f031a1a27708f0 Iron's resolution: https://github.com/hueniverse/iron/pull/43/commits/9e0a1ef5927c707fc79c5f2fa8c69a4b956897a4 As of Hapi v9, they have removed three build-in plugins from the core which we rely on inert (files and directories), vision (view templates), and h2o2 (proxy). https://github.com/hapijs/hapi/issues/2682 Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co>
2016-09-13 21:20:22 +02:00
"inert": "4.0.2",
[ftr] make room for more projects (#11848) Squashed commit of the following: commit 659ea986fdeb9a5ff2ca1fa5360cccb01c671ede Author: spalger <spalger@users.noreply.github.com> Date: Wed May 17 09:19:22 2017 -0700 [test/*/fixtures] rename es_archives to es_archiver commit d3667457c78e88e2d6974f3c38dd0fe61b846b91 Author: spalger <spalger@users.noreply.github.com> Date: Wed May 17 08:22:03 2017 -0700 [ftr/config] fix default directory value functions commit 9a6a2cc0b295e2281e83da04fcea40e9d6f00781 Author: spalger <spalger@users.noreply.github.com> Date: Wed May 17 07:30:52 2017 -0700 fix import paths commit fcb65a877d54b5b1d36b8c81f1264b36845e826e Author: spalger <spalger@users.noreply.github.com> Date: Tue May 16 21:39:57 2017 -0700 [grunt/ftr] use named exports for configs commit 7d7f38c7615cdbf8eb0119efc0f2a5188bca8792 Author: spalger <spalger@users.noreply.github.com> Date: Tue May 16 18:50:04 2017 -0700 [test] remove unnecessary directory definitions commit 0c28984669768482f0a2ee7fc2800d5bcaf49025 Author: spalger <spalger@users.noreply.github.com> Date: Tue May 16 18:46:29 2017 -0700 [ftr/config] make default directories relative to config path commit cd2f33612624cacffec138797f3fc0f4ecb46cca Author: spalger <spalger@users.noreply.github.com> Date: Tue May 16 18:32:12 2017 -0700 [test/common] put server config into common commit 7851ed811a236576c63bd20850b3ef2099be2a4e Author: spalger <spalger@users.noreply.github.com> Date: Tue May 16 18:18:20 2017 -0700 [grunt] "deprecate" test:api:runner task commit b2ac4c26593a1947c94f0168191fe8123ff74122 Author: spalger <spalger@users.noreply.github.com> Date: Tue May 16 18:15:41 2017 -0700 [ftr] accept the project name as an unnamed arg commit 47e292894fc70c0a04883403c50c5d2ae0738d76 Author: spalger <spalger@users.noreply.github.com> Date: Tue May 16 17:56:34 2017 -0700 [ftr/grunt] convert ftr task to multi-task with config commit 83375855f88e5e7b3fa8b6a1c5d24a9f54766ce5 Author: spalger <spalger@users.noreply.github.com> Date: Tue May 16 17:54:54 2017 -0700 [test/functional] move fixtures into test/functional project commit 05994e9c92cf134c58f831c285b3b522a801acbc Author: spalger <spalger@users.noreply.github.com> Date: Tue May 16 17:02:51 2017 -0700 [src/test_utils] merge with test/utils directory commit c77ee5ed36b8b7eadf876cb6d9482a49dfc92b66 Author: spalger <spalger@users.noreply.github.com> Date: Tue May 16 16:53:00 2017 -0700 [test/api_integration] migrate api tests to functional test runner commit ca328c34648dd7e07f70e1844e07cfc392e41103 Author: spalger <spalger@users.noreply.github.com> Date: Tue May 16 16:50:12 2017 -0700 [esArchiver] refresh modified indices after load commit cde74a540850fd97578f441d6dccaefd1444e656 Author: spalger <spalger@users.noreply.github.com> Date: Tue May 16 16:46:48 2017 -0700 [test/functional] move shared services into test/common commit 0ea2646aea5817f6d1595e6ae0d356c426f138f0 Author: spalger <spalger@users.noreply.github.com> Date: Mon May 15 22:51:23 2017 -0700 [scripts/mocha] run _mocha script when debugging commit 1cc80600d90e318d4738920aa557d124075a4570 Author: spalger <spalger@users.noreply.github.com> Date: Mon May 15 22:48:12 2017 -0700 [ftr/config] allow child config files to have no testFiles config commit 2bb6c957443b18cebc419baa6f9db301c8f4dc4f Author: spalger <spalger@users.noreply.github.com> Date: Mon May 15 21:52:26 2017 -0700 [ftr] move screenshots into test/functional
2017-05-18 03:53:45 +02:00
"joi": "10.4.1",
Bump jquery to ^3.3.1 (#16472) * Bump jquery to ^3.3.1
2018-02-02 11:53:28 +01:00
"jquery": "^3.3.1",
[npm] remove package ranges Fixes #4866 As recently discussed in https://github.com/elastic/kibana/issues/4824 we have had a fair number of challenges with dependencies shipping breaking changes or broken code within the semver ranges which should prevent them. Nobody is perfect, we don't expect that, but as Kibana grows the number of modules does too. The output of npm ls is currently over 1100 lines, meaning we are very exposed to the semver ranges specified. While we may actually use a shrinkwrap file at some point, or implement something like uber's custom shrinkwrap utility, the only issues we have faced have been caused by top level dependencies (especially the very fast-moving ones).
2015-09-05 10:49:36 +02:00
"js-yaml": "3.4.1",
Migrating vega_vis from plugin (#15014) Large PR to migrate Vega plugin into the core. https://github.com/nyurik/kibana-vega-vis The code underwent a large number of changes and reviews discussed in the PR thread: https://github.com/elastic/kibana/pull/15014
2018-01-13 21:14:04 +01:00
"json-stringify-pretty-compact": "1.0.4",
[npm] remove package ranges Fixes #4866 As recently discussed in https://github.com/elastic/kibana/issues/4824 we have had a fair number of challenges with dependencies shipping breaking changes or broken code within the semver ranges which should prevent them. Nobody is perfect, we don't expect that, but as Kibana grows the number of modules does too. The output of npm ls is currently over 1100 lines, meaning we are very exposed to the semver ranges specified. While we may actually use a shrinkwrap file at some point, or implement something like uber's custom shrinkwrap utility, the only issues we have faced have been caused by top level dependencies (especially the very fast-moving ones).
2015-09-05 10:49:36 +02:00
"json-stringify-safe": "5.0.1",
"jstimezonedetect": "1.0.5",
Upgrade kibana to leaflet 1.x (#12367) * upgrade leaflet modules to 1.x latest * fix css for leaflet controls * update draw options so it is easier to see polygon when drawing * fix chrome touch issues with closing polygon in leaflet draw * use canvas renderer * use leaflet-responsive-popup to avoid tooltip cutoff * remove radius configuration from leaflet heatmap * make blur a factor of radius. Set maxZoom to map zoom since new values are calculated per precision * use _.get to avoid error, cannot read property of undefined * add cluster size slider * experiments with image differences * onload not onLoad * use canvas dimensions * compare map canvas to stored PNG of map canvas * remove pixelmatch from project dependecies * fix broken test - rounding error * add expected image tests for geohash layers shaded circles and geohash grids * bump z-index of vis-spy * update functional test expected data * update to leaflet 1.2.0 * revert to leaflet 1.0.3 and update expected data set for map functional tests * test geohash_layer heatmap in unit test * update region_map functional test since it can not longer pluck map vectors from DOM * update documentation
2017-08-23 01:26:30 +02:00
"leaflet": "1.0.3",
"leaflet-draw": "0.4.10",
"leaflet-responsive-popup": "0.2.0",
Bumped Vega lib version to 3.3.1 (#17829) Turns out there is a significant problem with how Vega library manages its dependencies. Instead of using a fairly common "^1.2.3" form, it used "1" (major only) almost everywhere. While this works fine if node_modules and yarn.lock are deleted and rebuilt, bumping Vega lib's primary version in our package.json and using yarn install would not touch other subcomponents. This resulted in several 6.2 and 6.3 shipping with the outdated vega dependencies while we thought that we included the latest vega versions The problem has been reported vega/vega#1259 and will hopefully be solved with the next version. In the mean time, this patch updates all vega-related dependencies in the yarn.lock file.
2018-04-26 00:31:16 +02:00
"leaflet-vega": "^0.8.6",
Eui/38 (#17616) Bumped up the EUI version to 0.0.38
2018-04-09 20:08:53 +02:00
"leaflet.heat": "0.2.0",
[webpack] fix loader query string usage (#9497) * [webpack] pin to fork with fixed loader aliases * [optimizer] upgrade to postcss+autoprefixer * [timelion] convert uiExports.modules -> webpackShims * [uiExports] remove implementation-leaking and unused uiExport types * [optimizer] remove unused imports * [uiBundlerEnv] add a method for exporting global import aliases for special cases
2016-12-16 00:11:42 +01:00
"less": "2.7.1",
Upgrade to webpack 3 (#14315) * [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
2017-11-01 00:31:22 +01:00
"less-loader": "4.0.5",
[npm] remove package ranges Fixes #4866 As recently discussed in https://github.com/elastic/kibana/issues/4824 we have had a fair number of challenges with dependencies shipping breaking changes or broken code within the semver ranges which should prevent them. Nobody is perfect, we don't expect that, but as Kibana grows the number of modules does too. The output of npm ls is currently over 1100 lines, meaning we are very exposed to the semver ranges specified. While we may actually use a shrinkwrap file at some point, or implement something like uber's custom shrinkwrap utility, the only issues we have faced have been caused by top level dependencies (especially the very fast-moving ones).
2015-09-05 10:49:36 +02:00
"lodash": "3.10.1",
[optimize] inject publicPath at request time (#14007) * [optimize] inject publicPath at request time * [optimize/getFileHash] finish doc block * [optimize/bundlesRoute] correct return value doc type * [optimize/bundleRoute] use more descriptive name for file hash cache * [optimize/dynamicAssetResponse] add more details to doc * [utils/createReplaceStream] trim the buffer based on the length of toReplace, not replacement * [utils/createReplaceStream] add inline docs * [utils/createReplaceStream] write unit tests * [optimize/bundleRoute] expect supports buffers * [optimize/bundleRoute/basePublicPath/tests] add happy path * [optimize/bundlesRoute/tests] verify content-type header * [optimize/bundlesRoute] use '
2017-10-03 10:51:59 +02:00
"lru-cache": "4.1.1",
Update markdown-it to 8.4.1 (#19470)
2018-05-28 16:52:04 +02:00
"markdown-it": "^8.4.1",
Updating minimatch (#21050)
2018-07-27 13:30:17 +02:00
"minimatch": "^3.0.4",
[npm] remove package ranges Fixes #4866 As recently discussed in https://github.com/elastic/kibana/issues/4824 we have had a fair number of challenges with dependencies shipping breaking changes or broken code within the semver ranges which should prevent them. Nobody is perfect, we don't expect that, but as Kibana grows the number of modules does too. The output of npm ls is currently over 1100 lines, meaning we are very exposed to the semver ranges specified. While we may actually use a shrinkwrap file at some point, or implement something like uber's custom shrinkwrap utility, the only issues we have faced have been caused by top level dependencies (especially the very fast-moving ones).
2015-09-05 10:49:36 +02:00
"mkdirp": "0.5.1",
[yarn] remove locked moment resolution (#16418) * [yarn] remove locked moment resolution * [yarn] upgrade moment to latest minor upgrade * [kibana/fieldFormats/date] fix test, see https://github.com/elastic/kibana/pull/16256#issuecomment-360592151 * [ui/timepicker] fix test to have valid date
2018-01-31 19:16:36 +01:00
"moment": "^2.20.1",
"moment-timezone": "^0.5.14",
Kibana Home page - phase two (#14749) * add tutorial directory and home promo section * tutorial components * use KuiCodeEditor for displaying instruction code * move spec files to server so joi can be used. Fetch via rest API * Adding more tutorials (#4) * More edits on the Apache logs tutorial * Added nginx, mysql, and sytem modules for FB * Moved apache to apacheLogs and added an apacheMetrics tutorial * Added mysqlMetrics, nginxMetrics, systemMetrics tutorials * Reduce duplication in the tutorials This uses common objects for the install and start steps for Filebeat. Same can be done for MB. * fix windows path for config file * add markdown parsing * use mustache to replace config.kibana.version with kibana version * add image preview to tutorial introduction * fix css class name * add param types constants * add docs variables * [WIP] Logstash Netflow module tutorial (#5) * First draft of Logstash Netflow module tutorial * Incorporated writing style suggestions * pass params to template replace logic * parameter inputs * use isReadOnly flag from ui-framework for KuiCodeEditor * dedemorton commits on netflow * remove trailing slash from base links * add config.docs.logstash and fix vertical spacing between Content component and commands * Use logstash docs config variable * Starting to add Deb instructions * Fix Logstash documentation link * Make commands optional * Refactor: extract common LS instructions * Edits for the existing tutorials * change schema to support three instruction types * [Netflow tutorial] Simplify OSX instructions * replace axios with fetch * pass credentials to tutorial fetch * display cloud instructions when cloud set * RadioButtonGroup component * update copy * add tutorial component jest tests * content component test * load isCloudEnabled in home_app * add functional test ensuring add data tutorials are fetch and displayed * rename card btns to 'Add data', fix type in tutorial directory tab, remove 'Set up index pattern from tutorial directory' * move parameters form to right of instruction set title * add copy snippet button, remove line numbers from command block * add breadcrumb to tutorial view * update tutorial jest snapshot * use componentDidMount and ignore async results if componenent has been unmounted * define shape of prop for instructionVariants and params. Create NumberParameter and StringParameter components * add bread crumb to add data directory page * Add cloud version of the apache_logs tutorial (#16) * Add cloud version of the apache_logs tutorial * Added onprem-cloud version as well * fix styling broken by EUI rebase * add artifacts to tutorial schema * fix styling for code block * [Tutorials] Netflow: instructions for onPremCloud (#18) * Extract common on-prem cloud instructions so LS and Beats can share them * Extracting common instructions; adding onPremCloud instructions * fix copy bug where copy would only contain previously selected text * make string parameter input type be text * Implementing Elastic Cloud tutorial for Netflow module (#19) * More tutorial edits (#20) * More tutorial edits This updates the on prem instructions with a step that installs the GeoIP and UA plugins in ES. It also makes the on-prem steps more consistent with the cloud instructions which results in less redundancy in the code. * Show config step for all variants * More DRY in the tutorial content * Updated screenshot for apache_logs * wrap markdown content in markdown-body class * use EuiFlexGroup to remove wasted space with 'copy snippet' button and instruction text * change OSX to macOS, use Computed property names for instruction_variant DISPLAY_MAP, replace /app/kibana with kbnBaseUrl, remove unneeded if check in copy_to_clippboard, put getTutorials mixin on server instead of request * capitilize 'C' in Elastic Cloud * remove try/catch from copy_to_clipboard * Removing unrelated instructions * Copy editing fixes * Multiply edits to the Beats tutorials (#21) * Updated Nginx module * Updated MySQL logs module * Updated system logs module * Correct the on_prem_cloud enable steps * Updated the Nginx metrics tutorial and added screenshot * Updated the Apache metrics module + screenshot * Updated the MySQL metrics module + screenshot * Updated the system metrics module + screenshot * prevent 'Copy snippet' button text from wrapping * [Netflow tutorial] Windows instructions (#22) * [Netflow tutorial] Adding onPrem instructions for Windows * Removing unrelated/superfluous instructions * Adding Windows instructions for onPremElasticCloud and elasticCloud * use EuiImage so tutorial images are clickable to view in full screen * fix jest tests * set fullScreenIconColor and alt options for EuiImage, add space between command block and instruction text
2018-01-10 15:20:38 +01:00
"mustache": "2.3.0",
Adding a `fetch` polyfill (#15968) * Adding a `fetch` polyfill * "globally" shimming the whatwg-fetch
2018-01-10 20:26:02 +01:00
"ngreact": "0.5.1",
Add Tag Cloud Visualization A tag cloud visualization is a visual representation of text data, typically used to visualize free form text. Tags are usually single words. The font size of word corresponds with its importance.
2016-11-21 23:03:25 +01:00
"no-ui-slider": "1.2.0",
[optimizer] move to querystring-browser package for up-to-date api Webpack automatically injects libraries to support many node.js APIs in the browser using the https://github.com/webpack/node-libs-browser package. This package uses https://github.com/mike-spainhower/querystring for the querystring module, but that module hasn't been updated in 4 years and doesn't support the modern querystring api. This change points to the https://github.com/mathiasvr/querystring package instead, which is up to date (specifically it supports the `encodeURIComponent` option of [`querystring.stringify`](https://nodejs.org/api/querystring.html#querystring_querystring_stringify_obj_sep_eq_options).
2016-09-09 23:10:50 +02:00
"node-fetch": "1.3.2",
"pegjs": "0.9.0",
Upgrade to webpack 3 (#14315) * [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
2017-11-01 00:31:22 +01:00
"postcss-loader": "2.0.6",
UiFramework: Modals in react (#11500) * Reactify the confirmation modal Up next: jest tests * Add tests - Relies on https://github.com/elastic/kibana/pull/10821 getting checked in first for commonHtmlProps * Don't include the overlay as part of the confirm modal component * Use the react version of a confirmation modal - Can’t use the modalOverlay or it would be two nested react roots, due to the way it’s embedded in angular. * Add snapshots * Fix tests * fix confirm_modal_promise tests I have no idea why the introduction of react would cause this to fail as it was, but for some reason, grabbing the button reference has to be after the digest loop. * Address code review comments * switch over the remaining React.PropType references (in the modals dir anyway)
2017-05-03 15:44:31 +02:00
"prop-types": "15.5.8",
[npm] move personal forks into elastic org (#13410)
2017-08-09 21:31:30 +02:00
"proxy-from-env": "1.0.0",
Switching from jade to pug (#21047) * Upgrading pug * Switching .jade to .pug and fixing templates * Renaming the I18N usages of jade to pug * No more jade in I18N
2018-07-27 13:21:27 +02:00
"pug": "^2.0.3",
[optimizer] move to querystring-browser package for up-to-date api Webpack automatically injects libraries to support many node.js APIs in the browser using the https://github.com/webpack/node-libs-browser package. This package uses https://github.com/mike-spainhower/querystring for the querystring module, but that module hasn't been updated in 4 years and doesn't support the modern querystring api. This change points to the https://github.com/mathiasvr/querystring package instead, which is up to date (specifically it supports the `encodeURIComponent` option of [`querystring.stringify`](https://nodejs.org/api/querystring.html#querystring_querystring_stringify_obj_sep_eq_options).
2016-09-09 23:10:50 +02:00
"querystring-browser": "1.0.4",
[npm] remove package ranges Fixes #4866 As recently discussed in https://github.com/elastic/kibana/issues/4824 we have had a fair number of challenges with dependencies shipping breaking changes or broken code within the semver ranges which should prevent them. Nobody is perfect, we don't expect that, but as Kibana grows the number of modules does too. The output of npm ls is currently over 1100 lines, meaning we are very exposed to the semver ranges specified. While we may actually use a shrinkwrap file at some point, or implement something like uber's custom shrinkwrap utility, the only issues we have faced have been caused by top level dependencies (especially the very fast-moving ones).
2015-09-05 10:49:36 +02:00
"raw-loader": "0.5.1",
Update React to 16.3 (#18768) * Update React to 16.3 * Switch off specific eslint rules * Update enzyme snapshots * Incorporate PR feedback
2018-05-14 14:05:17 +02:00
"react": "^16.3.0",
Remove pivotal-ui (#17181) * remove from input controls * remove from tutorial * remove from visual builder * update package.json
2018-03-16 16:59:59 +01:00
"react-addons-shallow-compare": "15.6.2",
[npm] upgrade react-anything-sortable (#17217) Now that https://github.com/jasonslyvia/react-anything-sortable/pull/93 is merged and released we can upgrade our version and get rid of the incompatibility warning
2018-03-28 21:33:17 +02:00
"react-anything-sortable": "^1.7.4",
Upgrade react deps (#16025) * [yarn] upgrade react deps * [yarn] reinstall pivotal-ui so that react dep is deduped * [yarn] remove unused deps * [react-ace] update snapshots to include new aria props * [react-input-range] update snapshot with new allowSameValues prop, default is still false * [react-select] update snapshots with new default from features added since 1.0.0-rc5
2018-01-17 10:14:12 +01:00
"react-color": "^2.13.8",
Update React to 16.3 (#18768) * Update React to 16.3 * Switch off specific eslint rules * Update enzyme snapshots * Incorporate PR feedback
2018-05-14 14:05:17 +02:00
"react-dom": "^16.3.0",
Upgrade react deps (#16025) * [yarn] upgrade react deps * [yarn] reinstall pivotal-ui so that react dep is deduped * [yarn] remove unused deps * [react-ace] update snapshots to include new aria props * [react-input-range] update snapshot with new allowSameValues prop, default is still false * [react-select] update snapshots with new default from features added since 1.0.0-rc5
2018-01-17 10:14:12 +01:00
"react-grid-layout": "^0.16.2",
"react-input-range": "^1.3.0",
"react-markdown": "^3.1.4",
Update redux, ,react-redux and corresponding types (#22442)
2018-08-29 13:18:46 +02:00
"react-redux": "^5.0.7",
Kibana Home page - phase one (#14673) * make kibana home app default when defaultAppId not set * make kibana icon link to home page, add react-router for routing within home app * directory registry * add href to directory listings * add tabs to directory page * add promo section to home page * home page styling * use kuiFlex components to display directory in columns * fix react array missing key warning * add icons * remove feature directory title from home page, change data sources to integrations * add tutorials registry * fix rebase mistake * start tutorial component * wrap tutorial registration in helper function to hide implemenation details * add constants for categry and instruction variant ids * filter tutorial directory by tab category * remove later phase stuff * clean-up feature directory styling * add kbnDirectory to uiExports * remove unused file * cleanup timelion plugin definition * fix lint errors * css work recommended by formgeist review * cleanup from pairing session with snide * rename kbnDirectory registry to featureCatalogue, rename kbnDirectory uiExports to home * update kibana index uses name to match ui-exports name * remove carot from package versions * remove kuiViewContent--constrainedWidth from feature directory view * updates from Stacey-Gammon review * import FeatureCatalogueCategory instead of passing as parameter * wrap KuiButton in href to fix button click bug * remove conditional check for ADMIN and DATA feature category tabs * consider apps for the 'OTHER' tab as anything not in ADMIN or DATA * remove temp variable tabs and just store in this * avoid overwriting kui class styles * prefix class names with home * updates from timroes review
2017-11-02 19:58:46 +01:00
"react-router-dom": "4.2.2",
Upgrade react deps (#16025) * [yarn] upgrade react deps * [yarn] reinstall pivotal-ui so that react dep is deduped * [yarn] remove unused deps * [react-ace] update snapshots to include new aria props * [react-input-range] update snapshot with new allowSameValues prop, default is still false * [react-select] update snapshots with new default from features added since 1.0.0-rc5
2018-01-17 10:14:12 +01:00
"react-sizeme": "^2.3.6",
Upgrade to react 16.0.0 (#15469) * get kibana to start with react 16.0.0 * ensure width and height for dashboard grid * Update to Enzyme 3.x. (#12) * Fix tests broken by Enzyme upgrade (#13) * Update to Enzyme 3.x. (#12) * Add findTestSubject test helper. Fix KuiCodeEditor tests. * Fix KuiContextMenu tests. * Fix KuiConfirmModal tests. * Fix tests for KuiPager. * Update KuiConfirmModal tests to use findTestSubject helper. * Publish test helpers from ui_framework. Fix DashboardCloneModal tests. * Fix more tests (#14) * Fix DashboardPanelContainer tests. * Update KuiColorPicker tests. * Fix ControlsTab tests. * Rename vis to input_control_vis. Update and fix InputControlVis tests. * Fix KuiListingTable tests. * Fix KuiTextInput tests. * Update DashboardGrid test snapshots. * Fix test file names (#15) * Remove old enzyme setup file. * Add .test to YesNo and AddDeleteButtons test files. * needed window.cancelAnimationFrame to accompany requestAnimationFrame * remove getDOMNode function call from findTestSubject
2017-12-11 22:02:39 +01:00
"react-toggle": "4.0.2",
"reactcss": "1.2.3",
Update redux, ,react-redux and corresponding types (#22442)
2018-08-29 13:18:46 +02:00
"redux": "4.0.0",
Introduce redux into dashboard (#14518) * Initial check in of introducing redux in dashboard * Use redux-actions and redux-thunks to reduce boilerplate * Make sure all panels are minimized from the start when a dashboard is loaded - we don't want a panel id from a different dashboard in the state tree on a fresh open. * Remove unused file * use classnames dependency instead of manual logic * First pass on selectors, handleActions, and more segmented reducers. * Fix bugs with selectors and reducers and add tests that would have caught them. * Fix issue plus tests discover was not returning a promise * Make expanding a panel purely a css modification which avoids all re-renders * Found another bug with initial state not being set correctly on a hard refresh * Remove check for change handlers now that the event handler bug is fixed * rename dashboardState => dashboard for reducers and redux state tree * Remove unnecessary top level describe in jest tests * Navigate back to landing page at the end of the newly added test suite * Fix lint errors * Stabilize flaky tests by waiting until saved object search is finished loading results * Don't leak subscriptions to the store. * use selectors to grab dashboard panel off state. * Remove use of getState in dispatcher to avoid circular reference and still use selectors * use spread over object.assign * No need to pass second param in when the input is simply returned as-is.
2017-10-23 22:39:23 +02:00
"redux-actions": "2.2.1",
Update redux, ,react-redux and corresponding types (#22442)
2018-08-29 13:18:46 +02:00
"redux-thunk": "2.3.0",
Table Visualization for TSVB (#12813) * Adding table vis * Making linter happy * Getting the data api inline * Fixing aggs for table vis * Fixing aggs for table vis * Adding table vis * Adding uiState and sorting * Adding sorting * Adding sorting and removing display fields * fixing color picker in timeseries and gauge; thresholds for trend arrows * Removing thresholds from trends * removing background color * remvoing obsolete tests * Fixing terminology... pivot doesn't make sense * updating error message * making the sort icons match the rest of the app * Fixing eslint bullshit * Fixing a few bugs from merges * Fixing linting issues * Adding a falsy check * Adding aria labels * Changing toggle to use a button * Adding focus-ring back in * Adding check for model and visData; they should never be null * Changing ids to use new htmlIdGenerator function * Switching to htmlIdGenerator * Fixing the way sorting works; fixing the error handling * making no data compatible with vis * Fixing defaults bug; Adding missing css rule * Fixing sorting bug
2017-10-25 00:45:57 +02:00
"regression": "2.0.0",
Updating request to 2.85.0 (#17592) * Updating request to 2.85.0 * Adding the caret * updating the yarn.lock
2018-04-17 19:57:52 +02:00
"request": "^2.85.0",
React/EUI-ify indexed fields table (#16695) * React/EUI-ifying indexed fields table
2018-03-09 17:09:54 +01:00
"reselect": "^3.0.1",
[ui/resize_checker] extract from vislib and use resize-observer polyfill (#9439)
2017-03-03 23:33:07 +01:00
"resize-observer-polyfill": "1.2.1",
[npm] remove package ranges Fixes #4866 As recently discussed in https://github.com/elastic/kibana/issues/4824 we have had a fair number of challenges with dependencies shipping breaking changes or broken code within the semver ranges which should prevent them. Nobody is perfect, we don't expect that, but as Kibana grows the number of modules does too. The output of npm ls is currently over 1100 lines, meaning we are very exposed to the semver ranges specified. While we may actually use a shrinkwrap file at some point, or implement something like uber's custom shrinkwrap utility, the only issues we have faced have been caused by top level dependencies (especially the very fast-moving ones).
2015-09-05 10:49:36 +02:00
"rimraf": "2.4.3",
[internal] Use rison dependency rather than hardcoding Rison was already pulled out into an npm module so it could be reused in the reporting plugin, so this should essentially be a noop on the resulting source. The rison file was originally copied and pasted directly into the Kibana project, so it doesn't match our styleguide and is unlintable. This means we basically have to keep our hands off of it. The node module also has the benefit of including some tests.
2016-04-15 23:58:20 +02:00
"rison-node": "1.0.0",
Upgrade `rxjs`: `6.1.0` ---> `6.2.1`. (#20209)
2018-06-25 20:04:19 +02:00
"rxjs": "^6.2.1",
Upgrade to webpack 3 (#14315) * [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
2017-11-01 00:31:22 +01:00
"script-loader": "0.7.2",
Validate current node version (#19154) * feat(12976): node version validation at runtime. * refact(12976): move the code into a static utilities class. * test(12976): added first test case using jest. * test(12976): added test cases for node_version. * feat(12976): create setup env node to bootstrap babel, ts-node and node version validator. * refact(12976): migrated node version code from es6 to es5. * feat(12976): node version validation at runtime. * refact(12976): move the code into a static utilities class. * test(12976): added first test case using jest. * test(12976): added test cases for node_version. * feat(12976): create setup env node to bootstrap babel, ts-node and node version validator. * refact(12976): migrated node version code from es6 to es5. * fix(12976): remove one level from ts node register cache directory link. * chore(12976): added caret to semver dependecy in order to support minor versions. * refact(12976): small change from named import to default import on node version validator. * refact(12976): removed ts_node_register and add the code to babel_register. * feat(12976): split eslint config in order to properly support files built to run before and after node version validator. refact(12976): convert script files to es5 code. refact(12976): delete inline eslint configs from node version check related files. * refact(12976): remove ts node register file. * refact(12976): completely port setup_node_env to es5. * refact(12976): remove babel_register invokation from external dependencies in scripts. * refact(12976): move node_version code directly into node_version_validator inside setup_node_env folder. * refact(12976): only node version validator for kbn script.
2018-05-25 19:43:01 +02:00
"semver": "^5.5.0",
Upgrade to webpack 3 (#14315) * [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
2017-11-01 00:31:22 +01:00
"style-loader": "0.19.0",
[npm] remove package ranges Fixes #4866 As recently discussed in https://github.com/elastic/kibana/issues/4824 we have had a fair number of challenges with dependencies shipping breaking changes or broken code within the semver ranges which should prevent them. Nobody is perfect, we don't expect that, but as Kibana grows the number of modules does too. The output of npm ls is currently over 1100 lines, meaning we are very exposed to the semver ranges specified. While we may actually use a shrinkwrap file at some point, or implement something like uber's custom shrinkwrap utility, the only issues we have faced have been caused by top level dependencies (especially the very fast-moving ones).
2015-09-05 10:49:36 +02:00
"tar": "2.2.0",
[optimizer] move to querystring-browser package for up-to-date api Webpack automatically injects libraries to support many node.js APIs in the browser using the https://github.com/webpack/node-libs-browser package. This package uses https://github.com/mike-spainhower/querystring for the querystring module, but that module hasn't been updated in 4 years and doesn't support the modern querystring api. This change points to the https://github.com/mathiasvr/querystring package instead, which is up to date (specifically it supports the `encodeURIComponent` option of [`querystring.stringify`](https://nodejs.org/api/querystring.html#querystring_querystring_stringify_obj_sep_eq_options).
2016-09-09 23:10:50 +02:00
"tinygradient": "0.3.0",
[TSVB] Math Aggregation (two point oh) (#16965) * Revert "Remove MathJS Feature (#15652)" This reverts commit 43bf1dbf4a258ae4453d9da2c18019e22a8b9070. * replacing math with tinymath * pining version * updating yarn.lock * Fixing Prettier mis formatting * fixing tests * Adding unsupported agg back * Adding functional test for math aggregation - Fixing bad tests - Resetting page for every test suite (why donesn't beforeEach work?) - Adding test for Math agg * Trying to fix values (due to inconsistencies in env)
2018-04-11 23:06:28 +02:00
"tinymath": "0.2.1",
Add topojson support / EMS v3 support (#15361) This adds support for the v3 endpoint of the Elastic Maps Service. This includes support for Topojson files.
2018-01-16 21:30:52 +01:00
"topojson-client": "3.0.0",
[feature/custom-banner] Added a custom banner feature in advanced settings. Fixes #4452.
2016-04-05 23:56:45 +02:00
"trunc-html": "1.0.2",
"trunc-text": "1.0.2",
[ts] enable support for iterators in browsers (#22986) I was surprised when I tried to spread a `Set` in TypeScript and the browser complained about `Set.slice()` not being defined. This is because TypeScript does not automatically enable support for iterators when targeting earlier ES versions, like we do in the browser, unless you use the `"downlevelIteration": true` compiler option. This injects some helpers into the necessary files for reading/spreading iterators, which can be stuffed behind an import statement with using the `"importHelpers": true` compiler option and include `tslib` in our dependencies. This is already a dependency of several of our packages, so it shouldn't cause any additional modules.
2018-09-13 23:18:13 +02:00
"tslib": "^1.9.3",
Integrate new platform (core) server side into Kibana (#18951) Co-authored-by: Kim Joar Bekkelund <kjbekkelund@gmail.com> Co-authored-by: archana <archanid@users.noreply.github.com> Co-authored-by: Spencer <spalger@users.noreply.github.com> Co-authored-by: Court Ewing <court@epixa.com>
2018-07-11 10:19:35 +02:00
"type-detect": "^4.0.8",
Upgrade uglifyJS webpack plugin, disabling compress and enabling parallel (#21809)
2018-08-09 01:00:14 +02:00
"uglifyjs-webpack-plugin": "^1.2.7",
Use ui-select for index pattern selector (#10144) * Replace index pattern selector with ui-select * Show index patterns in alphabetical order * Add highlighting to select
2017-03-31 20:37:10 +02:00
"ui-select": "0.19.6",
Upgrade to webpack 3 (#14315) * [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
2017-11-01 00:31:22 +01:00
"url-loader": "0.5.9",
Replace node-uuid with uuid (#12209) * replace node-uuid with uuid package * fix all the uuid call sites
2017-06-07 00:15:53 +02:00
"uuid": "3.0.1",
[uiExports] migrate uiApp "uses" to explicit imports in apps (#17828) * [uiExports] migrate uiApp "uses" to explicit imports in apps * [uiApp] update tests for getModules() method * [optimize/uiExports] improve naming and comments * [uiExports] sort imports so they load in the same order as before * [testHarness] load hacks when testing in the browser * [x-pack/uiExports] use new uiExports modules * [testHarness] describe why we import uiExports/hacks * [optimize] remove needless [].concat() * [optimize/createUiExportsModule] string.includes > string.indexOf * [uiExports/createUiExportsModule] remove needless capture of module exports
2018-05-03 21:18:50 +02:00
"val-loader": "^1.1.0",
[pack installer] various tweaks from PR review
2016-03-04 16:31:58 +01:00
"validate-npm-package-name": "2.2.2",
Bumped Vega lib version to 3.3.1 (#17829) Turns out there is a significant problem with how Vega library manages its dependencies. Instead of using a fairly common "^1.2.3" form, it used "1" (major only) almost everywhere. While this works fine if node_modules and yarn.lock are deleted and rebuilt, bumping Vega lib's primary version in our package.json and using yarn install would not touch other subcomponents. This resulted in several 6.2 and 6.3 shipping with the outdated vega dependencies while we thought that we included the latest vega versions The problem has been reported vega/vega#1259 and will hopefully be solved with the next version. In the mean time, this patch updates all vega-related dependencies in the yarn.lock file.
2018-04-26 00:31:16 +02:00
"vega-lib": "^3.3.1",
"vega-lite": "^2.4.0",
Migrating vega_vis from plugin (#15014) Large PR to migrate Vega plugin into the core. https://github.com/nyurik/kibana-vega-vis The code underwent a large number of changes and reviews discussed in the PR thread: https://github.com/elastic/kibana/pull/15014
2018-01-13 21:14:04 +01:00
"vega-schema-url-parser": "1.0.0",
[typescript] add typescript support for the server and browser (#19104) * [typescript] add typescript support for the server and browser * [ts-jest] upgrade to latest version * [jest] support test.tsx files * [jest/ts] modify `ts-jest.tsConfigFile` config based on filePath * [types] use correct major version of minimatch types * [jest] add ts support to x-pack jest config * [ts/projects] fix tsconfig.json not found error message * [optimizer/ts] use lowercase jsx option * [tsconfig] remove ui/* alias * [plguin-helpers] remove mention of `buildSourcePatterns` * [plugin-helpers] expect typescript to be a devDep * [dev/build] place transpile tasks next to each other * [ts/x-pack] add common and server directories to ts project * [dev/ts/project] use a limited set of globs to find tsconfig files
2018-05-18 19:54:57 +02:00
"vega-tooltip": "^0.9.14",
Upgrades Hapi to 14.2.0 As of Node 6, crypto.pbkdf emits a deprecation warning when the digest isn't explicily set. Under certain conditions we are seeing this warning from Hapi's dependency Iron. Iron resolved this issue as of 4.0.4, which was introduced into Hapi as of 14.0.0. Node deprecation: https://github.com/nodejs/node/pull/4047/commits/8e8959d3ee0bfe48b5f4d239e7f031a1a27708f0 Iron's resolution: https://github.com/hueniverse/iron/pull/43/commits/9e0a1ef5927c707fc79c5f2fa8c69a4b956897a4 As of Hapi v9, they have removed three build-in plugins from the core which we rely on inert (files and directories), vision (view templates), and h2o2 (proxy). https://github.com/hapijs/hapi/issues/2682 Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co>
2016-09-13 21:20:22 +02:00
"vision": "4.1.0",
Upgrade to webpack 3 (#14315) * [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
2017-11-01 00:31:22 +01:00
"webpack": "3.6.0",
"webpack-merge": "4.1.0",
Adding a `fetch` polyfill (#15968) * Adding a `fetch` polyfill * "globally" shimming the whatwg-fetch
2018-01-10 20:26:02 +01:00
"whatwg-fetch": "^2.0.3",
[npm] Upgrage wreck (#13849)
2017-09-15 03:46:55 +02:00
"wreck": "12.4.0",
Migrate x-pack-kibana source to kibana
2018-04-20 21:13:37 +02:00
"x-pack": "link:x-pack",
Replaces zip library and small refactor of plugin install (#11145) Previously our plugin installation used over 5,000 file descriptors when analyzing and extracting the archive. To mitigate this, we are moving to a more supported zip library, Yauzl. In addition to the replacement of the zip library, this refactors the getPackData method. It was extracting the plugin package.json files, reading them, then finally deleting them. This commit performs this all in memory, removing the need for any file system operations during this step. These changes reduced the installation time by an average of 35%, from 211.18 seconds to 137.8 seconds. The majority of this time is now spent during optimize. Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co>
2017-04-11 21:58:38 +02:00
"yauzl": "2.7.0"
Consolidating package.json adding JSON logger
2015-01-07 21:48:58 +01:00
},
reorganized the projects a tad, included grunt tasks for testing and running the server. Includes incomplete Courier code for now.
2014-02-11 00:09:04 +01:00
"devDependencies": {
Implement a build tool for default messages extraction (#19620) * Implement a build tool for default messages extraction * Refactor extraction tool, resolve review comments, fix bugs * Resolve comments, refactor extraction tool, fix bugs * Add context to messages extraction tool * Resolve comments * Fix bugs * Add messages extraction from .jade files, refactor code * Add template literals parsing * Return defaultMessages.json to plain structure * Refactor utils * Fix bugs * Refactor code, resolve review comments, fix bugs * Fix minor bug * Get rid of '@babel/traverse' and add its native implementation * Add handlebars messages extraction * Fix mkdir on macOS * Fix bugs, inject default formats, finalize the tool * Fix filsystem permissions * Refactor nodes traversal * Update code style * Downgrade @babel/types to fix build issues * Resolve comments * Fix minor bugs
2018-07-17 14:56:55 +02:00
"@babel/parser": "7.0.0-beta.52",
"@babel/types": "7.0.0-beta.31",
Kibana build tool (#15055) * Introduce `kbn`, the Kibana build tool * yarn kbn * Make all deps devDeps * Exclude __fixtures__ folder from Jest to avoid warnings * Review fixes * Update readme * Use 'yarn kbn' * Consistent rootPath * Link to kbn tool * Unsupported URL 'debug help' in contributing guide
2018-01-24 10:34:52 +01:00
"@elastic/eslint-config-kibana": "link:packages/eslint-config-kibana",
"@elastic/eslint-plugin-kibana-custom": "link:packages/eslint-plugin-kibana-custom",
[kbn-es] Package for managing Elasticsearch during dev and testing (#17168) Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co>
2018-03-20 16:30:15 +01:00
"@kbn/es": "link:packages/kbn-es",
[eslint-import-resolver-kibana] bring in repo as package (#17665) * [eslint-import-resolver-kibana] bring in repo as package * [eslint-import-resolver] enable prettier
2018-04-12 00:21:29 +02:00
"@kbn/eslint-import-resolver-kibana": "link:packages/kbn-eslint-import-resolver-kibana",
Migrate x-pack-kibana source to kibana
2018-04-20 21:13:37 +02:00
"@kbn/eslint-plugin-license-header": "link:packages/kbn-eslint-plugin-license-header",
[kbn-plugin-generator] add plugin generator to the repo (#16655) * [kbn-plugin-generator] add plugin generator to the repo * [plugin-generator] use snake_case plugin name for directory name * [plugin-generator] fix typo * [plugin-generator] remove translation support until we resume i18n efforts * [yarn] update lockfile * [mocha] remove plugin-generator selector from mocha tests * [plugin-generator] update generated readme to recommend yarn * [plugin-generator] add readme to generator pacakge * [plugin-generator] link from plugin-resource docs * [plugin-generator] mention very important `kbn bootstrap` script * [plugin-generator] rework some parts of the README * [plugin-generator] log actual directory name with system separators * [plugin-generator] include bootstrap/yarn preinstall check script
2018-02-12 20:23:23 +01:00
"@kbn/plugin-generator": "link:packages/kbn-plugin-generator",
Functional test setup with kbn-test package (#18568) Restructure testing with kbn-test package - Run with multiple configs, move cli options to config - Package-ify kbn-test - Eventually we'll have functional_test_runner live in a package of its own, and then this kbn-test will use that as a dependency, probably still as a devDependency. - Implement functional_tests_server - Collapse single and multiple config apis into one command Use kbn-es Replace es_test_cluster + es_test_config with kbn/test utils Implement new createEsTestCluster Improve scripts, jsdocs, cli top-level tools Lift error handling to the top level
2018-05-10 01:23:49 +02:00
"@kbn/test": "link:packages/kbn-test",
Add jenkins:report task for test failures (#22682) * Add jenkins:report task * PR comments
2018-09-21 16:31:51 +02:00
"@octokit/rest": "^15.10.0",
Replace spy panels by Inspector (#16387) * Add Inspector feature * So long, and thanks for all the fish, spy panel * Fix several functional tests * Fix unit tests * Fix spy panel button tests * Replace old spy panel documentation * Disable test temporarily until we have dashboard triggers * Enter edit mode for dark theme test * Fix some more functional tests * Fix more functional tests * More test fixing * Fix more functional tests * Allow opening the inspector via loader handler * Refactor InspectorViewChooser, remove unused CSS * Remove dead code * Fix data download button style * Remove redundant code * Load inspectorViews for dashboard_viewer * Extract inspector views to custom core_plugin * Switch API to TypeScript :tada: * Design changes * Remove icons from views * Design changes * Improve typings of API * Add typing to all adapters * Show loading spinner in request selector * Rewrite InspectorView to TypeScript * Fix help text for data view * Remove deprecated React lifecycle methods * Embed inspector into dashboard panel actions * Remove temporary inspector trigger * Remove old CSS * Fix dashboard trigger for new panel action * Add tests for InspectorPanel and DataAdapter * Produce a hierarchical table if the vis is hierarchical * Remove allowJs option again * Add missing Apache license headers * Close inspector on dashboard when navigating away * Use proper title for dashboard panels * Fix functional tests * Skip broken test for now * Flush view chooser button * Add request adapter tests * Skip more tests, broken due to typescript * Add Request Time description * Add description for courier request * Fix tests * Replace icon by new (not yet released) icon * Finalize design of inspector * Remove discover test, that relied on spy panels * Change API to be properly mockable in tests * Add aria-live region for request status * Replace old method in functional tests * Replace abitrary magic number * Use object destructuring in vis * Fix issue with crashing requests view * Add request time tooltip * Get request body of correct search source * Make filter buttons properly keyboard accessible * Follow Dave's design suggestions * Remove redundant request from name * Remove unneeded comments * WIP raw-formatted values * Fix filtering issue * Fix tests and more license headers * Add data view tests * Remove search from table * Fix typos * Implement review suggestion * Remove artificial delays for testing * Fix new panel action structure * Minor design adjustments * Fix failing functional test * Update failing snapshot test * Implement final wording * Apply new EUI styling * Fix closing inspector in tests * Fix sorting of table * Align punctuation between tooltips
2018-06-20 11:07:44 +02:00
"@types/angular": "^1.6.45",
Typescript-ify screenshot stitcher code in reporting (#20061) * typescript screenshot stitcher * Throw an error if the data captured is not of the expected width and height. * Import babel-core types * Add babel-core types to x-pack package.json * Dimensions => Rectangle
2018-06-22 15:18:29 +02:00
"@types/babel-core": "^6.25.5",
"@types/bluebird": "^3.1.1",
Add saved object index migrations (#20243) Migrations are the mechanism by which saved object indices are kept up to date with the Kibana codebase. Plugin authors can write their plugins to work with a certain set of mappings. Migrations ensure that the index actually conforms to those expectations.
2018-09-17 20:24:32 +02:00
"@types/boom": "^7.2.0",
Integrate new platform (core) server side into Kibana (#18951) Co-authored-by: Kim Joar Bekkelund <kjbekkelund@gmail.com> Co-authored-by: archana <archanid@users.noreply.github.com> Co-authored-by: Spencer <spalger@users.noreply.github.com> Co-authored-by: Court Ewing <court@epixa.com>
2018-07-11 10:19:35 +02:00
"@types/chance": "^1.0.0",
Replace spy panels by Inspector (#16387) * Add Inspector feature * So long, and thanks for all the fish, spy panel * Fix several functional tests * Fix unit tests * Fix spy panel button tests * Replace old spy panel documentation * Disable test temporarily until we have dashboard triggers * Enter edit mode for dark theme test * Fix some more functional tests * Fix more functional tests * More test fixing * Fix more functional tests * Allow opening the inspector via loader handler * Refactor InspectorViewChooser, remove unused CSS * Remove dead code * Fix data download button style * Remove redundant code * Load inspectorViews for dashboard_viewer * Extract inspector views to custom core_plugin * Switch API to TypeScript :tada: * Design changes * Remove icons from views * Design changes * Improve typings of API * Add typing to all adapters * Show loading spinner in request selector * Rewrite InspectorView to TypeScript * Fix help text for data view * Remove deprecated React lifecycle methods * Embed inspector into dashboard panel actions * Remove temporary inspector trigger * Remove old CSS * Fix dashboard trigger for new panel action * Add tests for InspectorPanel and DataAdapter * Produce a hierarchical table if the vis is hierarchical * Remove allowJs option again * Add missing Apache license headers * Close inspector on dashboard when navigating away * Use proper title for dashboard panels * Fix functional tests * Skip broken test for now * Flush view chooser button * Add request adapter tests * Skip more tests, broken due to typescript * Add Request Time description * Add description for courier request * Fix tests * Replace icon by new (not yet released) icon * Finalize design of inspector * Remove discover test, that relied on spy panels * Change API to be properly mockable in tests * Add aria-live region for request status * Replace old method in functional tests * Replace abitrary magic number * Use object destructuring in vis * Fix issue with crashing requests view * Add request time tooltip * Get request body of correct search source * Make filter buttons properly keyboard accessible * Follow Dave's design suggestions * Remove redundant request from name * Remove unneeded comments * WIP raw-formatted values * Fix filtering issue * Fix tests and more license headers * Add data view tests * Remove search from table * Fix typos * Implement review suggestion * Remove artificial delays for testing * Fix new panel action structure * Minor design adjustments * Fix failing functional test * Update failing snapshot test * Implement final wording * Apply new EUI styling * Fix closing inspector in tests * Fix sorting of table * Align punctuation between tooltips
2018-06-20 11:07:44 +02:00
"@types/classnames": "^2.2.3",
[TypeScript] add type-check script (#19325) * [TypeScript] add type-check script * [ci] run scripts/type_check after linting * [ts] improve filterProjectsByFlag readability * fix typo * simplify type signature
2018-08-10 02:19:24 +02:00
"@types/dedent": "^0.7.0",
Migrate ui/notify/fatal_error to new platform (#20752) Fixes #20695 Extracts the "fatal error" handling logic from the `ui/notify` module and reimplements it in the new platform, using EUI for the fatal error page and continuing to support the `fatalError()` and `addFatalErrorCallback()` methods exported by the `ui/notify` module. ![image](https://user-images.githubusercontent.com/1329312/43032175-d37fbafc-8c65-11e8-8f1f-da71f0dac014.png)
2018-07-31 00:06:31 +02:00
"@types/enzyme": "^3.1.12",
[tslint] lint typescript code (#19105) * [tslint] lint typescript code * [tslint] filter projects when running specific project * [dev/ts] use more explicit types * [dev/ts] add note about why using glob * [dev/ts] rely on ts, use fewer getters
2018-05-22 23:00:02 +02:00
"@types/eslint": "^4.16.2",
"@types/execa": "^0.9.0",
[kfetch] TypeScript-ify (#20914) In order to make the awesome new kfetch api easier to consume in purely TypeScript projects, and since it's a pretty small module with very few dependencies, I converted it to TypeScript. Along with kfetch I also started a type definition file for `ui/chrome` that we can extend as we go, but will likely be unnecessary after #19992
2018-07-19 15:31:44 +02:00
"@types/fetch-mock": "^5.12.2",
[tslint] lint typescript code (#19105) * [tslint] lint typescript code * [tslint] filter projects when running specific project * [dev/ts] use more explicit types * [dev/ts] add note about why using glob * [dev/ts] rely on ts, use fewer getters
2018-05-22 23:00:02 +02:00
"@types/getopts": "^2.0.0",
"@types/glob": "^5.0.35",
Integrate new platform (core) server side into Kibana (#18951) Co-authored-by: Kim Joar Bekkelund <kjbekkelund@gmail.com> Co-authored-by: archana <archanid@users.noreply.github.com> Co-authored-by: Spencer <spalger@users.noreply.github.com> Co-authored-by: Court Ewing <court@epixa.com>
2018-07-11 10:19:35 +02:00
"@types/hapi-latest": "npm:@types/hapi@17.0.12",
"@types/has-ansi": "^3.0.0",
Upgrade to Jest 23.5.0 (#22791) I'd really like to upgrade to Typescript 3 for its `unknown` type, but we need to upgrade to `jest@23` to support a recent version of `ts-jest@23`. The [jest changelog](https://github.com/facebook/jest/blob/master/CHANGELOG.md) breaks down the breaking changes in 23.x, but I found it to be slightly incomplete so I've broken down the changes that actually caused breaks for us here, and addressed each in individual commits to make review a little easier: - the `testURL` config default was changed from `about:blank` to `http://localhost` - this cause some XHR requests powered by JSdom to start failing. It seems these requests just do nothing in master but start to fail when JSdom is initialized with an actual URL... I think we would ideally stop sending meaningless XHR requests in the tests, but it was a lot easier to just set the config to `about:blank` for now, and we can worry about cleanup later if necessary - `expect(...).toThrow()` only passes if an actual error was thrown. - In two places in the index pattern code we were throwing strings, which broke the assertions. Fortunately/Unfortunately the errors are not being consumed by anything, so I was able to wrap them in `new Error()` without causing any issues. - snapshots of mock functions now include a `results` array, detailing the return values of the function - React fragments are now serialized as `<React.Fragment>` instead of `<UNDEFINED>` - undefined props in React components are now stripped from snapshots - minor changes to the ordering of mocks, imports resolution, and before hooks caused the uiSettings API tests to start breaking, but I'm replacing them with totally new tests in #22694 so I just deleted them here - mocks created with `jest.spyOn()` that are restored now have their `mock.calls` reset, so some of the kbn-pm tests stated failing. This was fixed by restoring them with `jest.restoreAllMocks()` rather than trying to do it before the assertions
2018-09-08 03:36:13 +02:00
"@types/jest": "^23.3.1",
Integrate new platform (core) server side into Kibana (#18951) Co-authored-by: Kim Joar Bekkelund <kjbekkelund@gmail.com> Co-authored-by: archana <archanid@users.noreply.github.com> Co-authored-by: Spencer <spalger@users.noreply.github.com> Co-authored-by: Court Ewing <court@epixa.com>
2018-07-11 10:19:35 +02:00
"@types/joi": "^10.4.4",
Upgrade to TypeScript 3 (#22792) LGTM :tada: :tada: :tada:
2018-09-11 07:38:41 +02:00
"@types/jquery": "^3.3.6",
Integrate new platform (core) server side into Kibana (#18951) Co-authored-by: Kim Joar Bekkelund <kjbekkelund@gmail.com> Co-authored-by: archana <archanid@users.noreply.github.com> Co-authored-by: Spencer <spalger@users.noreply.github.com> Co-authored-by: Court Ewing <court@epixa.com>
2018-07-11 10:19:35 +02:00
"@types/js-yaml": "^3.11.1",
[tslint] lint typescript code (#19105) * [tslint] lint typescript code * [tslint] filter projects when running specific project * [dev/ts] use more explicit types * [dev/ts] add note about why using glob * [dev/ts] rely on ts, use fewer getters
2018-05-22 23:00:02 +02:00
"@types/listr": "^0.13.0",
Typescriptify dashboard redux code (#19857) * Typescriptify dashboard redux code * Address code review comments * minor fixes * move all type dependencies to dev
2018-06-19 15:41:12 +02:00
"@types/lodash": "^3.10.1",
[typescript] add typescript support for the server and browser (#19104) * [typescript] add typescript support for the server and browser * [ts-jest] upgrade to latest version * [jest] support test.tsx files * [jest/ts] modify `ts-jest.tsConfigFile` config based on filePath * [types] use correct major version of minimatch types * [jest] add ts support to x-pack jest config * [ts/projects] fix tsconfig.json not found error message * [optimizer/ts] use lowercase jsx option * [tsconfig] remove ui/* alias * [plguin-helpers] remove mention of `buildSourcePatterns` * [plugin-helpers] expect typescript to be a devDep * [dev/build] place transpile tasks next to each other * [ts/x-pack] add common and server directories to ts project * [dev/ts/project] use a limited set of globs to find tsconfig files
2018-05-18 19:54:57 +02:00
"@types/minimatch": "^2.0.29",
Integrate new platform (core) server side into Kibana (#18951) Co-authored-by: Kim Joar Bekkelund <kjbekkelund@gmail.com> Co-authored-by: archana <archanid@users.noreply.github.com> Co-authored-by: Spencer <spalger@users.noreply.github.com> Co-authored-by: Court Ewing <court@epixa.com>
2018-07-11 10:19:35 +02:00
"@types/node": "^8.10.20",
Typescriptify dashboard redux code (#19857) * Typescriptify dashboard redux code * Address code review comments * minor fixes * move all type dependencies to dev
2018-06-19 15:41:12 +02:00
"@types/prop-types": "^15.5.3",
Typings for chromium driver (#22688) * Typings for chromium driver * buffer => base64 * remove unused param. consolidate imports
2018-09-07 22:01:39 +02:00
"@types/puppeteer": "^1.6.2",
[ts] put JSX support in root tsconfig file (#19359)
2018-05-23 21:05:08 +02:00
"@types/react": "^16.3.14",
"@types/react-dom": "^16.0.5",
Update redux, ,react-redux and corresponding types (#22442)
2018-08-29 13:18:46 +02:00
"@types/react-redux": "^6.0.6",
bump EUI to 3.11.0 (#22745) * bump EUI to 3.9.0 * add @types/react-virtualized * remove react-virtualized from x-pack package.json * bump to 3.11.0
2018-09-13 14:20:01 +02:00
"@types/react-virtualized": "^9.18.7",
Add saved object index migrations (#20243) Migrations are the mechanism by which saved object indices are kept up to date with the Kibana codebase. Plugin authors can write their plugins to work with a certain set of mappings. Migrations ensure that the index actually conforms to those expectations.
2018-09-17 20:24:32 +02:00
"@types/redux": "^3.6.31",
Typescriptify dashboard redux code (#19857) * Typescriptify dashboard redux code * Address code review comments * minor fixes * move all type dependencies to dev
2018-06-19 15:41:12 +02:00
"@types/redux-actions": "^2.2.1",
Add saved object index migrations (#20243) Migrations are the mechanism by which saved object indices are kept up to date with the Kibana codebase. Plugin authors can write their plugins to work with a certain set of mappings. Migrations ensure that the index actually conforms to those expectations.
2018-09-17 20:24:32 +02:00
"@types/semver": "^5.5.0",
"@types/sinon": "^5.0.1",
Integrate new platform (core) server side into Kibana (#18951) Co-authored-by: Kim Joar Bekkelund <kjbekkelund@gmail.com> Co-authored-by: archana <archanid@users.noreply.github.com> Co-authored-by: Spencer <spalger@users.noreply.github.com> Co-authored-by: Court Ewing <court@epixa.com>
2018-07-11 10:19:35 +02:00
"@types/strip-ansi": "^3.0.0",
Implement `LegacyService`. Use `core` to start legacy Kibana. (#22190) * Implement `LegacyService`. Use `core` to start legacy Kibana. * Fix Worker tests * Do not rely on kbnServer when testing mixins.
2018-09-06 17:39:04 +02:00
"@types/supertest": "^2.0.5",
Integrate new platform (core) server side into Kibana (#18951) Co-authored-by: Kim Joar Bekkelund <kjbekkelund@gmail.com> Co-authored-by: archana <archanid@users.noreply.github.com> Co-authored-by: Spencer <spalger@users.noreply.github.com> Co-authored-by: Court Ewing <court@epixa.com>
2018-07-11 10:19:35 +02:00
"@types/type-detect": "^4.0.1",
Add saved object index migrations (#20243) Migrations are the mechanism by which saved object indices are kept up to date with the Kibana codebase. Plugin authors can write their plugins to work with a certain set of mappings. Migrations ensure that the index actually conforms to those expectations.
2018-09-17 20:24:32 +02:00
"@types/uuid": "^3.4.4",
[ngMock] Upgraded ng mock
2015-10-19 15:39:34 +02:00
"angular-mocks": "1.4.7",
Upgrade eslint (#15796) * [eslint] upgrade eslint-related deps * [eslint] remove snake_case destructured keys
2017-12-30 10:03:28 +01:00
"babel-eslint": "8.1.2",
Upgrade to Jest 23.5.0 (#22791) I'd really like to upgrade to Typescript 3 for its `unknown` type, but we need to upgrade to `jest@23` to support a recent version of `ts-jest@23`. The [jest changelog](https://github.com/facebook/jest/blob/master/CHANGELOG.md) breaks down the breaking changes in 23.x, but I found it to be slightly incomplete so I've broken down the changes that actually caused breaks for us here, and addressed each in individual commits to make review a little easier: - the `testURL` config default was changed from `about:blank` to `http://localhost` - this cause some XHR requests powered by JSdom to start failing. It seems these requests just do nothing in master but start to fail when JSdom is initialized with an actual URL... I think we would ideally stop sending meaningless XHR requests in the tests, but it was a lot easier to just set the config to `about:blank` for now, and we can worry about cleanup later if necessary - `expect(...).toThrow()` only passes if an actual error was thrown. - In two places in the index pattern code we were throwing strings, which broke the assertions. Fortunately/Unfortunately the errors are not being consumed by anything, so I was able to wrap them in `new Error()` without causing any issues. - snapshots of mock functions now include a `results` array, detailing the return values of the function - React fragments are now serialized as `<React.Fragment>` instead of `<UNDEFINED>` - undefined props in React components are now stripped from snapshots - minor changes to the ordering of mocks, imports resolution, and before hooks caused the uiSettings API tests to start breaking, but I'm replacing them with totally new tests in #22694 so I just deleted them here - mocks created with `jest.spyOn()` that are restored now have their `mock.calls` reset, so some of the kbn-pm tests stated failing. This was fixed by restoring them with `jest.restoreAllMocks()` rather than trying to do it before the assertions
2018-09-08 03:36:13 +02:00
"babel-jest": "^23.4.2",
Bump backport to 4.4.1 (#22456) * Bump backport to 4.4.1 * Update lock file
2018-08-29 00:29:42 +02:00
"backport": "4.4.1",
Add timelion tests
2016-08-15 20:29:17 +02:00
"chai": "3.5.0",
Align x-pack and kibana devDeps (#19022) * Align Node deps * Added grunt task * Update name
2018-05-14 19:33:04 +02:00
"chance": "1.0.10",
Add a method for plugins to add injected vars to every app (#9071) * [uiExports] add replaceInjectedVars() export type * [ui] do not assume es plugin is always there * [server/status] fix typo * [ui] add errror handling to /app/{id} endpoint * [ui] add tests for replaceInjectedVars() * [npm] swap out jsdom with cheerio * [server/ui] continue extender => replacer rename
2016-11-18 18:35:30 +01:00
"cheerio": "0.22.0",
Upgrade to Node 6.4.0 * Updated dependencies to include graceful-fs ~4.0 * Replaced deprecated grunt-s3 package with suggested grunt-aws-s3 * Update licenses task to better support npm 3 Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co>
2016-07-21 00:00:30 +02:00
"chokidar": "1.6.0",
Bump chromedriver to 2.41.0 (#21798)
2018-08-15 20:31:39 +02:00
"chromedriver": "2.41.0",
Migrate UI Framework source into Kibana. (#9192) Migrate UI Framework source into Kibana. - Add dependencies to package.json. - Add task for building UI Framework docs and serving locally. - Import UI Framework scss from autoload/styles.js instead of importing the CSS in base.less. - Refactor UI Framework directory structure. - Remove babel-polyfill. - Include SCSS synchronously.
2016-12-13 02:54:56 +01:00
"classnames": "2.2.5",
Migrate x-pack-kibana source to kibana
2018-04-20 21:13:37 +02:00
"dedent": "^0.7.0",
Upgrade to react 16.0.0 (#15469) * get kibana to start with react 16.0.0 * ensure width and height for dashboard grid * Update to Enzyme 3.x. (#12) * Fix tests broken by Enzyme upgrade (#13) * Update to Enzyme 3.x. (#12) * Add findTestSubject test helper. Fix KuiCodeEditor tests. * Fix KuiContextMenu tests. * Fix KuiConfirmModal tests. * Fix tests for KuiPager. * Update KuiConfirmModal tests to use findTestSubject helper. * Publish test helpers from ui_framework. Fix DashboardCloneModal tests. * Fix more tests (#14) * Fix DashboardPanelContainer tests. * Update KuiColorPicker tests. * Fix ControlsTab tests. * Rename vis to input_control_vis. Update and fix InputControlVis tests. * Fix KuiListingTable tests. * Fix KuiTextInput tests. * Update DashboardGrid test snapshots. * Fix test file names (#15) * Remove old enzyme setup file. * Add .test to YesNo and AddDeleteButtons test files. * needed window.cancelAnimationFrame to accompany requestAnimationFrame * remove getDOMNode function call from findTestSubject
2017-12-11 22:02:39 +01:00
"enzyme": "3.2.0",
Upgrade react deps (#16025) * [yarn] upgrade react deps * [yarn] reinstall pivotal-ui so that react dep is deduped * [yarn] remove unused deps * [react-ace] update snapshots to include new aria props * [react-input-range] update snapshot with new allowSameValues prop, default is still false * [react-select] update snapshots with new default from features added since 1.0.0-rc5
2018-01-17 10:14:12 +01:00
"enzyme-adapter-react-16": "^1.1.1",
Align x-pack and kibana devDeps (#19022) * Align Node deps * Added grunt task * Update name
2018-05-14 19:33:04 +02:00
"enzyme-to-json": "3.3.1",
Upgrade eslint (#15796) * [eslint] upgrade eslint-related deps * [eslint] remove snake_case destructured keys
2017-12-30 10:03:28 +01:00
"eslint": "4.14.0",
Prettier + ESLint setup (#16514) * Move .eslintrc (yaml) to .eslintrc.js (js) * Add Prettier setup to ESLint * Run Prettier on @kbn/build * Update style guide with Prettier
2018-02-05 18:18:43 +01:00
"eslint-config-prettier": "^2.9.0",
Upgrade to eslint 4 (#14862) * [eslint] upgrade to 4.10.0 * [eslint-config-kibana] limit jest config to jest test files * [ui_framework] remove trailing comma from rest-spreads * [dashboard/tests] tag jest helpers with .test.js suffix * explicitly import expect.js where used * [eslint] apply auto-fixes * [eslint] manually add/wrap some parens for compliance * [npm] point to local packages for testing/review * [jest] remove .test extension from jest helpers * [ui_framework] fix trailing comma removal from 3bc661a1c8 * [packages] upgrade eslint packages
2017-11-15 02:16:59 +01:00
"eslint-plugin-babel": "4.1.2",
"eslint-plugin-import": "2.8.0",
Upgrade to Jest 23.5.0 (#22791) I'd really like to upgrade to Typescript 3 for its `unknown` type, but we need to upgrade to `jest@23` to support a recent version of `ts-jest@23`. The [jest changelog](https://github.com/facebook/jest/blob/master/CHANGELOG.md) breaks down the breaking changes in 23.x, but I found it to be slightly incomplete so I've broken down the changes that actually caused breaks for us here, and addressed each in individual commits to make review a little easier: - the `testURL` config default was changed from `about:blank` to `http://localhost` - this cause some XHR requests powered by JSdom to start failing. It seems these requests just do nothing in master but start to fail when JSdom is initialized with an actual URL... I think we would ideally stop sending meaningless XHR requests in the tests, but it was a lot easier to just set the config to `about:blank` for now, and we can worry about cleanup later if necessary - `expect(...).toThrow()` only passes if an actual error was thrown. - In two places in the index pattern code we were throwing strings, which broke the assertions. Fortunately/Unfortunately the errors are not being consumed by anything, so I was able to wrap them in `new Error()` without causing any issues. - snapshots of mock functions now include a `results` array, detailing the return values of the function - React fragments are now serialized as `<React.Fragment>` instead of `<UNDEFINED>` - undefined props in React components are now stripped from snapshots - minor changes to the ordering of mocks, imports resolution, and before hooks caused the uiSettings API tests to start breaking, but I'm replacing them with totally new tests in #22694 so I just deleted them here - mocks created with `jest.spyOn()` that are restored now have their `mock.calls` reset, so some of the kbn-pm tests stated failing. This was fixed by restoring them with `jest.restoreAllMocks()` rather than trying to do it before the assertions
2018-09-08 03:36:13 +02:00
"eslint-plugin-jest": "^21.22.0",
Upgrade to eslint 4 (#14862) * [eslint] upgrade to 4.10.0 * [eslint-config-kibana] limit jest config to jest test files * [ui_framework] remove trailing comma from rest-spreads * [dashboard/tests] tag jest helpers with .test.js suffix * explicitly import expect.js where used * [eslint] apply auto-fixes * [eslint] manually add/wrap some parens for compliance * [npm] point to local packages for testing/review * [jest] remove .test extension from jest helpers * [ui_framework] fix trailing comma removal from 3bc661a1c8 * [packages] upgrade eslint packages
2017-11-15 02:16:59 +01:00
"eslint-plugin-mocha": "4.11.0",
[eslint-plugin-no-unsanitized] upgrade for `import()` support (#19315)
2018-05-24 20:36:59 +02:00
"eslint-plugin-no-unsanitized": "^3.0.2",
Use Object spread instead of Object.assign where it makes sense (#13903) * Prefer Object spread * Add eslint rules for Object spread * no slice
2017-10-10 14:50:56 +02:00
"eslint-plugin-prefer-object-spread": "1.2.1",
Prettier + ESLint setup (#16514) * Move .eslintrc (yaml) to .eslintrc.js (js) * Add Prettier setup to ESLint * Run Prettier on @kbn/build * Update style guide with Prettier
2018-02-05 18:18:43 +01:00
"eslint-plugin-prettier": "^2.6.0",
Upgrade eslint (#15796) * [eslint] upgrade eslint-related deps * [eslint] remove snake_case destructured keys
2017-12-30 10:03:28 +01:00
"eslint-plugin-react": "7.5.1",
[test/fix] Improved test case for logging configuration reloads.
2016-04-06 22:56:23 +02:00
"event-stream": "3.3.2",
[npm] remove package ranges Fixes #4866 As recently discussed in https://github.com/elastic/kibana/issues/4824 we have had a fair number of challenges with dependencies shipping breaking changes or broken code within the semver ranges which should prevent them. Nobody is perfect, we don't expect that, but as Kibana grows the number of modules does too. The output of npm ls is currently over 1100 lines, meaning we are very exposed to the semver ranges specified. While we may actually use a shrinkwrap file at some point, or implement something like uber's custom shrinkwrap utility, the only issues we have faced have been caused by top level dependencies (especially the very fast-moving ones).
2015-09-05 10:49:36 +02:00
"expect.js": "0.3.1",
"faker": "1.1.0",
[build] more cleaning (#21746) * [build] remove npm * remove angular-ui-bootstrap * fix * remove bodyParser, fetch mock to dev * remove more packages * remove check-hash; * remove babel-eslint * remove marked-text-renderer * move fetch-mock to dev dependencies * Revert "remove babel-eslint" This reverts commit 37d3df9146cdab24661022b9edf4aa2fd3b14e30. * fix npm path * fix again * remove entire node_modules dir * CleanNodeTask -> CleanNodeBuildsTask * move to node folder * remove more
2018-08-13 19:28:23 +02:00
"fetch-mock": "^5.13.1",
Bump geckodriver to 1.12.2 (#21799)
2018-09-18 20:21:30 +02:00
"geckodriver": "1.12.2",
[precommit hook] add dev script (#14890) * [precommitHook] move to dev script * [eslint] fix lint error * [dev/eslint] do simply boolean checks first * [dev] use shared REPO_ROOT constant * [dev/File] precompute relative/ext of path * [dev/eslint] fix relative import * [dev/eslint] fix typos * [grunt] remove unused run:eslintStaged config * [dev/run] only create log if we are going to use it * [dev/run/isFailError] ensure return value is Boolean * [dev/precommitHook] use less intermediate vars
2017-11-20 22:22:24 +01:00
"getopts": "2.0.0",
Check filename casing in CI (#19282) * [dev/checkCasing] add script to find casing violations * [dev/casingCheck] fix es-ES.json violation
2018-05-24 20:38:42 +02:00
"globby": "^8.0.1",
Upgrade to Node 6.4.0 * Updated dependencies to include graceful-fs ~4.0 * Replaced deprecated grunt-s3 package with suggested grunt-aws-s3 * Update licenses task to better support npm 3 Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co>
2016-07-21 00:00:30 +02:00
"grunt": "1.0.1",
Updating minimatch (#21050)
2018-07-27 13:30:17 +02:00
"grunt-cli": "^1.2.0",
Create grunt task to generate parsers from peg files (#17069) * Create grunt task to generate parsers from peg files * Leave comment * Move grunt config to config/
2018-03-22 00:42:23 +01:00
"grunt-contrib-watch": "^1.0.0",
Upgrade to Node 6.4.0 * Updated dependencies to include graceful-fs ~4.0 * Replaced deprecated grunt-s3 package with suggested grunt-aws-s3 * Update licenses task to better support npm 3 Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co>
2016-07-21 00:00:30 +02:00
"grunt-karma": "2.0.0",
Create grunt task to generate parsers from peg files (#17069) * Create grunt task to generate parsers from peg files * Leave comment * Move grunt config to config/
2018-03-22 00:42:23 +01:00
"grunt-peg": "^2.0.1",
Bump grunt-run to 0.7.0 (#12127)
2017-06-02 16:15:45 +02:00
"grunt-run": "0.7.0",
Migrate x-pack-kibana source to kibana
2018-04-20 21:13:37 +02:00
"gulp-babel": "^7.0.1",
[hotfix] force gulp-sourcemaps to 1.7.x https://github.com/floridoo/gulp-sourcemaps/issues/238#issuecomment-253634399
2016-10-13 23:09:12 +02:00
"gulp-sourcemaps": "1.7.3",
Integrate new platform (core) server side into Kibana (#18951) Co-authored-by: Kim Joar Bekkelund <kjbekkelund@gmail.com> Co-authored-by: archana <archanid@users.noreply.github.com> Co-authored-by: Spencer <spalger@users.noreply.github.com> Co-authored-by: Court Ewing <court@epixa.com>
2018-07-11 10:19:35 +02:00
"has-ansi": "^3.0.0",
[npm] remove package ranges Fixes #4866 As recently discussed in https://github.com/elastic/kibana/issues/4824 we have had a fair number of challenges with dependencies shipping breaking changes or broken code within the semver ranges which should prevent them. Nobody is perfect, we don't expect that, but as Kibana grows the number of modules does too. The output of npm ls is currently over 1100 lines, meaning we are very exposed to the semver ranges specified. While we may actually use a shrinkwrap file at some point, or implement something like uber's custom shrinkwrap utility, the only issues we have faced have been caused by top level dependencies (especially the very fast-moving ones).
2015-09-05 10:49:36 +02:00
"husky": "0.8.1",
Add screenshot-comparison utility, to protect against visual regressions during CSS refactors. - Remove test/output and added test/screenshots (requires a Jenkins change). - Add test/screenshots/baseline images. These document the expected state of the UI. - Add dependency on image-diff package. - Add utilities/compareScreenshots.js, which can be run via 'npm run compareScreenshots'.
2016-06-08 19:27:49 +02:00
"image-diff": "1.6.0",
Upgrade to webpack 3 (#14315) * [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
2017-11-01 00:31:22 +01:00
"istanbul-instrumenter-loader": "3.0.0",
Upgrade to Jest 23.5.0 (#22791) I'd really like to upgrade to Typescript 3 for its `unknown` type, but we need to upgrade to `jest@23` to support a recent version of `ts-jest@23`. The [jest changelog](https://github.com/facebook/jest/blob/master/CHANGELOG.md) breaks down the breaking changes in 23.x, but I found it to be slightly incomplete so I've broken down the changes that actually caused breaks for us here, and addressed each in individual commits to make review a little easier: - the `testURL` config default was changed from `about:blank` to `http://localhost` - this cause some XHR requests powered by JSdom to start failing. It seems these requests just do nothing in master but start to fail when JSdom is initialized with an actual URL... I think we would ideally stop sending meaningless XHR requests in the tests, but it was a lot easier to just set the config to `about:blank` for now, and we can worry about cleanup later if necessary - `expect(...).toThrow()` only passes if an actual error was thrown. - In two places in the index pattern code we were throwing strings, which broke the assertions. Fortunately/Unfortunately the errors are not being consumed by anything, so I was able to wrap them in `new Error()` without causing any issues. - snapshots of mock functions now include a `results` array, detailing the return values of the function - React fragments are now serialized as `<React.Fragment>` instead of `<UNDEFINED>` - undefined props in React components are now stripped from snapshots - minor changes to the ordering of mocks, imports resolution, and before hooks caused the uiSettings API tests to start breaking, but I'm replacing them with totally new tests in #22694 so I just deleted them here - mocks created with `jest.spyOn()` that are restored now have their `mock.calls` reset, so some of the kbn-pm tests stated failing. This was fixed by restoring them with `jest.restoreAllMocks()` rather than trying to do it before the assertions
2018-09-08 03:36:13 +02:00
"jest": "^23.5.0",
"jest-cli": "^23.5.0",
[console] porting console tests to Jest (#19543) * porting console tests to Jest * adding missing import
2018-06-04 17:23:59 +02:00
"jest-raw-loader": "^1.0.1",
Add mechanism for dashboard snapshots (#15463) * Add mechanism for dashboard snapshots * Adjust wait for render function since it needs to be 2, not gt 0. Should be obsolete when the new render stuff is complete. * resize images using new library so comparisons work across different screen resolutions * use jimp comparison and see if expanding to expanded panel mode helps when comparing across browser/os * Try to ensure window size * Experiment with a smaller window, see if screenshot dimensions change Update screenshot for new window dimensions * Try cover + quality, see what the diffs look like. * Stop trying to get TSVB to pass, try area charts There is a timezone bug with tsvb: https://github.com/elastic/kibana/issues/15501 * gah, cover didn't work, check resize * bump render counter to 6, as it should be. As it turns out, the visualization was not done re-rendering to maximized mode * Bump threshold for comparison * reduce down to a single test run * Don't use an environment variable to detect updateBaselines cmd line flag
2017-12-13 19:41:40 +01:00
"jimp": "0.2.28",
Implement a build tool for default messages extraction (#19620) * Implement a build tool for default messages extraction * Refactor extraction tool, resolve review comments, fix bugs * Resolve comments, refactor extraction tool, fix bugs * Add context to messages extraction tool * Resolve comments * Fix bugs * Add messages extraction from .jade files, refactor code * Add template literals parsing * Return defaultMessages.json to plain structure * Refactor utils * Fix bugs * Refactor code, resolve review comments, fix bugs * Fix minor bug * Get rid of '@babel/traverse' and add its native implementation * Add handlebars messages extraction * Fix mkdir on macOS * Fix bugs, inject default formats, finalize the tool * Fix filsystem permissions * Refactor nodes traversal * Update code style * Downgrade @babel/types to fix build issues * Resolve comments * Fix minor bugs
2018-07-17 14:56:55 +02:00
"json5": "^1.0.1",
[npm] upgrade karma (#11806)
2017-05-16 01:46:52 +02:00
"karma": "1.7.0",
"karma-chrome-launcher": "2.1.1",
"karma-coverage": "1.1.1",
"karma-firefox-launcher": "1.0.1",
"karma-ie-launcher": "1.0.0",
[CI] Produce junit test reports (#15281) * [mocha] use custom reporter for legible results in jenkins * [jest] use custom result processor for legible results in jenkins * [karma] enable junit output on CI * [mocha/junitReporter] accept rootDirectory as configuration * [jest/reporter] use reporters option added in jest 20 * [toolingLog] remove black/white specific colors * [dev/mocha/junit] no reason for junit to be a "reporter" * typos * [dev/mocha/junit] use else if * [karma/junit] use string#replace for explicitness * [junit] use test file path as "classname" * [ftr/mocha] no longer a "console" specific reporter
2017-12-06 01:29:48 +01:00
"karma-junit-reporter": "1.2.0",
[npm] upgrade karma (#11806)
2017-05-16 01:46:52 +02:00
"karma-mocha": "1.3.0",
"karma-safari-launcher": "1.0.0",
Bumped leadfoot to 1.7.5 now that it issue has been merged. (#17582)
2018-04-06 21:19:50 +02:00
"leadfoot": "1.7.5",
Upgrade license checker (#16147)
2018-01-19 08:49:55 +01:00
"license-checker": "^16.0.0",
[tslint] lint typescript code (#19105) * [tslint] lint typescript code * [tslint] filter projects when running specific project * [dev/ts] use more explicit types * [dev/ts] add note about why using glob * [dev/ts] rely on ts, use fewer getters
2018-05-22 23:00:02 +02:00
"listr": "^0.14.1",
Upgrade to Node 6.4.0 * Updated dependencies to include graceful-fs ~4.0 * Replaced deprecated grunt-s3 package with suggested grunt-aws-s3 * Update licenses task to better support npm 3 Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co>
2016-07-21 00:00:30 +02:00
"load-grunt-config": "0.19.2",
Update makelogs to 4.1.0 (#20232)
2018-06-27 11:48:58 +02:00
"makelogs": "^4.1.0",
[npm] downgrade mocha even further, to before #19022 (#19238)
2018-05-19 03:05:27 +02:00
"mocha": "3.3.0",
Bumps node to 8.9.4 (#16981) Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co>
2018-03-06 01:19:02 +01:00
"mock-fs": "^4.4.2",
add test sharding The tests in master are currently failing regularly because our current browser tests are serious memory hogs. Investigation reveals that nearly every test is retaining all of the memory it causes to be allocated. We have made some progress to being able to diagnose the problems, but we expect that problem to take some serious work to fix. We need a short-term solution though, and this is it. Rather than modify the bundling process, we will shard the top-level test suites by name. For now, we've created 4 shards, but adding new shards is trivial if we need to. Sharding is accomplished by creating a murmur3 hash of the top level suite names, then bucketing based on the hash output. If a test suite resolves to shard2, but we are running shard1, we simply never pass the function to `mocha.describe()`. Rather than redefine every describe statement, we have shimmed the global `window.describe()` function to accomplish this.
2016-09-02 00:02:43 +02:00
"murmurhash3js": "3.0.1",
add mutation observer polyfill for jest test env (#20996) * add mutation observer polyfill for jest test env * use polyfill from npm * set bluebird scheduler * use correct version in comment about bluebird
2018-07-30 16:17:57 +02:00
"mutation-observer": "^1.0.3",
Bump versions on a handful of node modules
2016-09-06 22:10:54 +02:00
"nock": "8.0.0",
Adds SCSS support for plugins (#19643) Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co>
2018-06-22 01:25:29 +02:00
"node-sass": "^4.9.0",
Add ability to skip file writing for messages extraction tool (#21588) * Add ability to skip 'en.json' file writing for default messages extraction tool * Update default messages extractor * Add namespace validation * Update tests * Fix i18n config file * Add ability to choose output JSON format * Update output json properties keys
2018-08-22 13:57:32 +02:00
"normalize-path": "^3.0.0",
Upgrade kibana to leaflet 1.x (#12367) * upgrade leaflet modules to 1.x latest * fix css for leaflet controls * update draw options so it is easier to see polygon when drawing * fix chrome touch issues with closing polygon in leaflet draw * use canvas renderer * use leaflet-responsive-popup to avoid tooltip cutoff * remove radius configuration from leaflet heatmap * make blur a factor of radius. Set maxZoom to map zoom since new values are calculated per precision * use _.get to avoid error, cannot read property of undefined * add cluster size slider * experiments with image differences * onload not onLoad * use canvas dimensions * compare map canvas to stored PNG of map canvas * remove pixelmatch from project dependecies * fix broken test - rounding error * add expected image tests for geohash layers shaded circles and geohash grids * bump z-index of vis-spy * update functional test expected data * update to leaflet 1.2.0 * revert to leaflet 1.0.3 and update expected data set for map functional tests * test geohash_layer heatmap in unit test * update region_map functional test since it can not longer pluck map vectors from DOM * update documentation
2017-08-23 01:26:30 +02:00
"pixelmatch": "4.0.2",
[scss] Adds autoprefixer support and improves watcher (#21656) This adds support for autoprefixer which we have been using in Webpack. Additionally, we have improved the watching functionality and now update builds based directly on their dependencies an not an assumption that the files are children. Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co>
2018-08-10 23:24:14 +02:00
"postcss": "^7.0.2",
Upgrade prettier to version 1.14.0 (#21466) This upgrades prettier to version 1.14.0. The main motivation is to gain support for the new TypeScript language features introduced in 2.9 and 3.0. Prettier versions 1.13 and 1.14 also introduced some other JavaScript and TypeScript style improvements resulting in a few small line break and parenthesis changes. The relevant release notes are: * [Prettier 1.13.0 Release Notes](https://prettier.io/blog/2018/05/27/1.13.0.html) * [Prettier 1.40.0 Release Notes](https://prettier.io/blog/2018/07/29/1.14.0.html)
2018-07-31 15:30:36 +02:00
"prettier": "^1.14.0",
Align x-pack and kibana devDeps (#19022) * Align Node deps * Added grunt task * Update name
2018-05-14 19:33:04 +02:00
"proxyquire": "1.7.11",
[ftr] capture test output and only log on failure (#21903) This is an attempt to write a log capture integration for the functional test runner that will collect all log output written during a test, prevent it from being written to stdout to lower the amount of work Jenkins master has to do and include the entire log output for each test in the junit report. I'm slightly concerned about the amount of memory we'll be using to store a copy of the logs for each test, but streaming the XML report isn’t easy and there doesn’t seem to be a library out there to help. If we decide it’s torally necessary we might be able to figure it out.
2018-08-28 02:26:30 +02:00
"regenerate": "^1.4.0",
Add visual regression screenshot gallery. - Add 'test:visualRegression' grunt task. - Run 'test:visualRegression' as part of npm script 'test'. - Add 'clean:screenshots task'. - Clean screenshots/session when funtional tests are run.
2016-06-10 06:36:09 +02:00
"simple-git": "1.37.0",
Upgrade `sinon` (v1.17.3 --> v5.0.7). (#19074)
2018-05-22 12:13:38 +02:00
"sinon": "^5.0.7",
[ftr] take screenshots on failure (#11709) * [tests/functional] move screenshots to their own service * [ftr] add testFailure and testHookFailure lifecycle hooks * [tests/functional/screenshots] cleanup old screenshots at startup * [test/functional/screenshots] take screenshots when tests fail * [cli_plugin/install] fix test * [ui/scanner] fix test
2017-05-11 21:07:23 +02:00
"strip-ansi": "^3.0.1",
Implement `LegacyService`. Use `core` to start legacy Kibana. (#22190) * Implement `LegacyService`. Use `core` to start legacy Kibana. * Fix Worker tests * Do not rely on kbnServer when testing mixins.
2018-09-06 17:39:04 +02:00
"supertest": "^3.1.0",
"supertest-as-promised": "^4.0.2",
Align x-pack and kibana devDeps (#19022) * Align Node deps * Added grunt task * Update name
2018-05-14 19:33:04 +02:00
"tree-kill": "^1.1.0",
Upgrade to Jest 23.5.0 (#22791) I'd really like to upgrade to Typescript 3 for its `unknown` type, but we need to upgrade to `jest@23` to support a recent version of `ts-jest@23`. The [jest changelog](https://github.com/facebook/jest/blob/master/CHANGELOG.md) breaks down the breaking changes in 23.x, but I found it to be slightly incomplete so I've broken down the changes that actually caused breaks for us here, and addressed each in individual commits to make review a little easier: - the `testURL` config default was changed from `about:blank` to `http://localhost` - this cause some XHR requests powered by JSdom to start failing. It seems these requests just do nothing in master but start to fail when JSdom is initialized with an actual URL... I think we would ideally stop sending meaningless XHR requests in the tests, but it was a lot easier to just set the config to `about:blank` for now, and we can worry about cleanup later if necessary - `expect(...).toThrow()` only passes if an actual error was thrown. - In two places in the index pattern code we were throwing strings, which broke the assertions. Fortunately/Unfortunately the errors are not being consumed by anything, so I was able to wrap them in `new Error()` without causing any issues. - snapshots of mock functions now include a `results` array, detailing the return values of the function - React fragments are now serialized as `<React.Fragment>` instead of `<UNDEFINED>` - undefined props in React components are now stripped from snapshots - minor changes to the ordering of mocks, imports resolution, and before hooks caused the uiSettings API tests to start breaking, but I'm replacing them with totally new tests in #22694 so I just deleted them here - mocks created with `jest.spyOn()` that are restored now have their `mock.calls` reset, so some of the kbn-pm tests stated failing. This was fixed by restoring them with `jest.restoreAllMocks()` rather than trying to do it before the assertions
2018-09-08 03:36:13 +02:00
"ts-jest": "^23.1.4",
[typescript] add typescript support for the server and browser (#19104) * [typescript] add typescript support for the server and browser * [ts-jest] upgrade to latest version * [jest] support test.tsx files * [jest/ts] modify `ts-jest.tsConfigFile` config based on filePath * [types] use correct major version of minimatch types * [jest] add ts support to x-pack jest config * [ts/projects] fix tsconfig.json not found error message * [optimizer/ts] use lowercase jsx option * [tsconfig] remove ui/* alias * [plguin-helpers] remove mention of `buildSourcePatterns` * [plugin-helpers] expect typescript to be a devDep * [dev/build] place transpile tasks next to each other * [ts/x-pack] add common and server directories to ts project * [dev/ts/project] use a limited set of globs to find tsconfig files
2018-05-18 19:54:57 +02:00
"ts-loader": "^3.5.0",
Upgrade to TypeScript 3 (#22792) LGTM :tada: :tada: :tada:
2018-09-11 07:38:41 +02:00
"ts-node": "^7.0.1",
"tslint": "^5.11.0",
"tslint-config-prettier": "^1.15.0",
[tslint] lint typescript code (#19105) * [tslint] lint typescript code * [tslint] filter projects when running specific project * [dev/ts] use more explicit types * [dev/ts] add note about why using glob * [dev/ts] rely on ts, use fewer getters
2018-05-22 23:00:02 +02:00
"tslint-plugin-prettier": "^1.3.0",
Upgrade to TypeScript 3 (#22792) LGTM :tada: :tada: :tada:
2018-09-11 07:38:41 +02:00
"typescript": "^3.0.3",
Add/generate/verify NOTICE.txt file (#17504) * [dev/notice] add scripts for generating NOTICE.txt file * [notice] react-resize-detector@0.6.0 was removed in b445389b7960a53c38cc58ffa73c084243f4ce0a * [notice] move notice text into relevant source * [dev/notice] Generate NOTICE.txt file * [jenkins] verify that notice.txt is up to date in CI * [tasks/notice] update test to use new NOTICE.txt file * [dev/notice] update company name in NOTICE.txt * [notice/cli] exit with 0 when --help requested * [notice/cli] add helpful logging * [notice/cli] use --validate flag name instead * [notice/cli] simplify NEWLINE_RE, ignore obscure line endings * [utils/decode_geo_hash] fixup comment * [utils/decode_geo_hash] remove useless comment
2018-04-04 18:12:44 +02:00
"vinyl-fs": "^3.0.2",
Align x-pack and kibana devDeps (#19022) * Align Node deps * Added grunt task * Update name
2018-05-14 19:33:04 +02:00
"xml2js": "^0.4.19",
[package.json] Add missing dev dependencies (#19625)
2018-06-08 18:32:31 +02:00
"xmlbuilder": "9.0.4",
"zlib": "^1.0.5"
lets just test in 0.12 for now
2015-06-06 01:20:49 +02:00
},
"engines": {
Bump node to 8.11.4 (#22048)
2018-08-16 20:05:17 +02:00
"node": "8.11.4",
Move to Yarn 1.6.0 (#17741)
2018-04-17 18:53:12 +02:00
"yarn": "^1.6.0"
Consolidating package.json adding JSON logger
2015-01-07 21:48:58 +01:00
}
initial commit
2014-02-07 00:29:19 +01:00
}
Reference in a new issue Copy permalink