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

303 lines
9.6 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",
Consolidating package.json adding JSON logger
2015-01-07 21:48:58 +01:00
"description": "Kibana is an open source (Apache Licensed), 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.",
"keywords": [
"kibana",
"elasticsearch",
"logstash",
"analytics",
"visualizations",
"dashboards",
"dashboarding"
],
"private": false,
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
},
removed unused deps and prevent license failure
2015-06-08 23:17:22 +02:00
"license": "Apache-2.0",
[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
"contributors": [
[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
"Chris Cowan <chris.cowan@elastic.co>",
Add Court Ewing to contributor list
2015-10-26 22:19:32 +01:00
"Court Ewing <court@elastic.co>",
[contrib] The cake is a lie :cake: Sort alphabetically.
2016-03-30 21:16:01 +02:00
"Jim Unger <jim.unger@elastic.co>",
[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
"Joe Fleming <joe.fleming@elastic.co>",
[contrib] The cake is a lie :cake: Sort alphabetically.
2016-03-30 21:16:01 +02:00
"Jon Budzenski <jonathan.budzenski@elastic.co>",
"Juan Thomassie <juan.thomassie@elastic.co>",
Add Matt/Jon/Tim/Jim to constributor list I also moved Khalah to preserve the alphabetical order.
2015-10-26 22:26:16 +01:00
"Khalah Jones-Golden <khalah.jones@elastic.co>",
Update intern version to 3.2.3, fix failing test
2016-06-14 17:41:37 +02:00
"Lee Drengenberg <lee.drengenberg@elastic.co>",
[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
"Lukas Olson <lukas.olson@elastic.co>",
[contrib] The cake is a lie :cake: Sort alphabetically.
2016-03-30 21:16:01 +02:00
"Matt Bargar <matt.bargar@elastic.co>",
[contrib] Rank myself higher as a contributor :rocket: Profit.
2016-03-30 21:14:27 +02:00
"Nicolás Bevacqua <nico@elastic.co>",
[Cleanup] Fix name change to correctly spell name
2015-04-01 19:40:13 +02:00
"Shelby Sturgis <shelby@elastic.co>",
[contrib] The cake is a lie :cake: Sort alphabetically.
2016-03-30 21:16:01 +02:00
"Spencer Alger <spencer.alger@elastic.co>",
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
"Tim Sullivan <tim@elastic.co>",
"Yuri Astrakhan <yuri@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",
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",
Add intern task to grunt and associated npm script
2015-09-02 21:07:20 +02:00
"test:ui": "grunt test:ui",
[functional testing] Add dev mode
2015-09-11 21:08:35 +02:00
"test:ui:server": "grunt test:ui:server",
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",
[tests] remove unused visual_regression suite (#12046)
2017-05-26 23:57:36 +02:00
"test:visualRegression": "grunt test:visualRegression:buildGallery",
Integrate Kibana UI Framework CSS. - Migrate to new localNav component and subcomponent styles. - Add support for multi-slot transclusion to kbnTopNav. - Update Dashboard, Discover, Management, Visualize, Dev Tools, Timelion to use kbnTopNav consistently. - Update these apps to also display localNavDropdowns consistently, including Timepicker (this mostly meant adding titles). - Add checkLicenses npm script. - Add .fullWidth utility class and use it to make search forms 100% width.
2016-10-15 00:30:48 +02:00
"checkLicenses": "grunt licenses",
[grunt] link build to package.json, correct start command
2015-08-18 23:52:40 +02:00
"build": "grunt build",
Release task now always publishes to staging Production builds should never be published directly from a local machine. Instead, the release command will now publish to a commit-specific staging URL, so you use it to publish a release candidate, and then when those builds have been verified, you need to copy the RC builds from on the staging location on s3 to the production folder.
2016-06-17 20:26:08 +02:00
"release": "grunt release",
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",
Add debug script to set inspect flags (#15967) * Add debug script to set inspect flags * remove no-base-path flag
2018-01-11 00:12:20 +01:00
"debug": "node --nolazy --inspect --debug-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",
[npm] added lint and lintroller scripts
2015-09-23 03:58:14 +02:00
"elasticsearch": "grunt esvm:dev:keepalive",
[eslint] add eslint dev script (#14889)
2017-11-14 18:11:59 +01:00
"lint": "echo 'use `node scripts/eslint`' && false",
"lintroller": "echo 'use `node scripts/eslint --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",
"uiFramework:documentComponent": "cd packages/kbn-ui-framework && yarn documentComponent"
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": {
upgrade EUI to 0.0.26 (#17110) * upgrade EUI to 0.0.25 * remove last reference to TooltipTrigger * upgraded to EUI 0.0.26 * fix warning, EuiKeyboardAccessible child must have onClick defined
2018-03-13 18:16:22 +01:00
"@elastic/eui": "0.0.26",
[npm] move personal forks into elastic org (#13410)
2017-08-09 21:31:30 +02:00
"@elastic/filesaver": "1.1.2",
Fix: exponent values in table view (#15309) the new release includes a fix for dealing with exponent values and precision
2017-12-01 16:01:26 +01:00
"@elastic/numeral": "2.3.1",
[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",
[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",
[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
"JSONStream": "1.1.1",
Kibana Globalization - Phase 1 (#7545) * Add low level i18n plugin Manages languages that are available and is responsible for loading translated content at the granularity of a plugin. To be done: - APIs for store and retrieval * Use Kibana install as root for the translation store directory Setting the path for storing the bundled language translation files to <KIBANA_INSTALL>/data/store_translations/<PLUGIN_NAME> * Updated i18n core plugin APIs to be asynchronous To be done: - Better error handling in APIs - Fix threading issue with storePluginLanguageTranslations API * Fix thread synchroization issue in storePluginLanguageTranslations * Update error handling in i18n core plugin * Change to use NodeJS mkdirp function for creating directories recursively Updates with review comments from @srl295. Changed export syntax to show the exported functions at end of file. * Add REST API for getting translations of a language for a plugin To be done: - Add algorithm to decide on the language for a plugin by comparing the accept languages from the REST call and the plugin supported languages - Add REST API tests * Add algorithm for determining plugin language when retrieving translations Client would pass languages used in the 'accept-language' header. These languages would then be compared against the plugin supported languages and best compared language would be selected. To be done: - Add REST API tests * Add API to return all registered plugin language translations * Add HAPI API to get all plugins translation files * Update register translations API to be independent of plugin name and language The register API is updated to be independent of plugin name and language. The API will now traverse the path given and create language bundles as per language files it traverses. The translations files structure has also been simplified to be just key/value objects. To be done: - Add hapi API to get translations - Extend the API tests to test responses * Update API test * Add eslint fix for API test * Update with review comments From review https://github.com/elastic/kibana/pull/7545#issuecomment-231147435 following comments updated: - README, .gitignore, and .eslintrc are not needed in a core plugin - package.json only needs name and version - unit tests need to go in a tests directory otherwise they won't get picked up by the grunt tasks. Also our convention is to name the test file with the same name as the module it's testing (so i18n_tests.js should just be i18n.js) - For consistency with the rest of the code base, rename the data directory to fixtures. - Prefer const (or let if necessary). Don't use var. - Use ES6 imports/exports rather than commonjs style - Only export the i18n module's public API. For instance, I don't think getPluginTranslationDetails is used outside of the i18n module, so it shouldn't be exposed publicly. If you want to expose it for testing purposes, I would recommend creating an i18n directory with an index.js file that exports the module's public API, and a separate i18n.js file with the "private" API. index.js will be for public use, i18n.js will be for private internal use. * Update after review comments From review (https://github.com/elastic/kibana/pull/7545#issuecomment-231884490): - i18n module API should return promises for async operations instead of using callbacks - All filesystem access should be async - Unit tests need to be updated based on new proposed plugin structure (single language file, not split by view) From design (https://github.com/elastic/kibana/issues/6515#issuecomment-231400097): - Removed API as will consider in later phase TODO: - Make write function async * Update after review comments Updated write function to be asynchronous * Update registerTranslations API to take absolute translation file as argument The API originally took the directory as the argument but following reviews it was decided to change to absolute file because it will be less brittle since it is more explicit. * Translate the Kibana welcome message Translates the start-up message (“Kibana is loading ...”)in the Jade template. To be done: - Means to register the core plugin translations. They are currently added in the fixtures directory as static files. Need to be generated on the fly. * Add build task to generate core plugin translations Task which calls registerTranslations API and then a task which copies the regsitered translations to <kibana_root>/build/kibana * Add hook to optimize module to add registration during dev startup Registration of the core plugin translations during development start of Kibana server. The translations include the welcome message and server error startup message. * Handle scenario when the user preferred language header is not passed The UI when loading asks i18n plugin which language translation to use depending on the user preferred language header 'accept-language'. This commit is to handle scenario where header is not passed. The algorithm then chooses the default language. * Replace registering of translations at plugin install time to the plugin init phase This change follows review comments in: https://github.com/elastic/kibana/issues/6515#issuecomment-236237218 * Update after review comments Comments: - https://github.com/elastic/kibana/pull/7545#discussion-diff-72890673 - https://github.com/elastic/kibana/pull/7545#discussion-diff-72894762 * Update after plugin folder layout changes in Kibana This require to use <kibana_root>/data for registered translations and i18n plugin moved to core_plugins from plugins. Refer to PR for more details: https://github.com/elastic/kibana/pull/7562 * Update translation registration to file path rather than bundling After review discussions it was agreed to just register the absolute paths to translation files rather than bundling each file into one central file at registration. * Update review comments This commit contains the following review comments: - https://github.com/elastic/kibana/pull/7545#discussion-diff-74661282 - https://github.com/elastic/kibana/pull/7545#discussion-diff-74661392 - https://github.com/elastic/kibana/pull/7545#discussion-diff-74662271 - https://github.com/elastic/kibana/pull/7545#discussion-diff-74663235 - https://github.com/elastic/kibana/pull/7545#discussion-diff-74669201 - https://github.com/elastic/kibana/pull/7545#discussion-diff-74669269 - https://github.com/elastic/kibana/pull/7545#discussion-diff-74669419 - https://github.com/elastic/kibana/pull/7545#discussion-diff-74669628 - https://github.com/elastic/kibana/pull/7545#discussion-diff-74799382 * Update review comments The following review comments are included in the commit: - https://github.com/elastic/kibana/pull/7545#discussion_r74663515 - https://github.com/elastic/kibana/pull/7545#discussion_r74666995 - https://github.com/elastic/kibana/pull/7545#discussion_r74805552 * Expose the i18n APIs in the server object for plugin access Plugins should call the i18n plugin APIs through the server object and not directly from the module. This closes he following comments: - https://github.com/elastic/kibana/pull/7545#discussion_r74662598 - https://github.com/elastic/kibana/pull/7545#discussion_r74669327 - https://github.com/elastic/kibana/pull/7545#discussion_r74669765 * Update accept-language-parser module to 1.2.0 Module version 1.2.0 fixes issue: https://github.com/opentable/accept-language-parser/issues/8 This commit updates review comments: https://github.com/elastic/kibana/pull/7545#discussion-diff-75525214 https://github.com/elastic/kibana/pull/7545#issuecomment-240290461 * Add i18n default locale as a configurable item Adds 'defaultLocale' configurable item to the i18n plugin configuration. The default locale is used for translations if the locale specified by user is not supported. This commit satisfies the review comment: - https://github.com/elastic/kibana/pull/7545#discussion-diff-74669970 * Move UI i18n wrapper functionality into a module This commit better structures the i18n capability so that it can be called in UI code in a clearly defined fashion with minimum code. It also fixes potential race conditions. This commit updates review comments: - https://github.com/elastic/kibana/pull/7545#discussion-diff-74804791 - https://github.com/elastic/kibana/pull/7545#discussion-diff-74801802 - https://github.com/elastic/kibana/pull/7545#discussion-diff-74670457 * Fill any missing translations using translations from default locale The default language translations are loaded and are compared against the selected language translations. The comparison can then highlight any missing translation keys and can load the default translations keys as needed. This helps to unsure where possible that a translation string is available in most scenarios even if not in the locale requested. This commit resolves review comments: - https://github.com/elastic/kibana/pull/7545#issuecomment-239202583 - https://github.com/elastic/kibana/pull/7545#issuecomment-239203734 * Add unit tests for the i18n UI wrapper functions * Fix issues after rebase with master * Add translation keys verification tool This tool helps to check that translation keys are translated. This tool can be used for non-angular translation constructs like the Jade templates. * Updates after review comments Updates for review comments: https://github.com/elastic/kibana/pull/7545#pullrequestreview-3748114 * Update after review comments Update for review comments: https://github.com/elastic/kibana/pull/7545#pullrequestreview-3937958 To be done: - Update of unit tests for UI and server - Call of verify translations * Update unit tests after review changes There was a number of changes to the i18n module and the ui i18n wrapper following review comments. This commit is to update the unit tests with respect. * Add build task for verify translations * Update the kibana i18n IDs to be prefixed with kibana * Update verify translations to test registered translations It was testing the static translation files. It is now updated to test the translations registered when Kibana server is started and the plugins have initialized. * Update after review comments Updates following review comments: https://github.com/elastic/kibana/pull/7545#pullrequestreview-5529711 * Update after review This commit contain updates after the following review: https://github.com/elastic/kibana/pull/7545#pullrequestreview-5707951 * Updates after review Updates for review comments: https://github.com/elastic/kibana/pull/7545#pullrequestreview-6656571 * Update after review Updates for the following review comments: https://github.com/elastic/kibana/pull/7545#pullrequestreview-6911265 * Update after review Updates after the following review comments: https://github.com/elastic/kibana/pull/7545#pullrequestreview-7084765 * Update unit tests to use expect throwError * Update after rebase with master Loading message changed following merge of commit https://github.com/elastic/kibana/commit/26c53e8a8d62e0714feedf883ab066362ae9ae17#diff-e25d7fee746a4f249e17f87c02fd95f8R55 This required update to the welcome message and how it is called. * Update following review Updated the following review comments: https://github.com/elastic/kibana/pull/7545#pullrequestreview-9297662 * Update the algorithm to return the locale The algorithm to return which locale to use for translations based on the user locale list and the regsitered locales is updated in this commit. The algorithm previously did an exact match on all the user locales first before (by priority) then checking for best case match. The algorithm is now modified to check each user locale starting with the highest priority first for an exact match and then for best case match. If no match it then moves to the next user locale with the next highest priority. This is to follow the priority list that a user browser is configured for where there maybe a locale translation available but might not be the exact match with regard to the locale code and/or script. An example of this is that the highest priority locale of the user is 'en-US' but the locale translation available is 'en'. It is better select the 'en' locale rather than select the next highest locale which is an exact match. * Update after review comments Updates after the following reviews: https://github.com/elastic/kibana/pull/7545#pullrequestreview-9785665 https://github.com/elastic/kibana/pull/7545#pullrequestreview-9786404 * Fix after merge with master Change in the flo and layout of ui index meant that acceptLanguages were not being passed. This commit is an update to fix this so that the welcome messages are loaded. * Update after review comments This commit is for updates after the following review: https://github.com/elastic/kibana/pull/7545#pullrequestreview-10435175 * Fix issue when unit test run in CI as core translations are registered When unit tests are run on a test server (like in the CI), it will start Kibana server and register the core translations. This means that the i18n unit tests need to be able to store the existing registration prior to testing and replace after testing. * [server/ui] move i18n into ui module * [server/ui] restore renderApp() method signature * [server/ui] unify i18n logic in UiI18n class * [server] move translation files into "translations" dir * Update i18n module to loaded by multiple server instances within the one process * Update i18n module to a class Moving the i18n module into a class so as to encapsulate the registered translations which means there can be different and distinct instances per process. This is to accomodate the user case where there might be multiple Kibana server instances in a process and the localization should be at the server level. * Identify private members in a class with underscore-prefix convention * Remove redundant translation from core translation file Message starting with 'Give me a moment...' is no longer part of loading message folowing a rebase with master. * [ui/i18n] reject translations files that do not use absolute paths * Update config item locale to defaultLocale * Update after review comments - Update after following review: https://github.com/elastic/kibana/pull/7545#pullrequestreview-12775161 - Also, fix syntax mess following rebase with master of src/optimize/index.js * Fix rebase with master error * Add task for verifying translations in CI * Fix lint errors
2016-12-14 01:55:48 +01:00
"accept-language-parser": "1.2.0",
Upgrade Angular to 1.6.5 (#13543) * [angular/$http] remove use of .success() and .error() callbacks * [angular/$route] remove `!` hash prefix * [angular] upgrade * [angular/$timeout] prevent unhandled exception "canceled" logging * [ui/fancy_form] refactor FormController for compatibility * [ngModelController] ensure method calls keep context * [ui/queryBar/tests] attach $elem to DOM so "click" triggers "submit" * [confirmModalPromise] fix test for rejected promise * [watchMulti] specifically check watchers array for length * [typeahead] check for property rather than own keys * [ui/compat] add initAfterBindingsWorkaround * [ui/fancyForms] fix _getInvalidModels() * [fancyForm] add tests that check nested form error counting * [ui/fancyForms] ensure that submit is blocked properly * [ui/fancyForms] escalate soft errors on failed submit * [ui/fancyForms] bind handlers to this in constructor * [uiBootstrap/tooltip] describe the new error handling * [ui/confirmModalPromise] use more sinon assertions * [$http] resp => data before old .success() and .error() handlers * [indices/createWizard] apply callAfterBindings workarounds
2017-08-25 23:50:11 +02:00
"angular": "1.6.5",
[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",
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",
"autoprefixer": "6.5.4",
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 Jest 22.0.6 (#16041)
2018-01-16 09:26:34 +01:00
"babel-jest": "^22.0.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
"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",
[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
"body-parser": "1.12.0",
[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",
Update brace to 0.10.0 (#15060)
2017-11-22 12:01:14 +01:00
"brace": "0.10.0",
Bump bunyan version to 1.7.1 Unfortunately, the old version of bunyan we were depending on has a compilation failure during npm install, so we need to upgrade it in order to get more builds.
2016-03-09 19:40:43 +01:00
"bunyan": "1.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
"cache-loader": "1.0.3",
[CLI] Readable logs on Windows with chalk colors (#15557) * [colors] try new cli colors * [colors] try magentaBright instead of magenta * [colors] try white for log text * [colors] replace all remaining ansicolors with chalk * [colors] try yellowBright instead of yellow * remove ansicolors from package.json * [tests] attempt to fix tests * [tests] attempt to fix tests again * [color] backgrounds, cleanup
2017-12-15 21:35:10 +01:00
"chalk": "2.3.0",
[build] Check SHA sum of downloaded node package (#7746) * fix #7136 - check SHA of downloaded node binaries * skips download if --skip-node-download cli argument is present
2016-10-29 17:10:46 +02:00
"check-hash": "1.0.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",
[test] Added draggable container, item, and handles tests.
2016-05-12 11:46:34 +02:00
"dragula": "3.7.0",
[npm] upgrade elasticsearch-js (#17219)
2018-03-19 19:49:52 +01:00
"elasticsearch": "^14.2.1",
"elasticsearch-browser": "^14.2.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",
[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",
[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
"glob": "5.0.13",
[glob] switch out glob for glob-all
2016-02-12 04:01:14 +01:00
"glob-all": "3.0.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
"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",
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",
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",
Plugin installer proxy support (#12753) Proxy support for plugin installer
2017-07-26 09:35:00 +02:00
"http-proxy-agent": "1.0.0",
Make plugin installer proxy work for HTTPS (#15588)
2018-03-07 03:02:43 +01:00
"https-proxy-agent": "2.1.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",
[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
"jade": "1.11.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
"jade-loader": "0.8.0",
[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",
"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",
Replace "marked" with "markdown-it" (#13623) * add markdown functional test * update markdown vis to use markdown-it * migrate markdown angular filter to markdown-it * place other uses of marked and remove dependency * update breaking changes documenation and set linkify to true
2017-08-23 00:29:40 +02:00
"markdown-it": "8.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
"minimatch": "2.0.10",
"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",
[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",
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": "^16.2.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",
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-anything-sortable": "^1.7.3",
"react-color": "^2.13.8",
"react-dom": "^16.2.0",
"react-grid-layout": "^0.16.2",
"react-input-range": "^1.3.0",
"react-markdown": "^3.1.4",
"react-redux": "^5.0.6",
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-select": "^1.2.0",
"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",
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": "3.7.2",
"redux-actions": "2.2.1",
"redux-thunk": "2.2.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",
[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
"request": "2.61.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",
[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
"rxjs": "5.4.3",
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",
Fix semver version that was incorrectly bumped This change accidentally happened when bumping the version of Kibana.
2016-09-08 16:31:44 +02:00
"semver": "5.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
"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",
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",
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
"uglifyjs-webpack-plugin": "0.4.6",
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",
[pack installer] various tweaks from PR review
2016-03-04 16:31:58 +01:00
"validate-npm-package-name": "2.2.2",
Bumped Vega dependencies (#16891)
2018-03-02 02:16:58 +01:00
"vega-lib": "^3.1.0",
"vega-lite": "^2.1.3",
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",
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",
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": {
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",
Upgrade eslint (#15796) * [eslint] upgrade eslint-related deps * [eslint] remove snake_case destructured keys
2017-12-30 10:03:28 +01:00
"@elastic/eslint-import-resolver-kibana": "1.0.0",
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-plugin-kibana-custom": "link:packages/eslint-plugin-kibana-custom",
[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",
[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",
Bump backport dependency and add .backportrc.json (#15417)
2017-12-08 10:20:36 +01:00
"backport": "2.2.0",
Add timelion tests
2016-08-15 20:29:17 +02:00
"chai": "3.5.0",
[esArchiver] combine elasticDump and ScenarioManager (#10359) * As a part of bringing functional testing to plugins, esArchiver gives these plugins a way to capture and reload es indexes without needing to write a bunch of custom code. It works similarly to the elasticDump and ScenarioManager tools that it replaces. Differences: - Streaming implementation allows for much larger archives - CLI for creating and using archives - Configurable archive location - Stores the data in gzipped files (better for source control, searching, large archives) - Automatically identifies and upgrades Kibana config documents Methods: - `#load(name)`: import an archive - `#loadIfNeeded(name)`: import an archive, but skip the documents what belong to any existing index - `#unload(name)`: delete the indexes stored in an archive CLI operations: - `./bin/es_archiver save <name> [index patterns...]`: save the mapping and documents in one or more indexes that match the wild-card patterns into an the `<name>` archive - `./bin/es_archiver load <name>`: load the mapping and documents from the `<name>` archive * [functional_tests/common/nagivate] check for statusPage * [es_archiver] move bins into new scripts dir * [functional_tests/apps/context] use esArchiver * [esArchiver] general improvements after showing to a few folks - remove auto-upgrading config doc logic (until we have better access to kibana version info) - export unload command - remove preemptive checks in favor of reacting to errors - use type "doc" vs "hit" for doc records (consistency) - wrote a bunch of pending tests to think though and plan * [esArchiver] make log a stream that writes to itself * [esArchiver] fill in stats and archive format tests * [esArchiver] splitup action logic * [esArchiver/cli] fix cli --help output and comment * [esArchiver] remove type-based param coercion * [esArchiver/log] use strings for log levels * [esArchvier] remove unused var * [esArchiver/indexDocRecordsStream] add tests * [esArchive] fill in remaining tests * [esArchiver] fix dem tests * [eslint] remove unused vars * [esArchiver/loadIfNeeded] fix call to load() * [esArchiver] remove loadDumpData helpers
2017-03-27 21:29:14 +02:00
"chance": "1.0.6",
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",
Bumped chromedriver to 2.36 which fixes bustage on Chrome 65. (#17252)
2018-03-19 20:09:03 +01:00
"chromedriver": "2.36",
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",
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",
Add "recently accessed" to Kibana Home (#16556) * kbn history * put Add Data section in panel and move to seperate component * RecentlyAccessed component * complete circle with recently accessed dashboards * record visualizations in recent accessed history * render recently accessed * do not show recently accessed panel when no recently accessed history * add test cases for home feature panels * render dropdown when more than 5 items * only add saved search when id is provided * remove border around add data cards, move set up index patterns to under cards * add dot icon to seperate recently accessed items * fix white space issues * add timelion sheet to recently accessed * fix spelling errors, better name space styles, enhance dropdown label * avoid cutting off bottom of letters, do not display separators with small screen * wrap separator (EuiIcon) in EuiText component so it is even link text * track history by object id to avoid duplicate entries when saved object is renamed * align link dropdown on right side * shift popover placement for small screens * update recently_accessed tests to look for nodes insted of using snapshots * move id to variable * change 'Recently accessed' to 'Recently viewed' * change more dropdown label * add max-width to flex item * include /app in link path, use arrow functions to remove bind in react props * add to recently accessed when saved object is saved * address cjcenizal's comments on test assertion order and react imports
2018-03-08 20:48:05 +01:00
"enzyme-to-json": "3.3.0",
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 22.0.6 (#16041)
2018-01-16 09:26:34 +01:00
"eslint-plugin-jest": "^21.6.2",
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",
lint: error on innerHTML and family (#16477) * lint for innerHTML and family Browser apis like innerHTML and document.write are dangerous when used incorrectly, so we should not be using them unless we explicitly opt-out of the linting rule on a case by case basis. * add no-unsanitized to eslint peerDependencies
2018-02-04 14:38:37 +01:00
"eslint-plugin-no-unsanitized": "^2.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",
Adding firefox to test suite (#17195) * Created general driver to accept an argument select the driver to run. * Added environment variable for driver, changed package.json to use custim leadfoot, and made changes to browserdriver to use any driver. * Made changes per PR. * Fixed all nits.
2018-03-17 04:05:10 +01:00
"geckodriver": "1.10.0",
[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",
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",
"grunt-aws-s3": "0.14.5",
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
"grunt-babel": "6.0.0",
[npm] lock down package versions in package.json
2015-06-05 01:19:31 +02:00
"grunt-cli": "0.1.13",
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-contrib-clean": "1.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
"grunt-contrib-copy": "0.8.1",
[npm] bump grunt-esvm (#15937)
2018-01-09 21:10:33 +01:00
"grunt-esvm": "3.2.12",
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",
Bump grunt-run to 0.7.0 (#12127)
2017-06-02 16:15:45 +02:00
"grunt-run": "0.7.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
"grunt-simple-mocha": "0.4.0",
[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",
[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 22.0.6 (#16041)
2018-01-16 09:26:34 +01:00
"jest": "^22.0.6",
"jest-cli": "^22.0.6",
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",
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
"jsdom": "9.9.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",
Adding firefox to test suite (#17195) * Created general driver to accept an argument select the driver to run. * Added environment variable for driver, changed package.json to use custim leadfoot, and made changes to browserdriver to use any driver. * Made changes per PR. * Fixed all nits.
2018-03-17 04:05:10 +01:00
"leadfoot": "silne30/leadfoot#validation_for_response_in_ff58",
Upgrade license checker (#16147)
2018-01-19 08:49:55 +01:00
"license-checker": "^16.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
"load-grunt-config": "0.19.2",
[npm] upgrade elasticsearch/elasticsearch-browser packages (#17119) * [npm] upgrade elasticsearch/elasticsearch-browser packages * [es/patchKibanaIndex] update tests to expect indices.getMapping * [npm] use ^ version range for elasticsearch(-browser) packages * [es/patchKibanaIndex/tests] expand assertion
2018-03-15 00:11:18 +01:00
"makelogs": "^4.0.4",
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
"marked-text-renderer": "0.1.0",
[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
"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",
Ignore OS-specific files in other operating systems. Fixes #4460
2016-03-18 01:05:15 +01:00
"ncp": "2.0.0",
Bump versions on a handful of node modules
2016-09-06 22:10:54 +02:00
"nock": "8.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",
Upgrade to Prettier 1.11.1 (#16956)
2018-03-05 06:59:34 +01:00
"prettier": "^1.11.1",
Add timelion tests
2016-08-15 20:29:17 +02:00
"proxyquire": "1.7.10",
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",
[npm] upgrade sinon to 1.17.2
2015-11-10 23:49:38 +01:00
"sinon": "1.17.2",
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
"source-map": "0.5.6",
"source-map-support": "0.2.10",
[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",
[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
"supertest": "3.0.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
"supertest-as-promised": "2.0.2",
Lock chromedriver and tree-kill (#11660)
2017-05-10 03:51:36 +02:00
"tree-kill": "1.1.0",
Port `kbn-pm` to TypeScript. (#16732)
2018-02-21 10:09:30 +01:00
"ts-jest": "^22.0.4",
"typescript": "^2.7.2",
[dev/mocha/junit] report real skipped test count and errors from hooks (#15465) * [dev/mocha/junit] report real skipped test count and errors from hooks * typo
2017-12-07 20:09:22 +01:00
"xml2js": "0.4.19",
[@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
"xmlbuilder": "9.0.4"
lets just test in 0.12 for now
2015-06-06 01:20:49 +02:00
},
"engines": {
Bumps node to 8.9.4 (#16981) Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co>
2018-03-06 01:19:02 +01:00
"node": "8.9.4",
Switch to Yarn (#15485) * switch to yarn * cleanup misc references to npm * [yarn] loosen dependency ranges so yarn will merge more deps * fix linting error now that moment uses ESM * [licenses] font-awesome changed the format of its license id * Use local yarn * Misc fixes * eslintignore built yarn file * Remove mkdir which doesn't do what it should do * Check build without upgrading lots of versions * Fix license check * too many moments * Better description * Review fixes * Lock to angular@1.6.5 * More specific version locks * Revert "More specific version locks" This reverts commit 11ef81102e3206fe1c83d03e5ff8345445a47fd0. * Revert "Lock to angular@1.6.5" This reverts commit 3ade68c14c6d3d3562aa6946959c440e4dfed17b. * rm yarn.lock; yarn * Forcing a specific version of React, Angular, Moment * Using vendored version of yarn in ci * Use --frozen-lockfile * fixes
2018-01-10 13:23:43 +01:00
"yarn": "^1.3.2"
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