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

271 lines
8.2 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,
Bump to verson 6.0.0-alpha1
2016-09-08 16:23:22 +02:00
"version": "6.0.0-alpha1",
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>",
"Tim Sullivan <tim@elastic.co>"
Consolidating package.json adding JSON logger
2015-01-07 21:48:58 +01:00
],
"scripts": {
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",
"test:ui:runner": "grunt test:ui:runner",
[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",
Create visual_regression test suite. - Add test:visualRegression npm script. - Split up test:visualRegression grunt task into takeScreenshots and buildGallery subtasks. - Add intern_visual_regression.js test file. - Rename api_itern.js -> intern_api.js for consistency. - Refactor delayed exports logic for readability. - Refactor common.js page object to use ES2015 Class.
2016-06-22 01:59:43 +02:00
"test:visualRegression": "grunt test:visualRegression",
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",
[cli] Cross-platform CLI execution of "npm start". Fixes #4962
2016-03-17 18:19:36 +01:00
"start": "sh ./bin/kibana --dev",
[grunt/precommit] added check for snake_case filenames
2015-11-23 21:07:10 +01:00
"precommit": "grunt precommit",
[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",
[npm] rename esWithPlugins script
2016-01-16 01:54:15 +01:00
"elasticsearchWithPlugins": "grunt esvm:withPlugins:keepalive",
[npm] added lint and lintroller scripts
2015-09-23 03:58:14 +02:00
"lint": "grunt eslint:source",
Add scripts for running mocha with babel and optional debugging
2015-12-02 18:28:27 +01:00
"lintroller": "grunt eslint:fixSource",
Makelogs as a dev dependency Different versions of makelogs are required based on the current Kibana branch/version, so we now include it as a dev dependency that we can version accordingly. There is also an npm script for makelogs so you do not need to traverse the node_modules bin directory.
2016-02-29 20:12:58 +01:00
"makelogs": "makelogs",
[mocha] move setup work into module with https://github.com/elastic/kibana/pull/5553 we added command line flags the told mocha it was supposed to use babel. This changes the strategy here and instead uses mocha's -r option (and it's mocha.opts file to specify it). This means that using mocha directly from the command line still works, and that we have a place where we can do other setup work.
2016-01-13 00:23:32 +01:00
"mocha": "mocha",
Merge branch 'master' of github.com:elastic/kibana into implement/npmCleanTask
2016-02-08 23:20:48 +01:00
"mocha:debug": "mocha --debug-brk",
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",
Remove libsass as a dependency (#9803) Remove libsass as a dependency libsass is platform specific, therefore we can not ship it as a dependency. Instead, we will commit the compiled CSS for the UI Framework to the repository. This is updated when running `npm run uiFramework:start` which also starts the docs site. Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co>
2017-01-10 05:27:54 +01:00
"uiFramework:start": "grunt uiFramework:start"
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 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
"@bigfunger/decompress-zip": "0.2.0-stripfix3",
[ingest] added missing dependency
2016-02-05 23:58:31 +01:00
"@bigfunger/jsondiffpatch": "0.1.38-webpack",
Bump datemath to 2.3.0
2016-06-15 22:38:24 +02:00
"@elastic/datemath": "2.3.0",
Bump httpolyglot to use our fork (#10225)
2017-02-07 17:29:55 +01:00
"@elastic/httpolyglot": "0.1.2-elasticpatch1",
[webpack] upgrade to @elastic/webpack-directory-name-as-main v2 (#9601) * [webpack] upgrade to @elastic/webpack-directory-name-as-main v2 * bump @elastic/webpack-directory-name-as-main * import browser mocha with webpackShim `import 'mocha'` will resolve to `mocha/index.js`, which points to `mocha/lib/mocha.js`, the node version of mocha. This will not work in the browser. Since ng_mock is browser code, we need the mocha build for the browser, which lives at `mocha/mocha.js`. This isn't referenced at all in the package.json file, but is references in the bower.json file. Webpack, however, doesn't observe the bower config, so we need to specifically reach into the mocha package and point to the `mocha/mocha.js` file.
2016-12-22 17:32:03 +01:00
"@elastic/webpack-directory-name-as-main": "2.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
"@spalger/filesaver": "1.1.2",
"@spalger/leaflet-draw": "0.2.3",
"@spalger/leaflet-heat": "0.1.3",
[numeral] replace with fork to fix #4857
2015-09-18 23:03:18 +02:00
"@spalger/numeral": "^2.0.0",
Include @spalger/test-subj-selector in builds This file is used by the jquery webpackshim, but it was being included as a devDependency, so it wasn't making it into the final builds. Fixes #5636
2015-12-10 19:57:34 +01:00
"@spalger/test-subj-selector": "0.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
"@spalger/ui-ace": "0.2.3",
[API] Use JSONStream instead of manually stringifying
2016-04-12 18:26:57 +02: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",
Merge branch 'master' into angularUpgrade
2015-10-15 15:32:20 +02:00
"angular": "1.4.7",
[field format] Lock color version, allow deletion from any position
2015-09-24 16:31:11 +02:00
"angular-bootstrap-colorpicker": "3.0.19",
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",
[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
"ansicolors": "0.3.2",
[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
"autoprefixer": "6.5.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
"autoprefixer-loader": "2.0.0",
babel 6 upgrade (#9702) * [npm] upgrade babel The upgrade to babel 6 requires an upgrade to all of the associated modules, which meant that a few other things changed at the same time. The most notable is the way that we handle our babel-options, which is now done with an npm module and includes using the babel-loader's "presets" query string param. This meant changes to the babel_options.js module and extending it to help setting up the "babel-register" module, which was previously copy-pasted in several places. * [mtodules] upgrade to support babel6 module semantics * [eslint] fix lint errors * [babel] ignoer massive fixture files * [cli/errors] use Object.setPrototypeOf since subclassing Error is broken * [babel] Upgrading core babel libraries [babel] Use WIP babel-6-fix branch of babel-preset-kibana * Fix broken test * [babel] Reverse unnecessary module.exports changes * Fix notifier * Use babel presets and plugins directly * [babel/options] resolve preset/plugins paths for better plugin compatibility * [babel/options] use babel-preset-env for correct node settings * [babel] cache babel compilation in webpack like we thought we were
2017-02-09 22:48:55 +01:00
"babel-cli": "6.18.0",
"babel-core": "6.21.0",
"babel-loader": "6.2.10",
"babel-plugin-add-module-exports": "0.2.1",
"babel-polyfill": "6.20.0",
"babel-preset-env": "1.1.8",
"babel-preset-es2015": "6.22.0",
"babel-preset-es2015-node": "6.1.1",
"babel-preset-react": "6.22.0",
"babel-preset-stage-1": "6.22.0",
"babel-register": "6.18.0",
"babel-runtime": "6.20.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",
[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
"boom": "2.8.0",
"brace": "0.5.1",
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",
[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",
"css-loader": "0.17.0",
"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 (#10509)
2017-02-22 18:40:29 +01:00
"elasticsearch": "13.0.0-beta2",
"elasticsearch-browser": "13.0.0-beta2",
[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",
"exports-loader": "0.6.2",
"expose-loader": "0.7.0",
"extract-text-webpack-plugin": "0.8.2",
"file-loader": "0.8.4",
"font-awesome": "4.4.0",
Moving front-end code out of devDependencies (#10670) * Moving front-end code out of devDependencies * removing range specifier * overriding ua-parser-js@0.7.12 to MIT * upgrading react-color; upgrading react; upgrading pui-tooltip;
2017-03-03 17:13:46 +01:00
"flot-charts": "0.8.3",
[optimizer] move to querystring-browser package for up-to-date api Webpack automatically injects libraries to support many node.js APIs in the browser using the https://github.com/webpack/node-libs-browser package. This package uses https://github.com/mike-spainhower/querystring for the querystring module, but that module hasn't been updated in 4 years and doesn't support the modern querystring api. This change points to the https://github.com/mathiasvr/querystring package instead, which is up to date (specifically it supports the `encodeURIComponent` option of [`querystring.stringify`](https://nodejs.org/api/querystring.html#querystring_querystring_stringify_obj_sep_eq_options).
2016-09-09 23:10:50 +02:00
"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",
"gridster": "0.5.6",
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",
"hapi": "14.2.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
"imports-loader": "0.6.4",
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",
"jade-loader": "0.7.1",
"joi": "6.6.1",
"jquery": "2.1.4",
"js-yaml": "3.4.1",
[npm] json-loader is a production dependency
2015-10-29 18:30:39 +01:00
"json-loader": "0.5.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
"json-stringify-safe": "5.0.1",
"jstimezonedetect": "1.0.5",
"leaflet": "0.7.5",
[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 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
"less-loader": "2.2.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
"lodash": "3.10.1",
Bump versions on a handful of node modules
2016-09-06 22:10:54 +02:00
"marked": "0.3.6",
[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",
Bump moment.js to latest version
2016-06-14 13:46:32 +02:00
"moment": "2.13.0",
"moment-timezone": "0.5.4",
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",
[server] generate and manage uuid
2016-03-15 23:36:39 +01:00
"node-uuid": "1.4.7",
[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
"pegjs": "0.9.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
"postcss-loader": "1.2.1",
Moving front-end code out of devDependencies (#10670) * Moving front-end code out of devDependencies * removing range specifier * overriding ua-parser-js@0.7.12 to MIT * upgrading react-color; upgrading react; upgrading pui-tooltip;
2017-03-03 17:13:46 +01:00
"pui-react-overlay-trigger": "7.5.4",
"pui-react-tooltip": "7.5.4",
[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",
Moving front-end code out of devDependencies (#10670) * Moving front-end code out of devDependencies * removing range specifier * overriding ua-parser-js@0.7.12 to MIT * upgrading react-color; upgrading react; upgrading pui-tooltip;
2017-03-03 17:13:46 +01:00
"react": "15.4.2",
"react-ace": "3.7.0",
"react-addons-test-utils": "15.4.2",
"react-anything-sortable": "1.6.1",
"react-color": "2.11.1",
"react-dom": "15.4.2",
"react-markdown": "2.4.2",
"react-redux": "4.4.5",
"react-router": "2.0.0",
"react-router-redux": "4.0.4",
"react-select": "1.0.0-rc.1",
"react-sortable": "1.1.0",
"reactcss": "1.0.7",
"redux": "3.0.0",
"redux-thunk": "0.1.0",
[npm] remove package ranges Fixes #4866 As recently discussed in https://github.com/elastic/kibana/issues/4824 we have had a fair number of challenges with dependencies shipping breaking changes or broken code within the semver ranges which should prevent them. Nobody is perfect, we don't expect that, but as Kibana grows the number of modules does too. The output of npm ls is currently over 1100 lines, meaning we are very exposed to the semver ranges specified. While we may actually use a shrinkwrap file at some point, or implement something like uber's custom shrinkwrap utility, the only issues we have faced have been caused by top level dependencies (especially the very fast-moving ones).
2015-09-05 10:49:36 +02:00
"request": "2.61.0",
"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",
[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
"rjs-repack-loader": "1.0.6",
"script-loader": "0.6.1",
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",
Moving front-end code out of devDependencies (#10670) * Moving front-end code out of devDependencies * removing range specifier * overriding ua-parser-js@0.7.12 to MIT * upgrading react-color; upgrading react; upgrading pui-tooltip;
2017-03-03 17:13:46 +01:00
"simianhacker-react-resize-aware": "1.0.11",
[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
"style-loader": "0.12.3",
"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",
[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",
[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
"url-loader": "0.5.6",
[pack installer] various tweaks from PR review
2016-03-04 16:31:58 +01:00
"validate-npm-package-name": "2.2.2",
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",
[npm] use elastic webpack fork (#9540)
2016-12-19 20:54:04 +01:00
"webpack": "github:elastic/webpack#fix/query-params-for-aliased-loaders",
Move wreck from dev dependencies to dependencies Fixes #5777
2015-12-28 18:25:38 +01:00
"whatwg-fetch": "0.9.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
"wreck": "6.2.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": {
[eslint] enable object-curly-spacing and no-global-assign (#9486) * [eslint] update eslint config to 0.3.0 * [eslint] autofix * [fixtures/hits] reformat to comply with max-len lint rule
2016-12-14 21:29:32 +01:00
"@elastic/eslint-config-kibana": "0.3.0",
[ngMock] Upgraded ng mock
2015-10-19 15:39:34 +02:00
"angular-mocks": "1.4.7",
[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
"auto-release-sinon": "1.0.3",
Upgrade eslint (#9357) * upgrade eslint, all related deps, and config files * replace gruntify-eslint with basic eslint-cli wrapper * arrow-IIFEs must be invoked outside of the parens * move import statements before their use * reindent to satisfy new indentation check algorithm * place missing semicolon * ignore copy-pasted decode geohash code * [grunt/eslint] fix argument spacing * [gurnt/eslint] add comment about contents of report * [grunt/tasks] use `export default`
2016-12-12 21:44:18 +01:00
"babel-eslint": "6.1.2",
Add timelion tests
2016-08-15 20:29:17 +02:00
"chai": "3.5.0",
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",
[npm] update chromedriver The latest macOS version of Chrome is incompatible with the version of chromedriver we currently depend on, so this updates it.
2016-10-14 23:03:23 +02:00
"chromedriver": "2.24.1",
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",
"del": "1.2.1",
New dashboard tests using elasticdump
2016-05-26 23:32:53 +02:00
"elasticdump": "2.1.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
"enzyme": "2.7.0",
Upgrade eslint (#9357) * upgrade eslint, all related deps, and config files * replace gruntify-eslint with basic eslint-cli wrapper * arrow-IIFEs must be invoked outside of the parens * move import statements before their use * reindent to satisfy new indentation check algorithm * place missing semicolon * ignore copy-pasted decode geohash code * [grunt/eslint] fix argument spacing * [gurnt/eslint] add comment about contents of report * [grunt/tasks] use `export default`
2016-12-12 21:44:18 +01:00
"eslint": "3.11.1",
[eslint] enable object-curly-spacing and no-global-assign (#9486) * [eslint] update eslint config to 0.3.0 * [eslint] autofix * [fixtures/hits] reformat to comply with max-len lint rule
2016-12-14 21:29:32 +01:00
"eslint-plugin-babel": "4.0.0",
Upgrade eslint (#9357) * upgrade eslint, all related deps, and config files * replace gruntify-eslint with basic eslint-cli wrapper * arrow-IIFEs must be invoked outside of the parens * move import statements before their use * reindent to satisfy new indentation check algorithm * place missing semicolon * ignore copy-pasted decode geohash code * [grunt/eslint] fix argument spacing * [gurnt/eslint] add comment about contents of report * [grunt/tasks] use `export default`
2016-12-12 21:44:18 +01:00
"eslint-plugin-mocha": "4.7.0",
[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",
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",
bump grunt-esvm elasticsearch 5.x uses a slightly different log format, so grunt-esvm needed an update.
2016-09-14 19:53:02 +02:00
"grunt-esvm": "3.2.6",
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",
"grunt-run": "0.6.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",
Update visualRegression task to use Handlebars instead of DoT templates. - This eliminates the annoying DoT messages from the terminal.
2016-06-21 19:36:13 +02:00
"handlebars": "4.0.5",
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
"highlight.js": "9.0.0",
"history": "2.1.1",
"html-loader": "0.4.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",
Update intern version to 3.2.3, fix failing test
2016-06-14 17:41:37 +02:00
"intern": "3.2.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
"istanbul-instrumenter-loader": "0.1.3",
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",
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
"karma": "1.2.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
"karma-chrome-launcher": "0.2.0",
"karma-coverage": "0.5.1",
"karma-firefox-launcher": "0.1.6",
"karma-ie-launcher": "0.2.0",
"karma-mocha": "0.2.0",
"karma-safari-launcher": "0.1.1",
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
"keymirror": "0.1.1",
Upgrade to Node 6.4.0 * Updated dependencies to include graceful-fs ~4.0 * Replaced deprecated grunt-s3 package with suggested grunt-aws-s3 * Update licenses task to better support npm 3 Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co>
2016-07-21 00:00:30 +02:00
"license-checker": "5.1.2",
"load-grunt-config": "0.19.2",
Bump makelogs to 3.2.3 (#10510)
2017-02-22 18:22:36 +01:00
"makelogs": "3.2.3",
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",
"mocha": "2.5.3",
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",
[npm] bump makelogs (#10279)
2017-02-10 09:09:11 +01:00
"node-sass": "3.8.0",
Bump node to 6.9.5 (#10135)
2017-02-01 18:54:57 +01:00
"npm": "3.10.10",
[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
"portscanner": "1.0.0",
Add timelion tests
2016-08-15 20:29:17 +02:00
"proxyquire": "1.7.10",
Remove libsass as a dependency (#9803) Remove libsass as a dependency libsass is platform specific, therefore we can not ship it as a dependency. Instead, we will commit the compiled CSS for the UI Framework to the repository. This is updated when running `npm run uiFramework:start` which also starts the docs site. Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co>
2017-01-10 05:27:54 +01:00
"sass-loader": "4.0.0",
Add visual regression screenshot gallery. - Add 'test:visualRegression' grunt task. - Run 'test:visualRegression' as part of npm script 'test'. - Add 'clean:screenshots task'. - Clean screenshots/session when funtional tests are run.
2016-06-10 06:36:09 +02:00
"simple-git": "1.37.0",
[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",
"supertest": "1.2.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",
"webpack-dev-server": "1.14.1"
lets just test in 0.12 for now
2015-06-06 01:20:49 +02:00
},
"engines": {
Bump node to 6.9.5 (#10135)
2017-02-01 18:54:57 +01:00
"node": "6.9.5",
"npm": "3.10.10"
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