Mirror
/
zulip
mirror of https://github.com/zulip/zulip.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
zulip/package.json

35 lines
812 B
JSON
Raw Normal View History

Install node dependencies using npm. The node packages 'jQuery' and 'jquery' are different--'jQuery' is the legacy support package that is needed for Zulip so the require statements in the tests were updated. Travis uses node 4.0 by default and we are using 0.10, so the command to install the correct version had to be added to the .travis.yml file.
2015-10-26 17:16:26 +01:00
{
"name": "zulip",
"version": "0.0.0",
"license": "Apache-2.0",
"description": "",
"main": "",
npm: Split out production-only dependencies.
2016-08-05 07:10:41 +02:00
"dependencies": {
Remove the committed handlebars package and install it via npm.
2015-10-26 17:17:14 +01:00
"handlebars": "1.3.0",
npm: Split out production-only dependencies.
2016-08-05 07:10:41 +02:00
"i18next": "3.0.0",
"i18next-parser": "0.7.0",
"i18next-xhr-backend": "0.5.4",
"i18next-browser-languagedetector": "0.3.0",
"i18next-localstorage-cache": "0.3.0",
Upgrade jQuery to 1.12.1 and fetch from node_modules. Fixes: #1196.
2016-08-24 21:49:53 +02:00
"jquery": "1.12.1",
Migrate jquery-validate to a current version installed via npm.
2016-08-25 23:21:15 +02:00
"jquery-validation": "1.15.1",
npm: Split out production-only dependencies.
2016-08-05 07:10:41 +02:00
"webpack": "1.12.2"
},
"devDependencies": {
Add istanbul for running node coverage reports. `tools/test-js-with-node cover` needs istanbul to be installed in order to work; we might as well install it by default rather than having it be an extra step users need to deal with. Of course, since this is only needed in the development environment, this could suggest we want to fork/conditionalize package.json, but I think for now it's reasonable to just install everything we use somewhere -- the npm list is still pretty short and we have that issue anyway with webpack-dev-server.
2015-11-19 18:21:05 +01:00
"istanbul": "0.4.0",
provision: Use NVM to install node and npm. NVM takes a specific node version and installs the node package and a corresponding compatible npm package. We use it in a somewhat hackish way to install node/npm globally with a pinned version, since that's how we actually want to consume node in our development environment. Other details: - Travis CI now is configured to use the version of node installed by provision; the easiest way to do this was to sabotage the existing node installation. - jsdom is upgraded to a current version, which both requires recent node and also is required for the tests to pass with recent node. This fixes running the node tests on Xenial. Fixes #1498. [tweaked by tabbott]
2016-09-21 08:44:01 +02:00
"jsdom": "9.4.1",
Install node dependencies using npm. The node packages 'jQuery' and 'jquery' are different--'jQuery' is the legacy support package that is needed for Zulip so the require statements in the tests were updated. Travis uses node 4.0 by default and we are using 0.10, so the command to install the correct version had to be added to the .travis.yml file.
2015-10-26 17:16:26 +01:00
"xmlhttprequest": "1.5.0",
"nwmatcher": "1.3.6",
"htmlparser2": "3.8.3",
Add webpack build process.
2015-10-26 17:11:44 +01:00
"cssstyle": "0.2.29",
Upgrade caspersjs to version 1.1.3. (w/acrefoot) (Most of this work was done by acrefoot in an earlier branch. I took over the branch to fix casper tests that were broken during the upgrade (which were fixed in a different commit). I also made most of the changes to run-casper.) This also upgrades phantomjs to 2.1.7. The huge structural change here is that we no longer vendor casperjs or download phantomjs with our own script. Instead, we just use casperjs and phantomjs from npm, via package.json. Another thing that we do now is run casperjs tests individually, so that we don't get strange test flakes from test interactions. (Tests can still influence each other in terms of changing data, since we don't yet have code to clear the test database in between tests.) A lot of this diff is just removing files and obsolete configurations. The main new piece is in package.json, which causes npm to install the new version. Also, run-casper now runs files individually, as mentioned above. We had vendored casperjs in the past. I didn't bring over any of our changes. Some of the changes were performance-related (primarily 5fd58cf24927359dce26588d59690c40c6ce6d4c), so the upgraded version may be slower in some instances. (I didn't do much measurement of that, since most of our slowness when running tests is about the setup environment, not casper itself.) Any bug fixes that we may have implemented in the past were either magically fixed by changes to casper itself or by improvements we have made in the tests themselves over the years. Tim tested the Casper suite on his machine and running the full Casper test suite is faster than it was before this change (1m30 vs. 1m50), so we're at least not regressing overall performance.
2016-10-07 18:20:59 +02:00
"webpack-dev-server": "1.12.1",
"phantomjs-prebuilt": "2.1.7",
"casperjs": "1.1.3"
Install node dependencies using npm. The node packages 'jQuery' and 'jquery' are different--'jQuery' is the legacy support package that is needed for Zulip so the require statements in the tests were updated. Travis uses node 4.0 by default and we are using 0.10, so the command to install the correct version had to be added to the .travis.yml file.
2015-10-26 17:16:26 +01:00
},
"scripts": {},
"repository": {
"type": "git",
"url": "https://github.com/zulip/zulip.git"
}
}