zulip/package.json

39 lines
920 B
JSON
Raw Normal View History

{
"name": "zulip",
"version": "0.0.0",
"license": "Apache-2.0",
"description": "",
"main": "",
"dependencies": {
"handlebars": "1.3.0",
"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",
"jquery": "1.12.1",
"jquery-validation": "1.15.1",
"webpack": "1.12.2"
},
"devDependencies": {
"casperjs": "1.1.3",
"cssstyle": "0.2.29",
"eslint": "^3.9.1",
"htmlparser2": "3.8.3",
"istanbul": "0.4.0",
"jsdom": "9.4.1",
"nwmatcher": "1.3.6",
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
"phantomjs-prebuilt": "2.1.7",
"webpack-dev-server": "1.12.1",
"xmlhttprequest": "1.5.0"
},
"scripts": {
"lint": "eslint --quiet",
"lint-loud": "eslint static/js frontend_tests"
},
"repository": {
"type": "git",
"url": "https://github.com/zulip/zulip.git"
}
}