mirror_php/moodle
1
0
Fork 0
mirror of https://github.com/moodle/moodle.git synced 2025-01-17 21:49:15 +01:00
Code Issues Projects Releases Wiki Activity
moodle/npm-shrinkwrap.json

2023 lines
69 KiB
JSON
Raw Normal View History

MDL-52250 npm: shrinkwrap to lock down dependencies We've tried various approaches to lock down our dependencies and they have been flawed because dependencies in our included packages may not be locked down and previous attempts to do that have not been correct. With npm shrinkwrap we lock down versions so that any npm install will always install the exact same versions for all developers - see: https://docs.npmjs.com/cli/shrinkwrap (This is a lot like composer.lock for those more fluent with composer)
2015-12-03 17:00:50 +00:00
{
"name": "Moodle",
"dependencies": {
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"abbrev": {
"version": "1.0.7",
"from": "abbrev@>=1.0.0 <2.0.0",
"resolved": "https://registry.npmjs.org/abbrev/-/abbrev-1.0.7.tgz"
},
MDL-52127 js: check amd files with eslint grunt task I have spent quite a lot of time working through the current list of eslint options and configuring them for Moodle style and I think this is a very good basis to start us at (as well as taking some of out jshint options out with https://www.npmjs.com/package/polyjuice ). Thanks to Andrew Nicols, Mark Johnson and Frédéric Massart for some refinements. With this configuration the grunt build will fail if errors are present in the js (though you can of course tell jshint to ignore some errors, as I have done in admin/tool/lp/amd/src/competency_rule_points.js and defining the Y global in lib/amd/src/yui.js ). The grunt task will not report warnings by default, but a new --show-lint-warnings flag will help achieve that. Editor integrations/stanadalone eslint tool will surely be a better way of getting eslint errors rather than using the grunt task.
2016-05-11 10:19:30 +01:00
"acorn": {
"version": "3.2.0",
"from": "acorn@>=3.1.0 <4.0.0",
"resolved": "https://registry.npmjs.org/acorn/-/acorn-3.2.0.tgz"
},
"acorn-jsx": {
"version": "3.0.1",
"from": "acorn-jsx@>=3.0.0 <4.0.0",
"resolved": "https://registry.npmjs.org/acorn-jsx/-/acorn-jsx-3.0.1.tgz"
},
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"align-text": {
"version": "0.1.3",
"from": "align-text@>=0.1.0 <0.2.0",
"resolved": "https://registry.npmjs.org/align-text/-/align-text-0.1.3.tgz"
},
"amdefine": {
"version": "1.0.0",
"from": "amdefine@>=0.0.4",
"resolved": "https://registry.npmjs.org/amdefine/-/amdefine-1.0.0.tgz"
},
"ansi-color": {
"version": "0.2.1",
"from": "ansi-color@*",
"resolved": "https://registry.npmjs.org/ansi-color/-/ansi-color-0.2.1.tgz"
},
MDL-52127 js: check amd files with eslint grunt task I have spent quite a lot of time working through the current list of eslint options and configuring them for Moodle style and I think this is a very good basis to start us at (as well as taking some of out jshint options out with https://www.npmjs.com/package/polyjuice ). Thanks to Andrew Nicols, Mark Johnson and Frédéric Massart for some refinements. With this configuration the grunt build will fail if errors are present in the js (though you can of course tell jshint to ignore some errors, as I have done in admin/tool/lp/amd/src/competency_rule_points.js and defining the Y global in lib/amd/src/yui.js ). The grunt task will not report warnings by default, but a new --show-lint-warnings flag will help achieve that. Editor integrations/stanadalone eslint tool will surely be a better way of getting eslint errors rather than using the grunt task.
2016-05-11 10:19:30 +01:00
"ansi-escapes": {
"version": "1.4.0",
"from": "ansi-escapes@>=1.1.0 <2.0.0",
"resolved": "https://registry.npmjs.org/ansi-escapes/-/ansi-escapes-1.4.0.tgz"
},
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"ansi-regex": {
"version": "2.0.0",
"from": "ansi-regex@>=2.0.0 <3.0.0",
"resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz"
},
"ansi-styles": {
"version": "2.1.0",
"from": "ansi-styles@>=2.1.0 <3.0.0",
"resolved": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-2.1.0.tgz"
},
"argparse": {
"version": "0.1.16",
"from": "argparse@>=0.1.11 <0.2.0",
"resolved": "https://registry.npmjs.org/argparse/-/argparse-0.1.16.tgz",
"dependencies": {
"underscore.string": {
"version": "2.4.0",
"from": "underscore.string@>=2.4.0 <2.5.0",
"resolved": "https://registry.npmjs.org/underscore.string/-/underscore.string-2.4.0.tgz"
}
}
},
MDL-52127 js: check amd files with eslint grunt task I have spent quite a lot of time working through the current list of eslint options and configuring them for Moodle style and I think this is a very good basis to start us at (as well as taking some of out jshint options out with https://www.npmjs.com/package/polyjuice ). Thanks to Andrew Nicols, Mark Johnson and Frédéric Massart for some refinements. With this configuration the grunt build will fail if errors are present in the js (though you can of course tell jshint to ignore some errors, as I have done in admin/tool/lp/amd/src/competency_rule_points.js and defining the Y global in lib/amd/src/yui.js ). The grunt task will not report warnings by default, but a new --show-lint-warnings flag will help achieve that. Editor integrations/stanadalone eslint tool will surely be a better way of getting eslint errors rather than using the grunt task.
2016-05-11 10:19:30 +01:00
"array-union": {
"version": "1.0.1",
"from": "array-union@>=1.0.1 <2.0.0",
"resolved": "https://registry.npmjs.org/array-union/-/array-union-1.0.1.tgz"
},
"array-uniq": {
"version": "1.0.2",
"from": "array-uniq@>=1.0.1 <2.0.0",
"resolved": "https://registry.npmjs.org/array-uniq/-/array-uniq-1.0.2.tgz"
},
"arrify": {
"version": "1.0.1",
"from": "arrify@>=1.0.0 <2.0.0",
"resolved": "https://registry.npmjs.org/arrify/-/arrify-1.0.1.tgz"
},
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"asap": {
"version": "1.0.0",
"from": "asap@>=1.0.0 <1.1.0",
"resolved": "https://registry.npmjs.org/asap/-/asap-1.0.0.tgz"
},
"asn1": {
"version": "0.2.3",
"from": "asn1@>=0.2.3 <0.3.0",
"resolved": "https://registry.npmjs.org/asn1/-/asn1-0.2.3.tgz"
},
"assert-plus": {
"version": "0.1.5",
"from": "assert-plus@>=0.1.5 <0.2.0",
"resolved": "https://registry.npmjs.org/assert-plus/-/assert-plus-0.1.5.tgz"
},
"async": {
MDL-49817 grunt: handle multiple watched files changed at once Includes multiple changes to the shifter task to simplify and support this: * Use grunt.file for shifter yui 'module' detection rather than our own 70 line function * Use grunt.util.spawn rather than our own exec for shifter * Improve behaviour on various yui subdirectories We have to add the 'async' depndency to npm because we are running multiple async operations in the single task. We use async.eachSeries to run each shifter job sequentally (else the output would be unreadable when running async). We also run shifter in non-recursive mode on the module directory so its not building everything (thanks to Ryan for pointing this out!)
2016-01-21 14:21:13 +00:00
"version": "1.5.2",
"from": "async@*",
"resolved": "https://registry.npmjs.org/async/-/async-1.5.2.tgz"
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
},
"aws-sign2": {
"version": "0.6.0",
"from": "aws-sign2@>=0.6.0 <0.7.0",
"resolved": "https://registry.npmjs.org/aws-sign2/-/aws-sign2-0.6.0.tgz"
},
"balanced-match": {
"version": "0.3.0",
"from": "balanced-match@>=0.3.0 <0.4.0",
"resolved": "https://registry.npmjs.org/balanced-match/-/balanced-match-0.3.0.tgz"
},
"bl": {
"version": "1.0.0",
"from": "bl@>=1.0.0 <1.1.0",
"resolved": "https://registry.npmjs.org/bl/-/bl-1.0.0.tgz",
"dependencies": {
"readable-stream": {
"version": "2.0.5",
"from": "readable-stream@>=2.0.0 <2.1.0",
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-2.0.5.tgz"
}
}
},
MDL-52127 js: check amd files with eslint grunt task I have spent quite a lot of time working through the current list of eslint options and configuring them for Moodle style and I think this is a very good basis to start us at (as well as taking some of out jshint options out with https://www.npmjs.com/package/polyjuice ). Thanks to Andrew Nicols, Mark Johnson and Frédéric Massart for some refinements. With this configuration the grunt build will fail if errors are present in the js (though you can of course tell jshint to ignore some errors, as I have done in admin/tool/lp/amd/src/competency_rule_points.js and defining the Y global in lib/amd/src/yui.js ). The grunt task will not report warnings by default, but a new --show-lint-warnings flag will help achieve that. Editor integrations/stanadalone eslint tool will surely be a better way of getting eslint errors rather than using the grunt task.
2016-05-11 10:19:30 +01:00
"bluebird": {
"version": "3.4.0",
"from": "bluebird@>=3.1.1 <4.0.0",
"resolved": "https://registry.npmjs.org/bluebird/-/bluebird-3.4.0.tgz"
},
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"boom": {
"version": "2.10.1",
"from": "boom@>=2.0.0 <3.0.0",
"resolved": "https://registry.npmjs.org/boom/-/boom-2.10.1.tgz"
},
"brace-expansion": {
"version": "1.1.2",
"from": "brace-expansion@>=1.0.0 <2.0.0",
"resolved": "https://registry.npmjs.org/brace-expansion/-/brace-expansion-1.1.2.tgz"
},
"browserify-zlib": {
"version": "0.1.4",
"from": "browserify-zlib@>=0.1.4 <0.2.0",
"resolved": "https://registry.npmjs.org/browserify-zlib/-/browserify-zlib-0.1.4.tgz"
},
"builtin-modules": {
"version": "1.1.1",
"from": "builtin-modules@>=1.0.0 <2.0.0",
"resolved": "https://registry.npmjs.org/builtin-modules/-/builtin-modules-1.1.1.tgz"
},
MDL-52127 js: check amd files with eslint grunt task I have spent quite a lot of time working through the current list of eslint options and configuring them for Moodle style and I think this is a very good basis to start us at (as well as taking some of out jshint options out with https://www.npmjs.com/package/polyjuice ). Thanks to Andrew Nicols, Mark Johnson and Frédéric Massart for some refinements. With this configuration the grunt build will fail if errors are present in the js (though you can of course tell jshint to ignore some errors, as I have done in admin/tool/lp/amd/src/competency_rule_points.js and defining the Y global in lib/amd/src/yui.js ). The grunt task will not report warnings by default, but a new --show-lint-warnings flag will help achieve that. Editor integrations/stanadalone eslint tool will surely be a better way of getting eslint errors rather than using the grunt task.
2016-05-11 10:19:30 +01:00
"caller-path": {
"version": "0.1.0",
"from": "caller-path@>=0.1.0 <0.2.0",
"resolved": "https://registry.npmjs.org/caller-path/-/caller-path-0.1.0.tgz"
},
"callsites": {
"version": "0.2.0",
"from": "callsites@>=0.2.0 <0.3.0",
"resolved": "https://registry.npmjs.org/callsites/-/callsites-0.2.0.tgz"
},
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"camelcase": {
"version": "2.0.1",
"from": "camelcase@>=2.0.0 <3.0.0",
"resolved": "https://registry.npmjs.org/camelcase/-/camelcase-2.0.1.tgz"
},
"camelcase-keys": {
"version": "2.0.0",
"from": "camelcase-keys@>=2.0.0 <3.0.0",
"resolved": "https://registry.npmjs.org/camelcase-keys/-/camelcase-keys-2.0.0.tgz"
},
"caseless": {
"version": "0.11.0",
"from": "caseless@>=0.11.0 <0.12.0",
"resolved": "https://registry.npmjs.org/caseless/-/caseless-0.11.0.tgz"
},
"center-align": {
"version": "0.1.2",
"from": "center-align@>=0.1.1 <0.2.0",
"resolved": "https://registry.npmjs.org/center-align/-/center-align-0.1.2.tgz"
},
"chalk": {
"version": "1.1.1",
"from": "chalk@>=1.0.0 <2.0.0",
"resolved": "https://registry.npmjs.org/chalk/-/chalk-1.1.1.tgz"
},
"cli": {
"version": "0.6.6",
"from": "cli@>=0.6.0 <0.7.0",
"resolved": "https://registry.npmjs.org/cli/-/cli-0.6.6.tgz",
MDL-52250 npm: shrinkwrap to lock down dependencies We've tried various approaches to lock down our dependencies and they have been flawed because dependencies in our included packages may not be locked down and previous attempts to do that have not been correct. With npm shrinkwrap we lock down versions so that any npm install will always install the exact same versions for all developers - see: https://docs.npmjs.com/cli/shrinkwrap (This is a lot like composer.lock for those more fluent with composer)
2015-12-03 17:00:50 +00:00
"dependencies": {
"glob": {
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"version": "3.2.11",
"from": "glob@>=3.2.1 <3.3.0",
"resolved": "https://registry.npmjs.org/glob/-/glob-3.2.11.tgz"
MDL-52250 npm: shrinkwrap to lock down dependencies We've tried various approaches to lock down our dependencies and they have been flawed because dependencies in our included packages may not be locked down and previous attempts to do that have not been correct. With npm shrinkwrap we lock down versions so that any npm install will always install the exact same versions for all developers - see: https://docs.npmjs.com/cli/shrinkwrap (This is a lot like composer.lock for those more fluent with composer)
2015-12-03 17:00:50 +00:00
},
"minimatch": {
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"version": "0.3.0",
"from": "minimatch@>=0.3.0 <0.4.0",
"resolved": "https://registry.npmjs.org/minimatch/-/minimatch-0.3.0.tgz"
}
}
},
MDL-52127 js: check amd files with eslint grunt task I have spent quite a lot of time working through the current list of eslint options and configuring them for Moodle style and I think this is a very good basis to start us at (as well as taking some of out jshint options out with https://www.npmjs.com/package/polyjuice ). Thanks to Andrew Nicols, Mark Johnson and Frédéric Massart for some refinements. With this configuration the grunt build will fail if errors are present in the js (though you can of course tell jshint to ignore some errors, as I have done in admin/tool/lp/amd/src/competency_rule_points.js and defining the Y global in lib/amd/src/yui.js ). The grunt task will not report warnings by default, but a new --show-lint-warnings flag will help achieve that. Editor integrations/stanadalone eslint tool will surely be a better way of getting eslint errors rather than using the grunt task.
2016-05-11 10:19:30 +01:00
"cli-cursor": {
"version": "1.0.2",
"from": "cli-cursor@>=1.0.1 <2.0.0",
"resolved": "https://registry.npmjs.org/cli-cursor/-/cli-cursor-1.0.2.tgz"
},
"cli-width": {
"version": "2.1.0",
"from": "cli-width@>=2.0.0 <3.0.0",
"resolved": "https://registry.npmjs.org/cli-width/-/cli-width-2.1.0.tgz"
},
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"cliui": {
"version": "2.1.0",
"from": "cliui@>=2.1.0 <3.0.0",
"resolved": "https://registry.npmjs.org/cliui/-/cliui-2.1.0.tgz"
},
MDL-52127 js: check amd files with eslint grunt task I have spent quite a lot of time working through the current list of eslint options and configuring them for Moodle style and I think this is a very good basis to start us at (as well as taking some of out jshint options out with https://www.npmjs.com/package/polyjuice ). Thanks to Andrew Nicols, Mark Johnson and Frédéric Massart for some refinements. With this configuration the grunt build will fail if errors are present in the js (though you can of course tell jshint to ignore some errors, as I have done in admin/tool/lp/amd/src/competency_rule_points.js and defining the Y global in lib/amd/src/yui.js ). The grunt task will not report warnings by default, but a new --show-lint-warnings flag will help achieve that. Editor integrations/stanadalone eslint tool will surely be a better way of getting eslint errors rather than using the grunt task.
2016-05-11 10:19:30 +01:00
"code-point-at": {
"version": "1.0.0",
"from": "code-point-at@>=1.0.0 <2.0.0",
"resolved": "https://registry.npmjs.org/code-point-at/-/code-point-at-1.0.0.tgz"
},
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"coffee-script": {
"version": "1.3.3",
"from": "coffee-script@>=1.3.3 <1.4.0",
"resolved": "https://registry.npmjs.org/coffee-script/-/coffee-script-1.3.3.tgz"
},
"colors": {
"version": "0.6.2",
"from": "colors@>=0.6.2 <0.7.0",
"resolved": "https://registry.npmjs.org/colors/-/colors-0.6.2.tgz"
},
"combined-stream": {
"version": "1.0.5",
"from": "combined-stream@>=1.0.5 <1.1.0",
"resolved": "https://registry.npmjs.org/combined-stream/-/combined-stream-1.0.5.tgz"
},
"commander": {
"version": "2.9.0",
"from": "commander@>=2.9.0 <3.0.0",
"resolved": "https://registry.npmjs.org/commander/-/commander-2.9.0.tgz"
},
"concat-map": {
"version": "0.0.1",
"from": "concat-map@0.0.1",
"resolved": "https://registry.npmjs.org/concat-map/-/concat-map-0.0.1.tgz"
},
"concat-stream": {
"version": "1.5.1",
"from": "concat-stream@>=1.4.1 <2.0.0",
"resolved": "https://registry.npmjs.org/concat-stream/-/concat-stream-1.5.1.tgz",
"dependencies": {
"readable-stream": {
"version": "2.0.5",
"from": "readable-stream@>=2.0.0 <2.1.0",
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-2.0.5.tgz"
}
}
},
"console-browserify": {
"version": "1.1.0",
"from": "console-browserify@>=1.1.0 <1.2.0",
"resolved": "https://registry.npmjs.org/console-browserify/-/console-browserify-1.1.0.tgz"
},
"core-util-is": {
"version": "1.0.2",
"from": "core-util-is@>=1.0.0 <1.1.0",
"resolved": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.2.tgz"
},
"cpr": {
"version": "0.0.6",
"from": "cpr@>=0.0.6 <0.1.0",
"resolved": "https://registry.npmjs.org/cpr/-/cpr-0.0.6.tgz",
"dependencies": {
"graceful-fs": {
"version": "1.1.14",
"from": "graceful-fs@>=1.1.14 <1.2.0",
"resolved": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-1.1.14.tgz"
MDL-52250 npm: shrinkwrap to lock down dependencies We've tried various approaches to lock down our dependencies and they have been flawed because dependencies in our included packages may not be locked down and previous attempts to do that have not been correct. With npm shrinkwrap we lock down versions so that any npm install will always install the exact same versions for all developers - see: https://docs.npmjs.com/cli/shrinkwrap (This is a lot like composer.lock for those more fluent with composer)
2015-12-03 17:00:50 +00:00
},
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"mkdirp": {
"version": "0.3.5",
"from": "mkdirp@>=0.3.4 <0.4.0",
"resolved": "https://registry.npmjs.org/mkdirp/-/mkdirp-0.3.5.tgz"
MDL-52250 npm: shrinkwrap to lock down dependencies We've tried various approaches to lock down our dependencies and they have been flawed because dependencies in our included packages may not be locked down and previous attempts to do that have not been correct. With npm shrinkwrap we lock down versions so that any npm install will always install the exact same versions for all developers - see: https://docs.npmjs.com/cli/shrinkwrap (This is a lot like composer.lock for those more fluent with composer)
2015-12-03 17:00:50 +00:00
},
"rimraf": {
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"version": "2.0.3",
"from": "rimraf@>=2.0.2 <2.1.0",
"resolved": "https://registry.npmjs.org/rimraf/-/rimraf-2.0.3.tgz"
}
}
},
"cryptiles": {
"version": "2.0.5",
"from": "cryptiles@>=2.0.0 <3.0.0",
"resolved": "https://registry.npmjs.org/cryptiles/-/cryptiles-2.0.5.tgz"
},
"csslint": {
"version": "0.10.0",
"from": "csslint@>=0.10.0 <0.11.0",
"resolved": "https://registry.npmjs.org/csslint/-/csslint-0.10.0.tgz"
},
"cssproc": {
"version": "0.0.7",
"from": "cssproc@>=0.0.1 <0.1.0",
"resolved": "https://registry.npmjs.org/cssproc/-/cssproc-0.0.7.tgz"
},
MDL-52127 js: check amd files with eslint grunt task I have spent quite a lot of time working through the current list of eslint options and configuring them for Moodle style and I think this is a very good basis to start us at (as well as taking some of out jshint options out with https://www.npmjs.com/package/polyjuice ). Thanks to Andrew Nicols, Mark Johnson and Frédéric Massart for some refinements. With this configuration the grunt build will fail if errors are present in the js (though you can of course tell jshint to ignore some errors, as I have done in admin/tool/lp/amd/src/competency_rule_points.js and defining the Y global in lib/amd/src/yui.js ). The grunt task will not report warnings by default, but a new --show-lint-warnings flag will help achieve that. Editor integrations/stanadalone eslint tool will surely be a better way of getting eslint errors rather than using the grunt task.
2016-05-11 10:19:30 +01:00
"d": {
"version": "0.1.1",
"from": "d@>=0.1.1 <0.2.0",
"resolved": "https://registry.npmjs.org/d/-/d-0.1.1.tgz"
},
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"dashdash": {
"version": "1.12.1",
"from": "dashdash@>=1.10.1 <2.0.0",
"resolved": "https://registry.npmjs.org/dashdash/-/dashdash-1.12.1.tgz"
},
"date-now": {
"version": "0.1.4",
"from": "date-now@>=0.1.4 <0.2.0",
"resolved": "https://registry.npmjs.org/date-now/-/date-now-0.1.4.tgz"
},
"dateformat": {
"version": "1.0.2-1.2.3",
"from": "dateformat@1.0.2-1.2.3",
"resolved": "https://registry.npmjs.org/dateformat/-/dateformat-1.0.2-1.2.3.tgz"
},
"debug": {
"version": "0.7.4",
"from": "debug@>=0.7.0 <0.8.0",
"resolved": "https://registry.npmjs.org/debug/-/debug-0.7.4.tgz"
},
"decamelize": {
"version": "1.1.2",
"from": "decamelize@>=1.1.2 <2.0.0",
"resolved": "https://registry.npmjs.org/decamelize/-/decamelize-1.1.2.tgz"
},
MDL-52127 js: check amd files with eslint grunt task I have spent quite a lot of time working through the current list of eslint options and configuring them for Moodle style and I think this is a very good basis to start us at (as well as taking some of out jshint options out with https://www.npmjs.com/package/polyjuice ). Thanks to Andrew Nicols, Mark Johnson and Frédéric Massart for some refinements. With this configuration the grunt build will fail if errors are present in the js (though you can of course tell jshint to ignore some errors, as I have done in admin/tool/lp/amd/src/competency_rule_points.js and defining the Y global in lib/amd/src/yui.js ). The grunt task will not report warnings by default, but a new --show-lint-warnings flag will help achieve that. Editor integrations/stanadalone eslint tool will surely be a better way of getting eslint errors rather than using the grunt task.
2016-05-11 10:19:30 +01:00
"deep-is": {
"version": "0.1.3",
"from": "deep-is@>=0.1.3 <0.2.0",
"resolved": "https://registry.npmjs.org/deep-is/-/deep-is-0.1.3.tgz"
},
"del": {
"version": "2.2.0",
"from": "del@>=2.0.2 <3.0.0",
"resolved": "https://registry.npmjs.org/del/-/del-2.2.0.tgz"
},
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"delayed-stream": {
"version": "1.0.0",
"from": "delayed-stream@>=1.0.0 <1.1.0",
"resolved": "https://registry.npmjs.org/delayed-stream/-/delayed-stream-1.0.0.tgz"
},
MDL-52127 js: check amd files with eslint grunt task I have spent quite a lot of time working through the current list of eslint options and configuring them for Moodle style and I think this is a very good basis to start us at (as well as taking some of out jshint options out with https://www.npmjs.com/package/polyjuice ). Thanks to Andrew Nicols, Mark Johnson and Frédéric Massart for some refinements. With this configuration the grunt build will fail if errors are present in the js (though you can of course tell jshint to ignore some errors, as I have done in admin/tool/lp/amd/src/competency_rule_points.js and defining the Y global in lib/amd/src/yui.js ). The grunt task will not report warnings by default, but a new --show-lint-warnings flag will help achieve that. Editor integrations/stanadalone eslint tool will surely be a better way of getting eslint errors rather than using the grunt task.
2016-05-11 10:19:30 +01:00
"doctrine": {
"version": "1.2.2",
"from": "doctrine@>=1.2.2 <2.0.0",
"resolved": "https://registry.npmjs.org/doctrine/-/doctrine-1.2.2.tgz",
"dependencies": {
"esutils": {
"version": "1.1.6",
"from": "esutils@>=1.1.6 <2.0.0",
"resolved": "https://registry.npmjs.org/esutils/-/esutils-1.1.6.tgz"
},
"isarray": {
"version": "1.0.0",
"from": "isarray@>=1.0.0 <2.0.0",
"resolved": "https://registry.npmjs.org/isarray/-/isarray-1.0.0.tgz"
}
}
},
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"dom-serializer": {
"version": "0.1.0",
"from": "dom-serializer@>=0.0.0 <1.0.0",
"resolved": "https://registry.npmjs.org/dom-serializer/-/dom-serializer-0.1.0.tgz",
"dependencies": {
"domelementtype": {
"version": "1.1.3",
"from": "domelementtype@>=1.1.1 <1.2.0",
"resolved": "https://registry.npmjs.org/domelementtype/-/domelementtype-1.1.3.tgz"
},
"entities": {
"version": "1.1.1",
"from": "entities@>=1.1.1 <1.2.0",
"resolved": "https://registry.npmjs.org/entities/-/entities-1.1.1.tgz"
}
}
},
"domelementtype": {
"version": "1.3.0",
"from": "domelementtype@>=1.0.0 <2.0.0",
"resolved": "https://registry.npmjs.org/domelementtype/-/domelementtype-1.3.0.tgz"
},
"domhandler": {
"version": "2.3.0",
"from": "domhandler@>=2.3.0 <2.4.0",
"resolved": "https://registry.npmjs.org/domhandler/-/domhandler-2.3.0.tgz"
},
"domutils": {
"version": "1.5.1",
"from": "domutils@>=1.5.0 <1.6.0",
"resolved": "https://registry.npmjs.org/domutils/-/domutils-1.5.1.tgz"
},
"ecc-jsbn": {
"version": "0.1.1",
"from": "ecc-jsbn@>=0.0.1 <1.0.0",
"resolved": "https://registry.npmjs.org/ecc-jsbn/-/ecc-jsbn-0.1.1.tgz"
},
"entities": {
"version": "1.0.0",
"from": "entities@>=1.0.0 <1.1.0",
"resolved": "https://registry.npmjs.org/entities/-/entities-1.0.0.tgz"
},
"errno": {
"version": "0.1.4",
"from": "errno@>=0.1.1 <0.2.0",
"resolved": "https://registry.npmjs.org/errno/-/errno-0.1.4.tgz"
},
"error-ex": {
"version": "1.3.0",
"from": "error-ex@>=1.2.0 <2.0.0",
"resolved": "https://registry.npmjs.org/error-ex/-/error-ex-1.3.0.tgz"
},
MDL-52127 js: check amd files with eslint grunt task I have spent quite a lot of time working through the current list of eslint options and configuring them for Moodle style and I think this is a very good basis to start us at (as well as taking some of out jshint options out with https://www.npmjs.com/package/polyjuice ). Thanks to Andrew Nicols, Mark Johnson and Frédéric Massart for some refinements. With this configuration the grunt build will fail if errors are present in the js (though you can of course tell jshint to ignore some errors, as I have done in admin/tool/lp/amd/src/competency_rule_points.js and defining the Y global in lib/amd/src/yui.js ). The grunt task will not report warnings by default, but a new --show-lint-warnings flag will help achieve that. Editor integrations/stanadalone eslint tool will surely be a better way of getting eslint errors rather than using the grunt task.
2016-05-11 10:19:30 +01:00
"es5-ext": {
"version": "0.10.11",
"from": "es5-ext@>=0.10.8 <0.11.0",
"resolved": "https://registry.npmjs.org/es5-ext/-/es5-ext-0.10.11.tgz"
},
"es6-iterator": {
"version": "2.0.0",
"from": "es6-iterator@>=2.0.0 <3.0.0",
"resolved": "https://registry.npmjs.org/es6-iterator/-/es6-iterator-2.0.0.tgz"
},
"es6-map": {
"version": "0.1.4",
"from": "es6-map@>=0.1.3 <0.2.0",
"resolved": "https://registry.npmjs.org/es6-map/-/es6-map-0.1.4.tgz",
"dependencies": {
"es6-symbol": {
"version": "3.1.0",
"from": "es6-symbol@>=3.1.0 <3.2.0",
"resolved": "https://registry.npmjs.org/es6-symbol/-/es6-symbol-3.1.0.tgz"
}
}
},
"es6-set": {
"version": "0.1.4",
"from": "es6-set@>=0.1.3 <0.2.0",
"resolved": "https://registry.npmjs.org/es6-set/-/es6-set-0.1.4.tgz"
},
"es6-symbol": {
"version": "3.0.2",
"from": "es6-symbol@>=3.0.1 <3.1.0",
"resolved": "https://registry.npmjs.org/es6-symbol/-/es6-symbol-3.0.2.tgz"
},
"es6-weak-map": {
"version": "2.0.1",
"from": "es6-weak-map@>=2.0.1 <3.0.0",
"resolved": "https://registry.npmjs.org/es6-weak-map/-/es6-weak-map-2.0.1.tgz"
},
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"escape-string-regexp": {
"version": "1.0.4",
"from": "escape-string-regexp@>=1.0.2 <2.0.0",
"resolved": "https://registry.npmjs.org/escape-string-regexp/-/escape-string-regexp-1.0.4.tgz"
},
"escodegen": {
"version": "0.0.28",
"from": "escodegen@>=0.0.0 <0.1.0",
"resolved": "https://registry.npmjs.org/escodegen/-/escodegen-0.0.28.tgz"
},
MDL-52127 js: check amd files with eslint grunt task I have spent quite a lot of time working through the current list of eslint options and configuring them for Moodle style and I think this is a very good basis to start us at (as well as taking some of out jshint options out with https://www.npmjs.com/package/polyjuice ). Thanks to Andrew Nicols, Mark Johnson and Frédéric Massart for some refinements. With this configuration the grunt build will fail if errors are present in the js (though you can of course tell jshint to ignore some errors, as I have done in admin/tool/lp/amd/src/competency_rule_points.js and defining the Y global in lib/amd/src/yui.js ). The grunt task will not report warnings by default, but a new --show-lint-warnings flag will help achieve that. Editor integrations/stanadalone eslint tool will surely be a better way of getting eslint errors rather than using the grunt task.
2016-05-11 10:19:30 +01:00
"escope": {
"version": "3.6.0",
"from": "escope@>=3.6.0 <4.0.0",
"resolved": "https://registry.npmjs.org/escope/-/escope-3.6.0.tgz",
"dependencies": {
"estraverse": {
"version": "4.2.0",
"from": "estraverse@4.2.0",
"resolved": "https://registry.npmjs.org/estraverse/-/estraverse-4.2.0.tgz"
}
}
},
"eslint": {
"version": "2.12.0",
"from": "eslint@>=2.0.0 <3.0.0",
"resolved": "https://registry.npmjs.org/eslint/-/eslint-2.12.0.tgz",
"dependencies": {
"ansi-styles": {
"version": "2.2.1",
"from": "ansi-styles@>=2.2.1 <3.0.0",
"resolved": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-2.2.1.tgz"
},
"argparse": {
"version": "1.0.7",
"from": "argparse@>=1.0.7 <2.0.0",
"resolved": "https://registry.npmjs.org/argparse/-/argparse-1.0.7.tgz"
},
"chalk": {
"version": "1.1.3",
"from": "chalk@>=1.1.3 <2.0.0",
"resolved": "https://registry.npmjs.org/chalk/-/chalk-1.1.3.tgz"
},
"debug": {
"version": "2.2.0",
"from": "debug@>=2.1.1 <3.0.0",
"resolved": "https://registry.npmjs.org/debug/-/debug-2.2.0.tgz"
},
"esprima": {
"version": "2.7.2",
"from": "esprima@>=2.6.0 <3.0.0",
"resolved": "https://registry.npmjs.org/esprima/-/esprima-2.7.2.tgz"
},
"estraverse": {
"version": "4.2.0",
"from": "estraverse@>=4.2.0 <5.0.0",
"resolved": "https://registry.npmjs.org/estraverse/-/estraverse-4.2.0.tgz"
},
"glob": {
"version": "7.0.3",
"from": "glob@>=7.0.3 <8.0.0",
"resolved": "https://registry.npmjs.org/glob/-/glob-7.0.3.tgz"
},
"js-yaml": {
"version": "3.6.1",
"from": "js-yaml@>=3.5.1 <4.0.0",
"resolved": "https://registry.npmjs.org/js-yaml/-/js-yaml-3.6.1.tgz"
},
"lodash": {
"version": "4.13.1",
"from": "lodash@>=4.0.0 <5.0.0",
"resolved": "https://registry.npmjs.org/lodash/-/lodash-4.13.1.tgz"
},
"minimatch": {
"version": "3.0.0",
"from": "minimatch@3.0.0",
"resolved": "https://registry.npmjs.org/minimatch/-/minimatch-3.0.0.tgz"
},
"progress": {
"version": "1.1.8",
"from": "progress@>=1.1.8 <2.0.0",
"resolved": "https://registry.npmjs.org/progress/-/progress-1.1.8.tgz"
},
"shelljs": {
"version": "0.6.0",
"from": "shelljs@>=0.6.0 <0.7.0",
"resolved": "https://registry.npmjs.org/shelljs/-/shelljs-0.6.0.tgz"
}
}
},
"espree": {
"version": "3.1.4",
"from": "espree@3.1.4",
"resolved": "https://registry.npmjs.org/espree/-/espree-3.1.4.tgz"
},
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"esprima": {
"version": "1.0.4",
"from": "esprima@>=1.0.2 <1.1.0",
"resolved": "https://registry.npmjs.org/esprima/-/esprima-1.0.4.tgz"
},
MDL-52127 js: check amd files with eslint grunt task I have spent quite a lot of time working through the current list of eslint options and configuring them for Moodle style and I think this is a very good basis to start us at (as well as taking some of out jshint options out with https://www.npmjs.com/package/polyjuice ). Thanks to Andrew Nicols, Mark Johnson and Frédéric Massart for some refinements. With this configuration the grunt build will fail if errors are present in the js (though you can of course tell jshint to ignore some errors, as I have done in admin/tool/lp/amd/src/competency_rule_points.js and defining the Y global in lib/amd/src/yui.js ). The grunt task will not report warnings by default, but a new --show-lint-warnings flag will help achieve that. Editor integrations/stanadalone eslint tool will surely be a better way of getting eslint errors rather than using the grunt task.
2016-05-11 10:19:30 +01:00
"esrecurse": {
"version": "4.1.0",
"from": "esrecurse@>=4.1.0 <5.0.0",
"resolved": "https://registry.npmjs.org/esrecurse/-/esrecurse-4.1.0.tgz",
"dependencies": {
"estraverse": {
"version": "4.1.1",
"from": "estraverse@>=4.1.0 <4.2.0",
"resolved": "https://registry.npmjs.org/estraverse/-/estraverse-4.1.1.tgz"
}
}
},
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"estraverse": {
"version": "1.3.2",
"from": "estraverse@>=1.3.0 <1.4.0",
"resolved": "https://registry.npmjs.org/estraverse/-/estraverse-1.3.2.tgz"
},
MDL-52127 js: check amd files with eslint grunt task I have spent quite a lot of time working through the current list of eslint options and configuring them for Moodle style and I think this is a very good basis to start us at (as well as taking some of out jshint options out with https://www.npmjs.com/package/polyjuice ). Thanks to Andrew Nicols, Mark Johnson and Frédéric Massart for some refinements. With this configuration the grunt build will fail if errors are present in the js (though you can of course tell jshint to ignore some errors, as I have done in admin/tool/lp/amd/src/competency_rule_points.js and defining the Y global in lib/amd/src/yui.js ). The grunt task will not report warnings by default, but a new --show-lint-warnings flag will help achieve that. Editor integrations/stanadalone eslint tool will surely be a better way of getting eslint errors rather than using the grunt task.
2016-05-11 10:19:30 +01:00
"esutils": {
"version": "2.0.2",
"from": "esutils@>=2.0.2 <3.0.0",
"resolved": "https://registry.npmjs.org/esutils/-/esutils-2.0.2.tgz"
},
"event-emitter": {
"version": "0.3.4",
"from": "event-emitter@>=0.3.4 <0.4.0",
"resolved": "https://registry.npmjs.org/event-emitter/-/event-emitter-0.3.4.tgz"
},
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"eventemitter2": {
"version": "0.4.14",
"from": "eventemitter2@>=0.4.13 <0.5.0",
"resolved": "https://registry.npmjs.org/eventemitter2/-/eventemitter2-0.4.14.tgz"
},
"exit": {
"version": "0.1.2",
"from": "exit@>=0.1.1 <0.2.0",
"resolved": "https://registry.npmjs.org/exit/-/exit-0.1.2.tgz"
},
MDL-52127 js: check amd files with eslint grunt task I have spent quite a lot of time working through the current list of eslint options and configuring them for Moodle style and I think this is a very good basis to start us at (as well as taking some of out jshint options out with https://www.npmjs.com/package/polyjuice ). Thanks to Andrew Nicols, Mark Johnson and Frédéric Massart for some refinements. With this configuration the grunt build will fail if errors are present in the js (though you can of course tell jshint to ignore some errors, as I have done in admin/tool/lp/amd/src/competency_rule_points.js and defining the Y global in lib/amd/src/yui.js ). The grunt task will not report warnings by default, but a new --show-lint-warnings flag will help achieve that. Editor integrations/stanadalone eslint tool will surely be a better way of getting eslint errors rather than using the grunt task.
2016-05-11 10:19:30 +01:00
"exit-hook": {
"version": "1.1.1",
"from": "exit-hook@>=1.0.0 <2.0.0",
"resolved": "https://registry.npmjs.org/exit-hook/-/exit-hook-1.1.1.tgz"
},
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"extend": {
"version": "3.0.0",
"from": "extend@>=3.0.0 <3.1.0",
"resolved": "https://registry.npmjs.org/extend/-/extend-3.0.0.tgz"
},
"extsprintf": {
"version": "1.0.2",
"from": "extsprintf@1.0.2",
"resolved": "https://registry.npmjs.org/extsprintf/-/extsprintf-1.0.2.tgz"
},
MDL-52127 js: check amd files with eslint grunt task I have spent quite a lot of time working through the current list of eslint options and configuring them for Moodle style and I think this is a very good basis to start us at (as well as taking some of out jshint options out with https://www.npmjs.com/package/polyjuice ). Thanks to Andrew Nicols, Mark Johnson and Frédéric Massart for some refinements. With this configuration the grunt build will fail if errors are present in the js (though you can of course tell jshint to ignore some errors, as I have done in admin/tool/lp/amd/src/competency_rule_points.js and defining the Y global in lib/amd/src/yui.js ). The grunt task will not report warnings by default, but a new --show-lint-warnings flag will help achieve that. Editor integrations/stanadalone eslint tool will surely be a better way of getting eslint errors rather than using the grunt task.
2016-05-11 10:19:30 +01:00
"fast-levenshtein": {
"version": "1.1.3",
"from": "fast-levenshtein@>=1.1.0 <2.0.0",
"resolved": "https://registry.npmjs.org/fast-levenshtein/-/fast-levenshtein-1.1.3.tgz"
},
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"faye-websocket": {
"version": "0.4.4",
"from": "faye-websocket@>=0.4.3 <0.5.0",
"resolved": "https://registry.npmjs.org/faye-websocket/-/faye-websocket-0.4.4.tgz"
},
"figures": {
"version": "1.4.0",
"from": "figures@>=1.0.1 <2.0.0",
"resolved": "https://registry.npmjs.org/figures/-/figures-1.4.0.tgz"
},
MDL-52127 js: check amd files with eslint grunt task I have spent quite a lot of time working through the current list of eslint options and configuring them for Moodle style and I think this is a very good basis to start us at (as well as taking some of out jshint options out with https://www.npmjs.com/package/polyjuice ). Thanks to Andrew Nicols, Mark Johnson and Frédéric Massart for some refinements. With this configuration the grunt build will fail if errors are present in the js (though you can of course tell jshint to ignore some errors, as I have done in admin/tool/lp/amd/src/competency_rule_points.js and defining the Y global in lib/amd/src/yui.js ). The grunt task will not report warnings by default, but a new --show-lint-warnings flag will help achieve that. Editor integrations/stanadalone eslint tool will surely be a better way of getting eslint errors rather than using the grunt task.
2016-05-11 10:19:30 +01:00
"file-entry-cache": {
"version": "1.2.4",
"from": "file-entry-cache@>=1.1.1 <2.0.0",
"resolved": "https://registry.npmjs.org/file-entry-cache/-/file-entry-cache-1.2.4.tgz"
},
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"fileset": {
"version": "0.1.8",
"from": "fileset@>=0.1.0 <0.2.0",
"resolved": "https://registry.npmjs.org/fileset/-/fileset-0.1.8.tgz"
},
"find-up": {
"version": "1.1.0",
"from": "find-up@>=1.0.0 <2.0.0",
"resolved": "https://registry.npmjs.org/find-up/-/find-up-1.1.0.tgz"
},
"findup-sync": {
"version": "0.1.3",
"from": "findup-sync@>=0.1.2 <0.2.0",
"resolved": "https://registry.npmjs.org/findup-sync/-/findup-sync-0.1.3.tgz",
"dependencies": {
"glob": {
"version": "3.2.11",
"from": "glob@>=3.2.9 <3.3.0",
"resolved": "https://registry.npmjs.org/glob/-/glob-3.2.11.tgz"
MDL-52250 npm: shrinkwrap to lock down dependencies We've tried various approaches to lock down our dependencies and they have been flawed because dependencies in our included packages may not be locked down and previous attempts to do that have not been correct. With npm shrinkwrap we lock down versions so that any npm install will always install the exact same versions for all developers - see: https://docs.npmjs.com/cli/shrinkwrap (This is a lot like composer.lock for those more fluent with composer)
2015-12-03 17:00:50 +00:00
},
"lodash": {
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"version": "2.4.2",
"from": "lodash@>=2.4.1 <2.5.0",
"resolved": "https://registry.npmjs.org/lodash/-/lodash-2.4.2.tgz"
MDL-52250 npm: shrinkwrap to lock down dependencies We've tried various approaches to lock down our dependencies and they have been flawed because dependencies in our included packages may not be locked down and previous attempts to do that have not been correct. With npm shrinkwrap we lock down versions so that any npm install will always install the exact same versions for all developers - see: https://docs.npmjs.com/cli/shrinkwrap (This is a lot like composer.lock for those more fluent with composer)
2015-12-03 17:00:50 +00:00
},
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"minimatch": {
"version": "0.3.0",
"from": "minimatch@>=0.3.0 <0.4.0",
"resolved": "https://registry.npmjs.org/minimatch/-/minimatch-0.3.0.tgz"
}
}
},
MDL-52127 js: check amd files with eslint grunt task I have spent quite a lot of time working through the current list of eslint options and configuring them for Moodle style and I think this is a very good basis to start us at (as well as taking some of out jshint options out with https://www.npmjs.com/package/polyjuice ). Thanks to Andrew Nicols, Mark Johnson and Frédéric Massart for some refinements. With this configuration the grunt build will fail if errors are present in the js (though you can of course tell jshint to ignore some errors, as I have done in admin/tool/lp/amd/src/competency_rule_points.js and defining the Y global in lib/amd/src/yui.js ). The grunt task will not report warnings by default, but a new --show-lint-warnings flag will help achieve that. Editor integrations/stanadalone eslint tool will surely be a better way of getting eslint errors rather than using the grunt task.
2016-05-11 10:19:30 +01:00
"flat-cache": {
"version": "1.0.10",
"from": "flat-cache@>=1.0.9 <2.0.0",
"resolved": "https://registry.npmjs.org/flat-cache/-/flat-cache-1.0.10.tgz",
"dependencies": {
"graceful-fs": {
"version": "4.1.4",
"from": "graceful-fs@>=4.1.2 <5.0.0",
"resolved": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.4.tgz"
}
}
},
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"forever-agent": {
"version": "0.6.1",
"from": "forever-agent@>=0.6.1 <0.7.0",
"resolved": "https://registry.npmjs.org/forever-agent/-/forever-agent-0.6.1.tgz"
},
"form-data": {
"version": "1.0.0-rc3",
"from": "form-data@>=1.0.0-rc3 <1.1.0",
"resolved": "https://registry.npmjs.org/form-data/-/form-data-1.0.0-rc3.tgz",
"dependencies": {
"async": {
"version": "1.5.2",
"from": "async@>=1.4.0 <2.0.0",
"resolved": "https://registry.npmjs.org/async/-/async-1.5.2.tgz"
}
}
},
"gaze": {
"version": "0.5.2",
"from": "gaze@>=0.5.1 <0.6.0",
"resolved": "https://registry.npmjs.org/gaze/-/gaze-0.5.2.tgz"
},
"gear": {
"version": "0.8.18",
"from": "gear@>=0.8.0 <0.9.0",
"resolved": "https://registry.npmjs.org/gear/-/gear-0.8.18.tgz",
"dependencies": {
"async": {
"version": "0.2.10",
"from": "async@>=0.2.0 <0.3.0",
"resolved": "https://registry.npmjs.org/async/-/async-0.2.10.tgz"
},
"mkdirp": {
"version": "0.3.5",
"from": "mkdirp@>=0.3.0 <0.4.0",
"resolved": "https://registry.npmjs.org/mkdirp/-/mkdirp-0.3.5.tgz"
}
}
},
"gear-lib": {
"version": "0.8.15",
"from": "gear-lib@>=0.8.0 <0.9.0",
"resolved": "https://registry.npmjs.org/gear-lib/-/gear-lib-0.8.15.tgz",
"dependencies": {
"async": {
"version": "0.2.10",
"from": "async@>=0.2.0 <0.3.0",
"resolved": "https://registry.npmjs.org/async/-/async-0.2.10.tgz"
MDL-52250 npm: shrinkwrap to lock down dependencies We've tried various approaches to lock down our dependencies and they have been flawed because dependencies in our included packages may not be locked down and previous attempts to do that have not been correct. With npm shrinkwrap we lock down versions so that any npm install will always install the exact same versions for all developers - see: https://docs.npmjs.com/cli/shrinkwrap (This is a lot like composer.lock for those more fluent with composer)
2015-12-03 17:00:50 +00:00
},
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"glob": {
"version": "3.2.11",
"from": "glob@>=3.2.0 <3.3.0",
"resolved": "https://registry.npmjs.org/glob/-/glob-3.2.11.tgz"
MDL-52250 npm: shrinkwrap to lock down dependencies We've tried various approaches to lock down our dependencies and they have been flawed because dependencies in our included packages may not be locked down and previous attempts to do that have not been correct. With npm shrinkwrap we lock down versions so that any npm install will always install the exact same versions for all developers - see: https://docs.npmjs.com/cli/shrinkwrap (This is a lot like composer.lock for those more fluent with composer)
2015-12-03 17:00:50 +00:00
},
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"jshint": {
"version": "2.5.11",
"from": "jshint@>=2.5.0 <2.6.0",
"resolved": "https://registry.npmjs.org/jshint/-/jshint-2.5.11.tgz",
MDL-52250 npm: shrinkwrap to lock down dependencies We've tried various approaches to lock down our dependencies and they have been flawed because dependencies in our included packages may not be locked down and previous attempts to do that have not been correct. With npm shrinkwrap we lock down versions so that any npm install will always install the exact same versions for all developers - see: https://docs.npmjs.com/cli/shrinkwrap (This is a lot like composer.lock for those more fluent with composer)
2015-12-03 17:00:50 +00:00
"dependencies": {
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"minimatch": {
"version": "1.0.0",
"from": "minimatch@>=1.0.0 <1.1.0",
"resolved": "https://registry.npmjs.org/minimatch/-/minimatch-1.0.0.tgz"
MDL-52250 npm: shrinkwrap to lock down dependencies We've tried various approaches to lock down our dependencies and they have been flawed because dependencies in our included packages may not be locked down and previous attempts to do that have not been correct. With npm shrinkwrap we lock down versions so that any npm install will always install the exact same versions for all developers - see: https://docs.npmjs.com/cli/shrinkwrap (This is a lot like composer.lock for those more fluent with composer)
2015-12-03 17:00:50 +00:00
}
}
},
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"less": {
"version": "1.3.3",
"from": "less@>=1.3.0 <1.4.0",
"resolved": "https://registry.npmjs.org/less/-/less-1.3.3.tgz"
MDL-52250 npm: shrinkwrap to lock down dependencies We've tried various approaches to lock down our dependencies and they have been flawed because dependencies in our included packages may not be locked down and previous attempts to do that have not been correct. With npm shrinkwrap we lock down versions so that any npm install will always install the exact same versions for all developers - see: https://docs.npmjs.com/cli/shrinkwrap (This is a lot like composer.lock for those more fluent with composer)
2015-12-03 17:00:50 +00:00
},
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"mime": {
"version": "1.2.11",
"from": "mime@>=1.2.0 <1.3.0",
"resolved": "https://registry.npmjs.org/mime/-/mime-1.2.11.tgz"
MDL-52250 npm: shrinkwrap to lock down dependencies We've tried various approaches to lock down our dependencies and they have been flawed because dependencies in our included packages may not be locked down and previous attempts to do that have not been correct. With npm shrinkwrap we lock down versions so that any npm install will always install the exact same versions for all developers - see: https://docs.npmjs.com/cli/shrinkwrap (This is a lot like composer.lock for those more fluent with composer)
2015-12-03 17:00:50 +00:00
},
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"minimatch": {
"version": "0.3.0",
"from": "minimatch@>=0.3.0 <0.4.0",
"resolved": "https://registry.npmjs.org/minimatch/-/minimatch-0.3.0.tgz"
MDL-52250 npm: shrinkwrap to lock down dependencies We've tried various approaches to lock down our dependencies and they have been flawed because dependencies in our included packages may not be locked down and previous attempts to do that have not been correct. With npm shrinkwrap we lock down versions so that any npm install will always install the exact same versions for all developers - see: https://docs.npmjs.com/cli/shrinkwrap (This is a lot like composer.lock for those more fluent with composer)
2015-12-03 17:00:50 +00:00
},
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"uglify-js": {
"version": "1.3.5",
"from": "uglify-js@>=1.3.0 <1.4.0",
"resolved": "https://registry.npmjs.org/uglify-js/-/uglify-js-1.3.5.tgz"
},
"underscore": {
"version": "1.6.0",
"from": "underscore@>=1.6.0 <1.7.0",
"resolved": "https://registry.npmjs.org/underscore/-/underscore-1.6.0.tgz"
MDL-52250 npm: shrinkwrap to lock down dependencies We've tried various approaches to lock down our dependencies and they have been flawed because dependencies in our included packages may not be locked down and previous attempts to do that have not been correct. With npm shrinkwrap we lock down versions so that any npm install will always install the exact same versions for all developers - see: https://docs.npmjs.com/cli/shrinkwrap (This is a lot like composer.lock for those more fluent with composer)
2015-12-03 17:00:50 +00:00
}
}
},
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"generate-function": {
"version": "2.0.0",
"from": "generate-function@>=2.0.0 <3.0.0",
"resolved": "https://registry.npmjs.org/generate-function/-/generate-function-2.0.0.tgz"
},
"generate-object-property": {
"version": "1.2.0",
"from": "generate-object-property@>=1.1.0 <2.0.0",
"resolved": "https://registry.npmjs.org/generate-object-property/-/generate-object-property-1.2.0.tgz"
},
"get-stdin": {
"version": "4.0.1",
"from": "get-stdin@>=4.0.1 <5.0.0",
"resolved": "https://registry.npmjs.org/get-stdin/-/get-stdin-4.0.1.tgz"
},
"getobject": {
"version": "0.1.0",
"from": "getobject@>=0.1.0 <0.2.0",
"resolved": "https://registry.npmjs.org/getobject/-/getobject-0.1.0.tgz"
},
"glob": {
"version": "3.1.21",
"from": "glob@>=3.1.21 <3.2.0",
"resolved": "https://registry.npmjs.org/glob/-/glob-3.1.21.tgz",
MDL-52250 npm: shrinkwrap to lock down dependencies We've tried various approaches to lock down our dependencies and they have been flawed because dependencies in our included packages may not be locked down and previous attempts to do that have not been correct. With npm shrinkwrap we lock down versions so that any npm install will always install the exact same versions for all developers - see: https://docs.npmjs.com/cli/shrinkwrap (This is a lot like composer.lock for those more fluent with composer)
2015-12-03 17:00:50 +00:00
"dependencies": {
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"inherits": {
"version": "1.0.2",
"from": "inherits@>=1.0.0 <2.0.0",
"resolved": "https://registry.npmjs.org/inherits/-/inherits-1.0.2.tgz"
}
}
},
MDL-52127 js: check amd files with eslint grunt task I have spent quite a lot of time working through the current list of eslint options and configuring them for Moodle style and I think this is a very good basis to start us at (as well as taking some of out jshint options out with https://www.npmjs.com/package/polyjuice ). Thanks to Andrew Nicols, Mark Johnson and Frédéric Massart for some refinements. With this configuration the grunt build will fail if errors are present in the js (though you can of course tell jshint to ignore some errors, as I have done in admin/tool/lp/amd/src/competency_rule_points.js and defining the Y global in lib/amd/src/yui.js ). The grunt task will not report warnings by default, but a new --show-lint-warnings flag will help achieve that. Editor integrations/stanadalone eslint tool will surely be a better way of getting eslint errors rather than using the grunt task.
2016-05-11 10:19:30 +01:00
"globals": {
"version": "9.8.0",
"from": "globals@>=9.2.0 <10.0.0",
"resolved": "https://registry.npmjs.org/globals/-/globals-9.8.0.tgz"
},
"globby": {
"version": "4.1.0",
"from": "globby@>=4.0.0 <5.0.0",
"resolved": "https://registry.npmjs.org/globby/-/globby-4.1.0.tgz",
"dependencies": {
"glob": {
"version": "6.0.4",
"from": "glob@>=6.0.1 <7.0.0",
"resolved": "https://registry.npmjs.org/glob/-/glob-6.0.4.tgz"
},
"minimatch": {
"version": "3.0.0",
"from": "minimatch@>=2.0.0 <3.0.0||>=3.0.0 <4.0.0",
"resolved": "https://registry.npmjs.org/minimatch/-/minimatch-3.0.0.tgz"
}
}
},
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"globule": {
"version": "0.1.0",
"from": "globule@>=0.1.0 <0.2.0",
"resolved": "https://registry.npmjs.org/globule/-/globule-0.1.0.tgz",
"dependencies": {
"lodash": {
"version": "1.0.2",
"from": "lodash@>=1.0.1 <1.1.0",
"resolved": "https://registry.npmjs.org/lodash/-/lodash-1.0.2.tgz"
MDL-52250 npm: shrinkwrap to lock down dependencies We've tried various approaches to lock down our dependencies and they have been flawed because dependencies in our included packages may not be locked down and previous attempts to do that have not been correct. With npm shrinkwrap we lock down versions so that any npm install will always install the exact same versions for all developers - see: https://docs.npmjs.com/cli/shrinkwrap (This is a lot like composer.lock for those more fluent with composer)
2015-12-03 17:00:50 +00:00
}
}
},
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"graceful-fs": {
"version": "1.2.3",
"from": "graceful-fs@>=1.2.0 <1.3.0",
"resolved": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-1.2.3.tgz"
},
"graceful-readlink": {
"version": "1.0.1",
"from": "graceful-readlink@>=1.0.0",
"resolved": "https://registry.npmjs.org/graceful-readlink/-/graceful-readlink-1.0.1.tgz"
},
"grunt": {
"version": "0.4.5",
"from": "grunt@0.4.5",
MDL-49817 grunt: handle multiple watched files changed at once Includes multiple changes to the shifter task to simplify and support this: * Use grunt.file for shifter yui 'module' detection rather than our own 70 line function * Use grunt.util.spawn rather than our own exec for shifter * Improve behaviour on various yui subdirectories We have to add the 'async' depndency to npm because we are running multiple async operations in the single task. We use async.eachSeries to run each shifter job sequentally (else the output would be unreadable when running async). We also run shifter in non-recursive mode on the module directory so its not building everything (thanks to Ryan for pointing this out!)
2016-01-21 14:21:13 +00:00
"resolved": "https://registry.npmjs.org/grunt/-/grunt-0.4.5.tgz",
"dependencies": {
"async": {
"version": "0.1.22",
"from": "async@>=0.1.22 <0.2.0",
"resolved": "https://registry.npmjs.org/async/-/async-0.1.22.tgz"
}
}
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
},
MDL-52250 npm: shrinkwrap to lock down dependencies We've tried various approaches to lock down our dependencies and they have been flawed because dependencies in our included packages may not be locked down and previous attempts to do that have not been correct. With npm shrinkwrap we lock down versions so that any npm install will always install the exact same versions for all developers - see: https://docs.npmjs.com/cli/shrinkwrap (This is a lot like composer.lock for those more fluent with composer)
2015-12-03 17:00:50 +00:00
"grunt-contrib-less": {
"version": "1.1.0",
"from": "grunt-contrib-less@1.1.0",
"resolved": "https://registry.npmjs.org/grunt-contrib-less/-/grunt-contrib-less-1.1.0.tgz",
"dependencies": {
"async": {
"version": "0.9.2",
"from": "async@>=0.9.0 <0.10.0",
"resolved": "https://registry.npmjs.org/async/-/async-0.9.2.tgz"
},
"lodash": {
"version": "3.10.1",
"from": "lodash@>=3.2.0 <4.0.0",
"resolved": "https://registry.npmjs.org/lodash/-/lodash-3.10.1.tgz"
}
}
},
"grunt-contrib-uglify": {
"version": "0.11.0",
"from": "grunt-contrib-uglify@0.11.0",
"resolved": "https://registry.npmjs.org/grunt-contrib-uglify/-/grunt-contrib-uglify-0.11.0.tgz",
"dependencies": {
"lodash": {
"version": "3.10.1",
"from": "lodash@>=3.2.0 <4.0.0",
"resolved": "https://registry.npmjs.org/lodash/-/lodash-3.10.1.tgz"
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
}
}
},
"grunt-contrib-watch": {
"version": "0.6.1",
"from": "grunt-contrib-watch@>=0.6.1 <0.7.0",
"resolved": "https://registry.npmjs.org/grunt-contrib-watch/-/grunt-contrib-watch-0.6.1.tgz",
"dependencies": {
"async": {
"version": "0.2.10",
"from": "async@>=0.2.9 <0.3.0",
"resolved": "https://registry.npmjs.org/async/-/async-0.2.10.tgz"
MDL-52250 npm: shrinkwrap to lock down dependencies We've tried various approaches to lock down our dependencies and they have been flawed because dependencies in our included packages may not be locked down and previous attempts to do that have not been correct. With npm shrinkwrap we lock down versions so that any npm install will always install the exact same versions for all developers - see: https://docs.npmjs.com/cli/shrinkwrap (This is a lot like composer.lock for those more fluent with composer)
2015-12-03 17:00:50 +00:00
},
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"lodash": {
"version": "2.4.2",
"from": "lodash@>=2.4.1 <2.5.0",
"resolved": "https://registry.npmjs.org/lodash/-/lodash-2.4.2.tgz"
}
}
},
MDL-52127 js: check amd files with eslint grunt task I have spent quite a lot of time working through the current list of eslint options and configuring them for Moodle style and I think this is a very good basis to start us at (as well as taking some of out jshint options out with https://www.npmjs.com/package/polyjuice ). Thanks to Andrew Nicols, Mark Johnson and Frédéric Massart for some refinements. With this configuration the grunt build will fail if errors are present in the js (though you can of course tell jshint to ignore some errors, as I have done in admin/tool/lp/amd/src/competency_rule_points.js and defining the Y global in lib/amd/src/yui.js ). The grunt task will not report warnings by default, but a new --show-lint-warnings flag will help achieve that. Editor integrations/stanadalone eslint tool will surely be a better way of getting eslint errors rather than using the grunt task.
2016-05-11 10:19:30 +01:00
"grunt-eslint": {
"version": "18.1.0",
"from": "grunt-eslint@>=18.1.0 <19.0.0",
"resolved": "https://registry.npmjs.org/grunt-eslint/-/grunt-eslint-18.1.0.tgz"
},
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"grunt-legacy-log": {
"version": "0.1.3",
"from": "grunt-legacy-log@>=0.1.0 <0.2.0",
"resolved": "https://registry.npmjs.org/grunt-legacy-log/-/grunt-legacy-log-0.1.3.tgz",
"dependencies": {
"lodash": {
"version": "2.4.2",
"from": "lodash@>=2.4.1 <2.5.0",
"resolved": "https://registry.npmjs.org/lodash/-/lodash-2.4.2.tgz"
MDL-52250 npm: shrinkwrap to lock down dependencies We've tried various approaches to lock down our dependencies and they have been flawed because dependencies in our included packages may not be locked down and previous attempts to do that have not been correct. With npm shrinkwrap we lock down versions so that any npm install will always install the exact same versions for all developers - see: https://docs.npmjs.com/cli/shrinkwrap (This is a lot like composer.lock for those more fluent with composer)
2015-12-03 17:00:50 +00:00
},
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"underscore.string": {
"version": "2.3.3",
"from": "underscore.string@>=2.3.3 <2.4.0",
"resolved": "https://registry.npmjs.org/underscore.string/-/underscore.string-2.3.3.tgz"
}
}
},
"grunt-legacy-log-utils": {
"version": "0.1.1",
"from": "grunt-legacy-log-utils@>=0.1.1 <0.2.0",
"resolved": "https://registry.npmjs.org/grunt-legacy-log-utils/-/grunt-legacy-log-utils-0.1.1.tgz",
"dependencies": {
"lodash": {
"version": "2.4.2",
"from": "lodash@>=2.4.1 <2.5.0",
"resolved": "https://registry.npmjs.org/lodash/-/lodash-2.4.2.tgz"
MDL-52250 npm: shrinkwrap to lock down dependencies We've tried various approaches to lock down our dependencies and they have been flawed because dependencies in our included packages may not be locked down and previous attempts to do that have not been correct. With npm shrinkwrap we lock down versions so that any npm install will always install the exact same versions for all developers - see: https://docs.npmjs.com/cli/shrinkwrap (This is a lot like composer.lock for those more fluent with composer)
2015-12-03 17:00:50 +00:00
},
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"underscore.string": {
"version": "2.3.3",
"from": "underscore.string@>=2.3.3 <2.4.0",
"resolved": "https://registry.npmjs.org/underscore.string/-/underscore.string-2.3.3.tgz"
MDL-52250 npm: shrinkwrap to lock down dependencies We've tried various approaches to lock down our dependencies and they have been flawed because dependencies in our included packages may not be locked down and previous attempts to do that have not been correct. With npm shrinkwrap we lock down versions so that any npm install will always install the exact same versions for all developers - see: https://docs.npmjs.com/cli/shrinkwrap (This is a lot like composer.lock for those more fluent with composer)
2015-12-03 17:00:50 +00:00
}
}
},
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"grunt-legacy-util": {
"version": "0.2.0",
"from": "grunt-legacy-util@>=0.2.0 <0.3.0",
MDL-49817 grunt: handle multiple watched files changed at once Includes multiple changes to the shifter task to simplify and support this: * Use grunt.file for shifter yui 'module' detection rather than our own 70 line function * Use grunt.util.spawn rather than our own exec for shifter * Improve behaviour on various yui subdirectories We have to add the 'async' depndency to npm because we are running multiple async operations in the single task. We use async.eachSeries to run each shifter job sequentally (else the output would be unreadable when running async). We also run shifter in non-recursive mode on the module directory so its not building everything (thanks to Ryan for pointing this out!)
2016-01-21 14:21:13 +00:00
"resolved": "https://registry.npmjs.org/grunt-legacy-util/-/grunt-legacy-util-0.2.0.tgz",
"dependencies": {
"async": {
"version": "0.1.22",
"from": "async@>=0.1.22 <0.2.0",
"resolved": "https://registry.npmjs.org/async/-/async-0.1.22.tgz"
}
}
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
},
"gzip-size": {
"version": "1.0.0",
"from": "gzip-size@>=1.0.0 <2.0.0",
"resolved": "https://registry.npmjs.org/gzip-size/-/gzip-size-1.0.0.tgz"
},
"handlebars": {
"version": "2.0.0",
"from": "handlebars@>=2.0.0 <2.1.0",
"resolved": "https://registry.npmjs.org/handlebars/-/handlebars-2.0.0.tgz",
MDL-52250 npm: shrinkwrap to lock down dependencies We've tried various approaches to lock down our dependencies and they have been flawed because dependencies in our included packages may not be locked down and previous attempts to do that have not been correct. With npm shrinkwrap we lock down versions so that any npm install will always install the exact same versions for all developers - see: https://docs.npmjs.com/cli/shrinkwrap (This is a lot like composer.lock for those more fluent with composer)
2015-12-03 17:00:50 +00:00
"dependencies": {
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"async": {
"version": "0.2.10",
"from": "async@>=0.2.6 <0.3.0",
"resolved": "https://registry.npmjs.org/async/-/async-0.2.10.tgz"
MDL-52250 npm: shrinkwrap to lock down dependencies We've tried various approaches to lock down our dependencies and they have been flawed because dependencies in our included packages may not be locked down and previous attempts to do that have not been correct. With npm shrinkwrap we lock down versions so that any npm install will always install the exact same versions for all developers - see: https://docs.npmjs.com/cli/shrinkwrap (This is a lot like composer.lock for those more fluent with composer)
2015-12-03 17:00:50 +00:00
},
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"source-map": {
"version": "0.1.43",
"from": "source-map@>=0.1.7 <0.2.0",
"resolved": "https://registry.npmjs.org/source-map/-/source-map-0.1.43.tgz"
MDL-52250 npm: shrinkwrap to lock down dependencies We've tried various approaches to lock down our dependencies and they have been flawed because dependencies in our included packages may not be locked down and previous attempts to do that have not been correct. With npm shrinkwrap we lock down versions so that any npm install will always install the exact same versions for all developers - see: https://docs.npmjs.com/cli/shrinkwrap (This is a lot like composer.lock for those more fluent with composer)
2015-12-03 17:00:50 +00:00
},
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"uglify-js": {
"version": "2.3.6",
"from": "uglify-js@>=2.3.0 <2.4.0",
"resolved": "https://registry.npmjs.org/uglify-js/-/uglify-js-2.3.6.tgz"
}
}
},
"har-validator": {
"version": "2.0.5",
"from": "har-validator@>=2.0.2 <2.1.0",
"resolved": "https://registry.npmjs.org/har-validator/-/har-validator-2.0.5.tgz"
},
"has-ansi": {
"version": "2.0.0",
"from": "has-ansi@>=2.0.0 <3.0.0",
"resolved": "https://registry.npmjs.org/has-ansi/-/has-ansi-2.0.0.tgz"
},
"hawk": {
"version": "3.1.2",
"from": "hawk@>=3.1.0 <3.2.0",
"resolved": "https://registry.npmjs.org/hawk/-/hawk-3.1.2.tgz"
},
"hoek": {
"version": "2.16.3",
"from": "hoek@>=2.0.0 <3.0.0",
"resolved": "https://registry.npmjs.org/hoek/-/hoek-2.16.3.tgz"
},
"hooker": {
"version": "0.2.3",
"from": "hooker@>=0.2.3 <0.3.0",
"resolved": "https://registry.npmjs.org/hooker/-/hooker-0.2.3.tgz"
},
"hosted-git-info": {
"version": "2.1.4",
"from": "hosted-git-info@>=2.1.4 <3.0.0",
"resolved": "https://registry.npmjs.org/hosted-git-info/-/hosted-git-info-2.1.4.tgz"
},
"htmlparser2": {
"version": "3.8.3",
"from": "htmlparser2@>=3.8.0 <3.9.0",
"resolved": "https://registry.npmjs.org/htmlparser2/-/htmlparser2-3.8.3.tgz"
},
"http-signature": {
"version": "1.1.0",
"from": "http-signature@>=1.1.0 <1.2.0",
"resolved": "https://registry.npmjs.org/http-signature/-/http-signature-1.1.0.tgz"
},
"iconv-lite": {
"version": "0.2.11",
"from": "iconv-lite@>=0.2.11 <0.3.0",
"resolved": "https://registry.npmjs.org/iconv-lite/-/iconv-lite-0.2.11.tgz"
},
MDL-52127 js: check amd files with eslint grunt task I have spent quite a lot of time working through the current list of eslint options and configuring them for Moodle style and I think this is a very good basis to start us at (as well as taking some of out jshint options out with https://www.npmjs.com/package/polyjuice ). Thanks to Andrew Nicols, Mark Johnson and Frédéric Massart for some refinements. With this configuration the grunt build will fail if errors are present in the js (though you can of course tell jshint to ignore some errors, as I have done in admin/tool/lp/amd/src/competency_rule_points.js and defining the Y global in lib/amd/src/yui.js ). The grunt task will not report warnings by default, but a new --show-lint-warnings flag will help achieve that. Editor integrations/stanadalone eslint tool will surely be a better way of getting eslint errors rather than using the grunt task.
2016-05-11 10:19:30 +01:00
"ignore": {
"version": "3.1.2",
"from": "ignore@>=3.1.2 <4.0.0",
"resolved": "https://registry.npmjs.org/ignore/-/ignore-3.1.2.tgz"
},
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"image-size": {
"version": "0.3.5",
"from": "image-size@>=0.3.5 <0.4.0",
"resolved": "https://registry.npmjs.org/image-size/-/image-size-0.3.5.tgz"
},
MDL-52127 js: check amd files with eslint grunt task I have spent quite a lot of time working through the current list of eslint options and configuring them for Moodle style and I think this is a very good basis to start us at (as well as taking some of out jshint options out with https://www.npmjs.com/package/polyjuice ). Thanks to Andrew Nicols, Mark Johnson and Frédéric Massart for some refinements. With this configuration the grunt build will fail if errors are present in the js (though you can of course tell jshint to ignore some errors, as I have done in admin/tool/lp/amd/src/competency_rule_points.js and defining the Y global in lib/amd/src/yui.js ). The grunt task will not report warnings by default, but a new --show-lint-warnings flag will help achieve that. Editor integrations/stanadalone eslint tool will surely be a better way of getting eslint errors rather than using the grunt task.
2016-05-11 10:19:30 +01:00
"imurmurhash": {
"version": "0.1.4",
"from": "imurmurhash@>=0.1.4 <0.2.0",
"resolved": "https://registry.npmjs.org/imurmurhash/-/imurmurhash-0.1.4.tgz"
},
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"indent-string": {
"version": "2.1.0",
"from": "indent-string@>=2.1.0 <3.0.0",
"resolved": "https://registry.npmjs.org/indent-string/-/indent-string-2.1.0.tgz"
},
MDL-52127 js: check amd files with eslint grunt task I have spent quite a lot of time working through the current list of eslint options and configuring them for Moodle style and I think this is a very good basis to start us at (as well as taking some of out jshint options out with https://www.npmjs.com/package/polyjuice ). Thanks to Andrew Nicols, Mark Johnson and Frédéric Massart for some refinements. With this configuration the grunt build will fail if errors are present in the js (though you can of course tell jshint to ignore some errors, as I have done in admin/tool/lp/amd/src/competency_rule_points.js and defining the Y global in lib/amd/src/yui.js ). The grunt task will not report warnings by default, but a new --show-lint-warnings flag will help achieve that. Editor integrations/stanadalone eslint tool will surely be a better way of getting eslint errors rather than using the grunt task.
2016-05-11 10:19:30 +01:00
"inflight": {
"version": "1.0.5",
"from": "inflight@>=1.0.4 <2.0.0",
"resolved": "https://registry.npmjs.org/inflight/-/inflight-1.0.5.tgz"
},
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"inherits": {
"version": "2.0.1",
"from": "inherits@>=2.0.0 <3.0.0",
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
},
MDL-52127 js: check amd files with eslint grunt task I have spent quite a lot of time working through the current list of eslint options and configuring them for Moodle style and I think this is a very good basis to start us at (as well as taking some of out jshint options out with https://www.npmjs.com/package/polyjuice ). Thanks to Andrew Nicols, Mark Johnson and Frédéric Massart for some refinements. With this configuration the grunt build will fail if errors are present in the js (though you can of course tell jshint to ignore some errors, as I have done in admin/tool/lp/amd/src/competency_rule_points.js and defining the Y global in lib/amd/src/yui.js ). The grunt task will not report warnings by default, but a new --show-lint-warnings flag will help achieve that. Editor integrations/stanadalone eslint tool will surely be a better way of getting eslint errors rather than using the grunt task.
2016-05-11 10:19:30 +01:00
"inquirer": {
"version": "0.12.0",
"from": "inquirer@>=0.12.0 <0.13.0",
"resolved": "https://registry.npmjs.org/inquirer/-/inquirer-0.12.0.tgz",
"dependencies": {
"lodash": {
"version": "4.13.1",
MDL-54889 jshint: stop using for everything but shifter Now jshint has been replaced by eslint.
2016-06-28 10:41:18 +01:00
"from": "lodash@4.13.1",
"resolved": "https://registry.npmjs.org/lodash/-/lodash-4.13.1.tgz"
MDL-52127 js: check amd files with eslint grunt task I have spent quite a lot of time working through the current list of eslint options and configuring them for Moodle style and I think this is a very good basis to start us at (as well as taking some of out jshint options out with https://www.npmjs.com/package/polyjuice ). Thanks to Andrew Nicols, Mark Johnson and Frédéric Massart for some refinements. With this configuration the grunt build will fail if errors are present in the js (though you can of course tell jshint to ignore some errors, as I have done in admin/tool/lp/amd/src/competency_rule_points.js and defining the Y global in lib/amd/src/yui.js ). The grunt task will not report warnings by default, but a new --show-lint-warnings flag will help achieve that. Editor integrations/stanadalone eslint tool will surely be a better way of getting eslint errors rather than using the grunt task.
2016-05-11 10:19:30 +01:00
}
}
},
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"is-arrayish": {
"version": "0.2.1",
"from": "is-arrayish@>=0.2.1 <0.3.0",
"resolved": "https://registry.npmjs.org/is-arrayish/-/is-arrayish-0.2.1.tgz"
},
"is-buffer": {
"version": "1.1.1",
"from": "is-buffer@>=1.0.2 <2.0.0",
"resolved": "https://registry.npmjs.org/is-buffer/-/is-buffer-1.1.1.tgz"
},
"is-builtin-module": {
"version": "1.0.0",
"from": "is-builtin-module@>=1.0.0 <2.0.0",
"resolved": "https://registry.npmjs.org/is-builtin-module/-/is-builtin-module-1.0.0.tgz"
},
"is-finite": {
"version": "1.0.1",
"from": "is-finite@>=1.0.0 <2.0.0",
"resolved": "https://registry.npmjs.org/is-finite/-/is-finite-1.0.1.tgz"
},
MDL-52127 js: check amd files with eslint grunt task I have spent quite a lot of time working through the current list of eslint options and configuring them for Moodle style and I think this is a very good basis to start us at (as well as taking some of out jshint options out with https://www.npmjs.com/package/polyjuice ). Thanks to Andrew Nicols, Mark Johnson and Frédéric Massart for some refinements. With this configuration the grunt build will fail if errors are present in the js (though you can of course tell jshint to ignore some errors, as I have done in admin/tool/lp/amd/src/competency_rule_points.js and defining the Y global in lib/amd/src/yui.js ). The grunt task will not report warnings by default, but a new --show-lint-warnings flag will help achieve that. Editor integrations/stanadalone eslint tool will surely be a better way of getting eslint errors rather than using the grunt task.
2016-05-11 10:19:30 +01:00
"is-fullwidth-code-point": {
"version": "1.0.0",
"from": "is-fullwidth-code-point@>=1.0.0 <2.0.0",
"resolved": "https://registry.npmjs.org/is-fullwidth-code-point/-/is-fullwidth-code-point-1.0.0.tgz"
},
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"is-my-json-valid": {
"version": "2.12.3",
"from": "is-my-json-valid@>=2.12.3 <3.0.0",
"resolved": "https://registry.npmjs.org/is-my-json-valid/-/is-my-json-valid-2.12.3.tgz"
},
MDL-52127 js: check amd files with eslint grunt task I have spent quite a lot of time working through the current list of eslint options and configuring them for Moodle style and I think this is a very good basis to start us at (as well as taking some of out jshint options out with https://www.npmjs.com/package/polyjuice ). Thanks to Andrew Nicols, Mark Johnson and Frédéric Massart for some refinements. With this configuration the grunt build will fail if errors are present in the js (though you can of course tell jshint to ignore some errors, as I have done in admin/tool/lp/amd/src/competency_rule_points.js and defining the Y global in lib/amd/src/yui.js ). The grunt task will not report warnings by default, but a new --show-lint-warnings flag will help achieve that. Editor integrations/stanadalone eslint tool will surely be a better way of getting eslint errors rather than using the grunt task.
2016-05-11 10:19:30 +01:00
"is-path-cwd": {
"version": "1.0.0",
"from": "is-path-cwd@>=1.0.0 <2.0.0",
"resolved": "https://registry.npmjs.org/is-path-cwd/-/is-path-cwd-1.0.0.tgz"
},
"is-path-in-cwd": {
"version": "1.0.0",
"from": "is-path-in-cwd@>=1.0.0 <2.0.0",
"resolved": "https://registry.npmjs.org/is-path-in-cwd/-/is-path-in-cwd-1.0.0.tgz"
},
"is-path-inside": {
"version": "1.0.0",
"from": "is-path-inside@>=1.0.0 <2.0.0",
"resolved": "https://registry.npmjs.org/is-path-inside/-/is-path-inside-1.0.0.tgz"
},
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"is-property": {
"version": "1.0.2",
"from": "is-property@>=1.0.0 <2.0.0",
"resolved": "https://registry.npmjs.org/is-property/-/is-property-1.0.2.tgz"
},
MDL-52127 js: check amd files with eslint grunt task I have spent quite a lot of time working through the current list of eslint options and configuring them for Moodle style and I think this is a very good basis to start us at (as well as taking some of out jshint options out with https://www.npmjs.com/package/polyjuice ). Thanks to Andrew Nicols, Mark Johnson and Frédéric Massart for some refinements. With this configuration the grunt build will fail if errors are present in the js (though you can of course tell jshint to ignore some errors, as I have done in admin/tool/lp/amd/src/competency_rule_points.js and defining the Y global in lib/amd/src/yui.js ). The grunt task will not report warnings by default, but a new --show-lint-warnings flag will help achieve that. Editor integrations/stanadalone eslint tool will surely be a better way of getting eslint errors rather than using the grunt task.
2016-05-11 10:19:30 +01:00
"is-resolvable": {
"version": "1.0.0",
"from": "is-resolvable@>=1.0.0 <2.0.0",
"resolved": "https://registry.npmjs.org/is-resolvable/-/is-resolvable-1.0.0.tgz"
},
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"is-typedarray": {
"version": "1.0.0",
"from": "is-typedarray@>=1.0.0 <1.1.0",
"resolved": "https://registry.npmjs.org/is-typedarray/-/is-typedarray-1.0.0.tgz"
},
"is-utf8": {
"version": "0.2.1",
"from": "is-utf8@>=0.2.0 <0.3.0",
"resolved": "https://registry.npmjs.org/is-utf8/-/is-utf8-0.2.1.tgz"
},
"isarray": {
"version": "0.0.1",
"from": "isarray@0.0.1",
"resolved": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz"
},
"isstream": {
"version": "0.1.2",
"from": "isstream@>=0.1.2 <0.2.0",
"resolved": "https://registry.npmjs.org/isstream/-/isstream-0.1.2.tgz"
},
"istanbul": {
"version": "0.1.37",
"from": "istanbul@0.1.37",
"resolved": "https://registry.npmjs.org/istanbul/-/istanbul-0.1.37.tgz",
"dependencies": {
"async": {
"version": "0.2.10",
"from": "async@>=0.2.0 <0.3.0",
"resolved": "https://registry.npmjs.org/async/-/async-0.2.10.tgz"
MDL-52250 npm: shrinkwrap to lock down dependencies We've tried various approaches to lock down our dependencies and they have been flawed because dependencies in our included packages may not be locked down and previous attempts to do that have not been correct. With npm shrinkwrap we lock down versions so that any npm install will always install the exact same versions for all developers - see: https://docs.npmjs.com/cli/shrinkwrap (This is a lot like composer.lock for those more fluent with composer)
2015-12-03 17:00:50 +00:00
},
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"handlebars": {
"version": "1.0.12",
"from": "handlebars@>=1.0.0 <1.1.0",
"resolved": "https://registry.npmjs.org/handlebars/-/handlebars-1.0.12.tgz"
},
"mkdirp": {
"version": "0.3.5",
"from": "mkdirp@>=0.3.0 <0.4.0",
"resolved": "https://registry.npmjs.org/mkdirp/-/mkdirp-0.3.5.tgz"
MDL-52250 npm: shrinkwrap to lock down dependencies We've tried various approaches to lock down our dependencies and they have been flawed because dependencies in our included packages may not be locked down and previous attempts to do that have not been correct. With npm shrinkwrap we lock down versions so that any npm install will always install the exact same versions for all developers - see: https://docs.npmjs.com/cli/shrinkwrap (This is a lot like composer.lock for those more fluent with composer)
2015-12-03 17:00:50 +00:00
},
"nopt": {
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"version": "2.1.2",
"from": "nopt@>=2.1.0 <2.2.0",
"resolved": "https://registry.npmjs.org/nopt/-/nopt-2.1.2.tgz"
MDL-52250 npm: shrinkwrap to lock down dependencies We've tried various approaches to lock down our dependencies and they have been flawed because dependencies in our included packages may not be locked down and previous attempts to do that have not been correct. With npm shrinkwrap we lock down versions so that any npm install will always install the exact same versions for all developers - see: https://docs.npmjs.com/cli/shrinkwrap (This is a lot like composer.lock for those more fluent with composer)
2015-12-03 17:00:50 +00:00
},
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"source-map": {
"version": "0.1.43",
"from": "source-map@>=0.1.7 <0.2.0",
"resolved": "https://registry.npmjs.org/source-map/-/source-map-0.1.43.tgz"
MDL-52250 npm: shrinkwrap to lock down dependencies We've tried various approaches to lock down our dependencies and they have been flawed because dependencies in our included packages may not be locked down and previous attempts to do that have not been correct. With npm shrinkwrap we lock down versions so that any npm install will always install the exact same versions for all developers - see: https://docs.npmjs.com/cli/shrinkwrap (This is a lot like composer.lock for those more fluent with composer)
2015-12-03 17:00:50 +00:00
},
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"uglify-js": {
"version": "2.3.6",
"from": "uglify-js@>=2.3.0 <2.4.0",
"resolved": "https://registry.npmjs.org/uglify-js/-/uglify-js-2.3.6.tgz"
}
}
},
"jodid25519": {
"version": "1.0.2",
"from": "jodid25519@>=1.0.0 <2.0.0",
"resolved": "https://registry.npmjs.org/jodid25519/-/jodid25519-1.0.2.tgz"
},
"js-yaml": {
"version": "2.0.5",
"from": "js-yaml@>=2.0.5 <2.1.0",
"resolved": "https://registry.npmjs.org/js-yaml/-/js-yaml-2.0.5.tgz"
},
"jsbn": {
"version": "0.1.0",
"from": "jsbn@>=0.1.0 <0.2.0",
"resolved": "https://registry.npmjs.org/jsbn/-/jsbn-0.1.0.tgz"
},
"jslint": {
"version": "0.3.4",
"from": "jslint@>=0.3.0 <0.4.0",
"resolved": "https://registry.npmjs.org/jslint/-/jslint-0.3.4.tgz",
"dependencies": {
"glob": {
"version": "3.2.11",
"from": "glob@>=3.2.8 <3.3.0",
"resolved": "https://registry.npmjs.org/glob/-/glob-3.2.11.tgz"
},
"minimatch": {
"version": "0.3.0",
"from": "minimatch@>=0.3.0 <0.4.0",
"resolved": "https://registry.npmjs.org/minimatch/-/minimatch-0.3.0.tgz"
}
}
},
"json-schema": {
"version": "0.2.2",
"from": "json-schema@0.2.2",
"resolved": "https://registry.npmjs.org/json-schema/-/json-schema-0.2.2.tgz"
},
MDL-52127 js: check amd files with eslint grunt task I have spent quite a lot of time working through the current list of eslint options and configuring them for Moodle style and I think this is a very good basis to start us at (as well as taking some of out jshint options out with https://www.npmjs.com/package/polyjuice ). Thanks to Andrew Nicols, Mark Johnson and Frédéric Massart for some refinements. With this configuration the grunt build will fail if errors are present in the js (though you can of course tell jshint to ignore some errors, as I have done in admin/tool/lp/amd/src/competency_rule_points.js and defining the Y global in lib/amd/src/yui.js ). The grunt task will not report warnings by default, but a new --show-lint-warnings flag will help achieve that. Editor integrations/stanadalone eslint tool will surely be a better way of getting eslint errors rather than using the grunt task.
2016-05-11 10:19:30 +01:00
"json-stable-stringify": {
"version": "1.0.1",
"from": "json-stable-stringify@>=1.0.0 <2.0.0",
"resolved": "https://registry.npmjs.org/json-stable-stringify/-/json-stable-stringify-1.0.1.tgz"
},
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"json-stringify-safe": {
"version": "5.0.1",
"from": "json-stringify-safe@>=5.0.1 <5.1.0",
"resolved": "https://registry.npmjs.org/json-stringify-safe/-/json-stringify-safe-5.0.1.tgz"
},
MDL-52127 js: check amd files with eslint grunt task I have spent quite a lot of time working through the current list of eslint options and configuring them for Moodle style and I think this is a very good basis to start us at (as well as taking some of out jshint options out with https://www.npmjs.com/package/polyjuice ). Thanks to Andrew Nicols, Mark Johnson and Frédéric Massart for some refinements. With this configuration the grunt build will fail if errors are present in the js (though you can of course tell jshint to ignore some errors, as I have done in admin/tool/lp/amd/src/competency_rule_points.js and defining the Y global in lib/amd/src/yui.js ). The grunt task will not report warnings by default, but a new --show-lint-warnings flag will help achieve that. Editor integrations/stanadalone eslint tool will surely be a better way of getting eslint errors rather than using the grunt task.
2016-05-11 10:19:30 +01:00
"jsonify": {
"version": "0.0.0",
"from": "jsonify@>=0.0.0 <0.1.0",
"resolved": "https://registry.npmjs.org/jsonify/-/jsonify-0.0.0.tgz"
},
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"jsonpointer": {
"version": "2.0.0",
"from": "jsonpointer@2.0.0",
"resolved": "https://registry.npmjs.org/jsonpointer/-/jsonpointer-2.0.0.tgz"
},
"jsprim": {
"version": "1.2.2",
"from": "jsprim@>=1.2.2 <2.0.0",
"resolved": "https://registry.npmjs.org/jsprim/-/jsprim-1.2.2.tgz"
},
"kind-of": {
"version": "2.0.1",
"from": "kind-of@>=2.0.0 <3.0.0",
"resolved": "https://registry.npmjs.org/kind-of/-/kind-of-2.0.1.tgz"
},
"knox": {
"version": "0.8.10",
"from": "knox@>=0.8.0 <0.9.0",
"resolved": "https://registry.npmjs.org/knox/-/knox-0.8.10.tgz"
},
"lazy-cache": {
"version": "0.2.7",
"from": "lazy-cache@>=0.2.4 <0.3.0",
"resolved": "https://registry.npmjs.org/lazy-cache/-/lazy-cache-0.2.7.tgz"
},
"less": {
"version": "2.5.3",
"from": "less@>=2.5.0 <2.6.0",
"resolved": "https://registry.npmjs.org/less/-/less-2.5.3.tgz",
"dependencies": {
"graceful-fs": {
"version": "3.0.8",
"from": "graceful-fs@>=3.0.5 <4.0.0",
"resolved": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-3.0.8.tgz"
}
}
},
MDL-52127 js: check amd files with eslint grunt task I have spent quite a lot of time working through the current list of eslint options and configuring them for Moodle style and I think this is a very good basis to start us at (as well as taking some of out jshint options out with https://www.npmjs.com/package/polyjuice ). Thanks to Andrew Nicols, Mark Johnson and Frédéric Massart for some refinements. With this configuration the grunt build will fail if errors are present in the js (though you can of course tell jshint to ignore some errors, as I have done in admin/tool/lp/amd/src/competency_rule_points.js and defining the Y global in lib/amd/src/yui.js ). The grunt task will not report warnings by default, but a new --show-lint-warnings flag will help achieve that. Editor integrations/stanadalone eslint tool will surely be a better way of getting eslint errors rather than using the grunt task.
2016-05-11 10:19:30 +01:00
"levn": {
"version": "0.3.0",
"from": "levn@>=0.3.0 <0.4.0",
"resolved": "https://registry.npmjs.org/levn/-/levn-0.3.0.tgz"
},
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"load-json-file": {
"version": "1.1.0",
"from": "load-json-file@>=1.0.0 <2.0.0",
"resolved": "https://registry.npmjs.org/load-json-file/-/load-json-file-1.1.0.tgz",
"dependencies": {
"graceful-fs": {
"version": "4.1.2",
"from": "graceful-fs@>=4.1.2 <5.0.0",
"resolved": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz"
}
}
},
"lodash": {
"version": "0.9.2",
"from": "lodash@>=0.9.2 <0.10.0",
"resolved": "https://registry.npmjs.org/lodash/-/lodash-0.9.2.tgz"
},
"longest": {
"version": "1.0.1",
"from": "longest@>=1.0.1 <2.0.0",
"resolved": "https://registry.npmjs.org/longest/-/longest-1.0.1.tgz"
},
"loud-rejection": {
"version": "1.2.0",
"from": "loud-rejection@>=1.0.0 <2.0.0",
"resolved": "https://registry.npmjs.org/loud-rejection/-/loud-rejection-1.2.0.tgz"
},
"lru-cache": {
"version": "2.7.3",
"from": "lru-cache@>=2.0.0 <3.0.0",
"resolved": "https://registry.npmjs.org/lru-cache/-/lru-cache-2.7.3.tgz"
},
"map-obj": {
"version": "1.0.1",
"from": "map-obj@>=1.0.1 <2.0.0",
"resolved": "https://registry.npmjs.org/map-obj/-/map-obj-1.0.1.tgz"
},
"maxmin": {
"version": "1.1.0",
"from": "maxmin@>=1.0.0 <2.0.0",
"resolved": "https://registry.npmjs.org/maxmin/-/maxmin-1.1.0.tgz"
},
"meow": {
"version": "3.7.0",
"from": "meow@>=3.1.0 <4.0.0",
"resolved": "https://registry.npmjs.org/meow/-/meow-3.7.0.tgz",
"dependencies": {
"minimist": {
"version": "1.2.0",
"from": "minimist@>=1.1.3 <2.0.0",
"resolved": "https://registry.npmjs.org/minimist/-/minimist-1.2.0.tgz"
}
}
},
"mime": {
"version": "1.3.4",
"from": "mime@>=1.2.11 <2.0.0",
"resolved": "https://registry.npmjs.org/mime/-/mime-1.3.4.tgz"
},
"mime-db": {
"version": "1.21.0",
"from": "mime-db@>=1.21.0 <1.22.0",
"resolved": "https://registry.npmjs.org/mime-db/-/mime-db-1.21.0.tgz"
},
"mime-types": {
"version": "2.1.9",
"from": "mime-types@>=2.1.7 <2.2.0",
"resolved": "https://registry.npmjs.org/mime-types/-/mime-types-2.1.9.tgz"
},
"minimatch": {
"version": "0.2.14",
"from": "minimatch@>=0.2.12 <0.3.0",
"resolved": "https://registry.npmjs.org/minimatch/-/minimatch-0.2.14.tgz"
},
"minimist": {
"version": "0.0.8",
"from": "minimist@0.0.8",
"resolved": "https://registry.npmjs.org/minimist/-/minimist-0.0.8.tgz"
},
"mkdirp": {
"version": "0.5.1",
"from": "mkdirp@>=0.5.0 <0.6.0",
"resolved": "https://registry.npmjs.org/mkdirp/-/mkdirp-0.5.1.tgz"
},
MDL-52127 js: check amd files with eslint grunt task I have spent quite a lot of time working through the current list of eslint options and configuring them for Moodle style and I think this is a very good basis to start us at (as well as taking some of out jshint options out with https://www.npmjs.com/package/polyjuice ). Thanks to Andrew Nicols, Mark Johnson and Frédéric Massart for some refinements. With this configuration the grunt build will fail if errors are present in the js (though you can of course tell jshint to ignore some errors, as I have done in admin/tool/lp/amd/src/competency_rule_points.js and defining the Y global in lib/amd/src/yui.js ). The grunt task will not report warnings by default, but a new --show-lint-warnings flag will help achieve that. Editor integrations/stanadalone eslint tool will surely be a better way of getting eslint errors rather than using the grunt task.
2016-05-11 10:19:30 +01:00
"ms": {
"version": "0.7.1",
"from": "ms@0.7.1",
"resolved": "https://registry.npmjs.org/ms/-/ms-0.7.1.tgz"
},
"mute-stream": {
"version": "0.0.5",
"from": "mute-stream@0.0.5",
"resolved": "https://registry.npmjs.org/mute-stream/-/mute-stream-0.0.5.tgz"
},
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"node-uuid": {
"version": "1.4.7",
"from": "node-uuid@>=1.4.7 <1.5.0",
"resolved": "https://registry.npmjs.org/node-uuid/-/node-uuid-1.4.7.tgz"
},
"nopt": {
"version": "1.0.10",
"from": "nopt@>=1.0.10 <1.1.0",
"resolved": "https://registry.npmjs.org/nopt/-/nopt-1.0.10.tgz"
},
"noptify": {
"version": "0.0.3",
"from": "noptify@>=0.0.3 <0.1.0",
"resolved": "https://registry.npmjs.org/noptify/-/noptify-0.0.3.tgz",
"dependencies": {
"nopt": {
"version": "2.0.0",
"from": "nopt@>=2.0.0 <2.1.0",
"resolved": "https://registry.npmjs.org/nopt/-/nopt-2.0.0.tgz"
}
}
},
"normalize-package-data": {
"version": "2.3.5",
"from": "normalize-package-data@>=2.3.4 <3.0.0",
"resolved": "https://registry.npmjs.org/normalize-package-data/-/normalize-package-data-2.3.5.tgz"
},
"number-is-nan": {
"version": "1.0.0",
"from": "number-is-nan@>=1.0.0 <2.0.0",
"resolved": "https://registry.npmjs.org/number-is-nan/-/number-is-nan-1.0.0.tgz"
},
"oauth-sign": {
"version": "0.8.0",
"from": "oauth-sign@>=0.8.0 <0.9.0",
"resolved": "https://registry.npmjs.org/oauth-sign/-/oauth-sign-0.8.0.tgz"
},
"object-assign": {
"version": "4.0.1",
"from": "object-assign@>=4.0.1 <5.0.0",
"resolved": "https://registry.npmjs.org/object-assign/-/object-assign-4.0.1.tgz"
},
MDL-52127 js: check amd files with eslint grunt task I have spent quite a lot of time working through the current list of eslint options and configuring them for Moodle style and I think this is a very good basis to start us at (as well as taking some of out jshint options out with https://www.npmjs.com/package/polyjuice ). Thanks to Andrew Nicols, Mark Johnson and Frédéric Massart for some refinements. With this configuration the grunt build will fail if errors are present in the js (though you can of course tell jshint to ignore some errors, as I have done in admin/tool/lp/amd/src/competency_rule_points.js and defining the Y global in lib/amd/src/yui.js ). The grunt task will not report warnings by default, but a new --show-lint-warnings flag will help achieve that. Editor integrations/stanadalone eslint tool will surely be a better way of getting eslint errors rather than using the grunt task.
2016-05-11 10:19:30 +01:00
"once": {
"version": "1.3.3",
"from": "once@>=1.3.0 <2.0.0",
"resolved": "https://registry.npmjs.org/once/-/once-1.3.3.tgz"
},
"onetime": {
"version": "1.1.0",
"from": "onetime@>=1.0.0 <2.0.0",
"resolved": "https://registry.npmjs.org/onetime/-/onetime-1.1.0.tgz"
},
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"optimist": {
"version": "0.3.7",
"from": "optimist@>=0.3.0 <0.4.0",
"resolved": "https://registry.npmjs.org/optimist/-/optimist-0.3.7.tgz"
},
MDL-52127 js: check amd files with eslint grunt task I have spent quite a lot of time working through the current list of eslint options and configuring them for Moodle style and I think this is a very good basis to start us at (as well as taking some of out jshint options out with https://www.npmjs.com/package/polyjuice ). Thanks to Andrew Nicols, Mark Johnson and Frédéric Massart for some refinements. With this configuration the grunt build will fail if errors are present in the js (though you can of course tell jshint to ignore some errors, as I have done in admin/tool/lp/amd/src/competency_rule_points.js and defining the Y global in lib/amd/src/yui.js ). The grunt task will not report warnings by default, but a new --show-lint-warnings flag will help achieve that. Editor integrations/stanadalone eslint tool will surely be a better way of getting eslint errors rather than using the grunt task.
2016-05-11 10:19:30 +01:00
"optionator": {
"version": "0.8.1",
"from": "optionator@>=0.8.1 <0.9.0",
"resolved": "https://registry.npmjs.org/optionator/-/optionator-0.8.1.tgz",
"dependencies": {
"wordwrap": {
"version": "1.0.0",
"from": "wordwrap@>=1.0.0 <1.1.0",
"resolved": "https://registry.npmjs.org/wordwrap/-/wordwrap-1.0.0.tgz"
}
}
},
"os-homedir": {
"version": "1.0.1",
"from": "os-homedir@>=1.0.0 <2.0.0",
"resolved": "https://registry.npmjs.org/os-homedir/-/os-homedir-1.0.1.tgz"
},
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"pako": {
"version": "0.2.8",
"from": "pako@>=0.2.0 <0.3.0",
"resolved": "https://registry.npmjs.org/pako/-/pako-0.2.8.tgz"
},
"parse-json": {
"version": "2.2.0",
"from": "parse-json@>=2.2.0 <3.0.0",
"resolved": "https://registry.npmjs.org/parse-json/-/parse-json-2.2.0.tgz"
},
"parserlib": {
"version": "0.2.5",
"from": "parserlib@>=0.2.2 <0.3.0",
"resolved": "https://registry.npmjs.org/parserlib/-/parserlib-0.2.5.tgz"
},
"path-exists": {
"version": "2.1.0",
"from": "path-exists@>=2.0.0 <3.0.0",
"resolved": "https://registry.npmjs.org/path-exists/-/path-exists-2.1.0.tgz"
},
MDL-52127 js: check amd files with eslint grunt task I have spent quite a lot of time working through the current list of eslint options and configuring them for Moodle style and I think this is a very good basis to start us at (as well as taking some of out jshint options out with https://www.npmjs.com/package/polyjuice ). Thanks to Andrew Nicols, Mark Johnson and Frédéric Massart for some refinements. With this configuration the grunt build will fail if errors are present in the js (though you can of course tell jshint to ignore some errors, as I have done in admin/tool/lp/amd/src/competency_rule_points.js and defining the Y global in lib/amd/src/yui.js ). The grunt task will not report warnings by default, but a new --show-lint-warnings flag will help achieve that. Editor integrations/stanadalone eslint tool will surely be a better way of getting eslint errors rather than using the grunt task.
2016-05-11 10:19:30 +01:00
"path-is-absolute": {
"version": "1.0.0",
"from": "path-is-absolute@>=1.0.0 <2.0.0",
"resolved": "https://registry.npmjs.org/path-is-absolute/-/path-is-absolute-1.0.0.tgz"
},
"path-is-inside": {
"version": "1.0.1",
"from": "path-is-inside@>=1.0.1 <2.0.0",
"resolved": "https://registry.npmjs.org/path-is-inside/-/path-is-inside-1.0.1.tgz"
},
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"path-type": {
"version": "1.1.0",
"from": "path-type@>=1.0.0 <2.0.0",
"resolved": "https://registry.npmjs.org/path-type/-/path-type-1.1.0.tgz",
"dependencies": {
"graceful-fs": {
"version": "4.1.2",
"from": "graceful-fs@>=4.1.2 <5.0.0",
"resolved": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz"
}
}
},
"pify": {
"version": "2.3.0",
"from": "pify@>=2.0.0 <3.0.0",
"resolved": "https://registry.npmjs.org/pify/-/pify-2.3.0.tgz"
},
"pinkie": {
"version": "2.0.1",
"from": "pinkie@>=2.0.0 <3.0.0",
"resolved": "https://registry.npmjs.org/pinkie/-/pinkie-2.0.1.tgz"
},
"pinkie-promise": {
"version": "2.0.0",
"from": "pinkie-promise@>=2.0.0 <3.0.0",
"resolved": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-2.0.0.tgz"
},
MDL-52127 js: check amd files with eslint grunt task I have spent quite a lot of time working through the current list of eslint options and configuring them for Moodle style and I think this is a very good basis to start us at (as well as taking some of out jshint options out with https://www.npmjs.com/package/polyjuice ). Thanks to Andrew Nicols, Mark Johnson and Frédéric Massart for some refinements. With this configuration the grunt build will fail if errors are present in the js (though you can of course tell jshint to ignore some errors, as I have done in admin/tool/lp/amd/src/competency_rule_points.js and defining the Y global in lib/amd/src/yui.js ). The grunt task will not report warnings by default, but a new --show-lint-warnings flag will help achieve that. Editor integrations/stanadalone eslint tool will surely be a better way of getting eslint errors rather than using the grunt task.
2016-05-11 10:19:30 +01:00
"pluralize": {
"version": "1.2.1",
"from": "pluralize@>=1.2.1 <2.0.0",
"resolved": "https://registry.npmjs.org/pluralize/-/pluralize-1.2.1.tgz"
},
"prelude-ls": {
"version": "1.1.2",
"from": "prelude-ls@>=1.1.2 <1.2.0",
"resolved": "https://registry.npmjs.org/prelude-ls/-/prelude-ls-1.1.2.tgz"
},
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"pretty-bytes": {
"version": "1.0.4",
"from": "pretty-bytes@>=1.0.0 <2.0.0",
"resolved": "https://registry.npmjs.org/pretty-bytes/-/pretty-bytes-1.0.4.tgz"
},
"process-nextick-args": {
"version": "1.0.6",
"from": "process-nextick-args@>=1.0.6 <1.1.0",
"resolved": "https://registry.npmjs.org/process-nextick-args/-/process-nextick-args-1.0.6.tgz"
},
"progress": {
"version": "0.1.0",
"from": "progress@>=0.1.0 <0.2.0",
"resolved": "https://registry.npmjs.org/progress/-/progress-0.1.0.tgz"
},
"promise": {
"version": "6.1.0",
"from": "promise@>=6.0.1 <7.0.0",
"resolved": "https://registry.npmjs.org/promise/-/promise-6.1.0.tgz"
},
"prr": {
"version": "0.0.0",
"from": "prr@>=0.0.0 <0.1.0",
"resolved": "https://registry.npmjs.org/prr/-/prr-0.0.0.tgz"
},
"qs": {
"version": "5.2.0",
"from": "qs@>=5.2.0 <5.3.0",
"resolved": "https://registry.npmjs.org/qs/-/qs-5.2.0.tgz"
},
MDL-52127 js: check amd files with eslint grunt task I have spent quite a lot of time working through the current list of eslint options and configuring them for Moodle style and I think this is a very good basis to start us at (as well as taking some of out jshint options out with https://www.npmjs.com/package/polyjuice ). Thanks to Andrew Nicols, Mark Johnson and Frédéric Massart for some refinements. With this configuration the grunt build will fail if errors are present in the js (though you can of course tell jshint to ignore some errors, as I have done in admin/tool/lp/amd/src/competency_rule_points.js and defining the Y global in lib/amd/src/yui.js ). The grunt task will not report warnings by default, but a new --show-lint-warnings flag will help achieve that. Editor integrations/stanadalone eslint tool will surely be a better way of getting eslint errors rather than using the grunt task.
2016-05-11 10:19:30 +01:00
"read-json-sync": {
"version": "1.1.1",
"from": "read-json-sync@>=1.1.0 <2.0.0",
"resolved": "https://registry.npmjs.org/read-json-sync/-/read-json-sync-1.1.1.tgz",
"dependencies": {
"graceful-fs": {
"version": "4.1.4",
"from": "graceful-fs@4.1.4",
"resolved": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.4.tgz"
}
}
},
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"read-pkg": {
"version": "1.1.0",
"from": "read-pkg@>=1.0.0 <2.0.0",
"resolved": "https://registry.npmjs.org/read-pkg/-/read-pkg-1.1.0.tgz"
},
"read-pkg-up": {
"version": "1.0.1",
"from": "read-pkg-up@>=1.0.1 <2.0.0",
"resolved": "https://registry.npmjs.org/read-pkg-up/-/read-pkg-up-1.0.1.tgz"
},
"readable-stream": {
"version": "1.1.13",
"from": "readable-stream@>=1.1.0 <1.2.0",
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-1.1.13.tgz"
},
MDL-52127 js: check amd files with eslint grunt task I have spent quite a lot of time working through the current list of eslint options and configuring them for Moodle style and I think this is a very good basis to start us at (as well as taking some of out jshint options out with https://www.npmjs.com/package/polyjuice ). Thanks to Andrew Nicols, Mark Johnson and Frédéric Massart for some refinements. With this configuration the grunt build will fail if errors are present in the js (though you can of course tell jshint to ignore some errors, as I have done in admin/tool/lp/amd/src/competency_rule_points.js and defining the Y global in lib/amd/src/yui.js ). The grunt task will not report warnings by default, but a new --show-lint-warnings flag will help achieve that. Editor integrations/stanadalone eslint tool will surely be a better way of getting eslint errors rather than using the grunt task.
2016-05-11 10:19:30 +01:00
"readline2": {
"version": "1.0.1",
"from": "readline2@>=1.0.1 <2.0.0",
"resolved": "https://registry.npmjs.org/readline2/-/readline2-1.0.1.tgz"
},
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"redent": {
"version": "1.0.0",
"from": "redent@>=1.0.0 <2.0.0",
"resolved": "https://registry.npmjs.org/redent/-/redent-1.0.0.tgz"
},
"repeat-string": {
"version": "1.5.2",
"from": "repeat-string@>=1.5.2 <2.0.0",
"resolved": "https://registry.npmjs.org/repeat-string/-/repeat-string-1.5.2.tgz"
},
"repeating": {
"version": "2.0.0",
"from": "repeating@>=2.0.0 <3.0.0",
"resolved": "https://registry.npmjs.org/repeating/-/repeating-2.0.0.tgz"
},
"request": {
"version": "2.67.0",
"from": "request@>=2.51.0 <3.0.0",
"resolved": "https://registry.npmjs.org/request/-/request-2.67.0.tgz"
},
MDL-52127 js: check amd files with eslint grunt task I have spent quite a lot of time working through the current list of eslint options and configuring them for Moodle style and I think this is a very good basis to start us at (as well as taking some of out jshint options out with https://www.npmjs.com/package/polyjuice ). Thanks to Andrew Nicols, Mark Johnson and Frédéric Massart for some refinements. With this configuration the grunt build will fail if errors are present in the js (though you can of course tell jshint to ignore some errors, as I have done in admin/tool/lp/amd/src/competency_rule_points.js and defining the Y global in lib/amd/src/yui.js ). The grunt task will not report warnings by default, but a new --show-lint-warnings flag will help achieve that. Editor integrations/stanadalone eslint tool will surely be a better way of getting eslint errors rather than using the grunt task.
2016-05-11 10:19:30 +01:00
"require-uncached": {
"version": "1.0.2",
"from": "require-uncached@>=1.0.2 <2.0.0",
"resolved": "https://registry.npmjs.org/require-uncached/-/require-uncached-1.0.2.tgz"
},
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"resolve": {
"version": "0.4.3",
"from": "resolve@>=0.4.0 <0.5.0",
"resolved": "https://registry.npmjs.org/resolve/-/resolve-0.4.3.tgz"
},
MDL-52127 js: check amd files with eslint grunt task I have spent quite a lot of time working through the current list of eslint options and configuring them for Moodle style and I think this is a very good basis to start us at (as well as taking some of out jshint options out with https://www.npmjs.com/package/polyjuice ). Thanks to Andrew Nicols, Mark Johnson and Frédéric Massart for some refinements. With this configuration the grunt build will fail if errors are present in the js (though you can of course tell jshint to ignore some errors, as I have done in admin/tool/lp/amd/src/competency_rule_points.js and defining the Y global in lib/amd/src/yui.js ). The grunt task will not report warnings by default, but a new --show-lint-warnings flag will help achieve that. Editor integrations/stanadalone eslint tool will surely be a better way of getting eslint errors rather than using the grunt task.
2016-05-11 10:19:30 +01:00
"resolve-from": {
"version": "1.0.1",
"from": "resolve-from@>=1.0.0 <2.0.0",
"resolved": "https://registry.npmjs.org/resolve-from/-/resolve-from-1.0.1.tgz"
},
"restore-cursor": {
"version": "1.0.1",
"from": "restore-cursor@>=1.0.1 <2.0.0",
"resolved": "https://registry.npmjs.org/restore-cursor/-/restore-cursor-1.0.1.tgz"
},
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"right-align": {
"version": "0.1.3",
"from": "right-align@>=0.1.1 <0.2.0",
"resolved": "https://registry.npmjs.org/right-align/-/right-align-0.1.3.tgz"
},
"rimraf": {
"version": "2.2.8",
"from": "rimraf@>=2.2.8 <2.3.0",
"resolved": "https://registry.npmjs.org/rimraf/-/rimraf-2.2.8.tgz"
},
MDL-52127 js: check amd files with eslint grunt task I have spent quite a lot of time working through the current list of eslint options and configuring them for Moodle style and I think this is a very good basis to start us at (as well as taking some of out jshint options out with https://www.npmjs.com/package/polyjuice ). Thanks to Andrew Nicols, Mark Johnson and Frédéric Massart for some refinements. With this configuration the grunt build will fail if errors are present in the js (though you can of course tell jshint to ignore some errors, as I have done in admin/tool/lp/amd/src/competency_rule_points.js and defining the Y global in lib/amd/src/yui.js ). The grunt task will not report warnings by default, but a new --show-lint-warnings flag will help achieve that. Editor integrations/stanadalone eslint tool will surely be a better way of getting eslint errors rather than using the grunt task.
2016-05-11 10:19:30 +01:00
"run-async": {
"version": "0.1.0",
"from": "run-async@>=0.1.0 <0.2.0",
"resolved": "https://registry.npmjs.org/run-async/-/run-async-0.1.0.tgz"
},
"rx-lite": {
"version": "3.1.2",
"from": "rx-lite@>=3.1.2 <4.0.0",
"resolved": "https://registry.npmjs.org/rx-lite/-/rx-lite-3.1.2.tgz"
},
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"sax": {
"version": "0.5.8",
"from": "sax@>=0.5.0 <0.6.0",
"resolved": "https://registry.npmjs.org/sax/-/sax-0.5.8.tgz"
},
"semver": {
"version": "5.1.0",
"from": "semver@>=2.0.0 <3.0.0||>=3.0.0 <4.0.0||>=4.0.0 <5.0.0||>=5.0.0 <6.0.0",
"resolved": "https://registry.npmjs.org/semver/-/semver-5.1.0.tgz"
},
"shelljs": {
"version": "0.3.0",
"from": "shelljs@>=0.3.0 <0.4.0",
"resolved": "https://registry.npmjs.org/shelljs/-/shelljs-0.3.0.tgz"
},
"shifter": {
"version": "0.5.0",
"from": "shifter@0.5.0",
"resolved": "https://registry.npmjs.org/shifter/-/shifter-0.5.0.tgz",
"dependencies": {
"cli": {
"version": "0.4.3",
"from": "cli@0.4.3",
"resolved": "https://registry.npmjs.org/cli/-/cli-0.4.3.tgz"
MDL-52250 npm: shrinkwrap to lock down dependencies We've tried various approaches to lock down our dependencies and they have been flawed because dependencies in our included packages may not be locked down and previous attempts to do that have not been correct. With npm shrinkwrap we lock down versions so that any npm install will always install the exact same versions for all developers - see: https://docs.npmjs.com/cli/shrinkwrap (This is a lot like composer.lock for those more fluent with composer)
2015-12-03 17:00:50 +00:00
},
"jshint": {
"version": "0.9.1",
"from": "jshint@>=0.9.0 <0.10.0",
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"resolved": "https://registry.npmjs.org/jshint/-/jshint-0.9.1.tgz"
MDL-52250 npm: shrinkwrap to lock down dependencies We've tried various approaches to lock down our dependencies and they have been flawed because dependencies in our included packages may not be locked down and previous attempts to do that have not been correct. With npm shrinkwrap we lock down versions so that any npm install will always install the exact same versions for all developers - see: https://docs.npmjs.com/cli/shrinkwrap (This is a lot like composer.lock for those more fluent with composer)
2015-12-03 17:00:50 +00:00
},
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"lru-cache": {
"version": "1.0.6",
"from": "lru-cache@>=1.0.2 <1.1.0",
"resolved": "https://registry.npmjs.org/lru-cache/-/lru-cache-1.0.6.tgz"
MDL-52250 npm: shrinkwrap to lock down dependencies We've tried various approaches to lock down our dependencies and they have been flawed because dependencies in our included packages may not be locked down and previous attempts to do that have not been correct. With npm shrinkwrap we lock down versions so that any npm install will always install the exact same versions for all developers - see: https://docs.npmjs.com/cli/shrinkwrap (This is a lot like composer.lock for those more fluent with composer)
2015-12-03 17:00:50 +00:00
},
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"minimatch": {
"version": "0.0.5",
"from": "minimatch@>=0.0.0 <0.1.0",
"resolved": "https://registry.npmjs.org/minimatch/-/minimatch-0.0.5.tgz"
}
}
},
"sigmund": {
"version": "1.0.1",
"from": "sigmund@>=1.0.0 <1.1.0",
"resolved": "https://registry.npmjs.org/sigmund/-/sigmund-1.0.1.tgz"
},
"signal-exit": {
"version": "2.1.2",
"from": "signal-exit@>=2.1.2 <3.0.0",
"resolved": "https://registry.npmjs.org/signal-exit/-/signal-exit-2.1.2.tgz"
},
MDL-52127 js: check amd files with eslint grunt task I have spent quite a lot of time working through the current list of eslint options and configuring them for Moodle style and I think this is a very good basis to start us at (as well as taking some of out jshint options out with https://www.npmjs.com/package/polyjuice ). Thanks to Andrew Nicols, Mark Johnson and Frédéric Massart for some refinements. With this configuration the grunt build will fail if errors are present in the js (though you can of course tell jshint to ignore some errors, as I have done in admin/tool/lp/amd/src/competency_rule_points.js and defining the Y global in lib/amd/src/yui.js ). The grunt task will not report warnings by default, but a new --show-lint-warnings flag will help achieve that. Editor integrations/stanadalone eslint tool will surely be a better way of getting eslint errors rather than using the grunt task.
2016-05-11 10:19:30 +01:00
"slice-ansi": {
"version": "0.0.4",
"from": "slice-ansi@0.0.4",
"resolved": "https://registry.npmjs.org/slice-ansi/-/slice-ansi-0.0.4.tgz"
},
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"sntp": {
"version": "1.0.9",
"from": "sntp@>=1.0.0 <2.0.0",
"resolved": "https://registry.npmjs.org/sntp/-/sntp-1.0.9.tgz"
},
"source-map": {
"version": "0.4.4",
"from": "source-map@>=0.4.2 <0.5.0",
"resolved": "https://registry.npmjs.org/source-map/-/source-map-0.4.4.tgz"
},
"spdx-correct": {
"version": "1.0.2",
"from": "spdx-correct@>=1.0.0 <1.1.0",
"resolved": "https://registry.npmjs.org/spdx-correct/-/spdx-correct-1.0.2.tgz"
},
"spdx-exceptions": {
"version": "1.0.4",
"from": "spdx-exceptions@>=1.0.4 <2.0.0",
"resolved": "https://registry.npmjs.org/spdx-exceptions/-/spdx-exceptions-1.0.4.tgz"
},
"spdx-expression-parse": {
"version": "1.0.2",
"from": "spdx-expression-parse@>=1.0.0 <1.1.0",
"resolved": "https://registry.npmjs.org/spdx-expression-parse/-/spdx-expression-parse-1.0.2.tgz"
},
"spdx-license-ids": {
"version": "1.2.0",
"from": "spdx-license-ids@>=1.0.2 <2.0.0",
"resolved": "https://registry.npmjs.org/spdx-license-ids/-/spdx-license-ids-1.2.0.tgz"
},
MDL-52127 js: check amd files with eslint grunt task I have spent quite a lot of time working through the current list of eslint options and configuring them for Moodle style and I think this is a very good basis to start us at (as well as taking some of out jshint options out with https://www.npmjs.com/package/polyjuice ). Thanks to Andrew Nicols, Mark Johnson and Frédéric Massart for some refinements. With this configuration the grunt build will fail if errors are present in the js (though you can of course tell jshint to ignore some errors, as I have done in admin/tool/lp/amd/src/competency_rule_points.js and defining the Y global in lib/amd/src/yui.js ). The grunt task will not report warnings by default, but a new --show-lint-warnings flag will help achieve that. Editor integrations/stanadalone eslint tool will surely be a better way of getting eslint errors rather than using the grunt task.
2016-05-11 10:19:30 +01:00
"sprintf-js": {
"version": "1.0.3",
"from": "sprintf-js@>=1.0.2 <1.1.0",
"resolved": "https://registry.npmjs.org/sprintf-js/-/sprintf-js-1.0.3.tgz"
},
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"sshpk": {
"version": "1.7.3",
"from": "sshpk@>=1.7.0 <2.0.0",
"resolved": "https://registry.npmjs.org/sshpk/-/sshpk-1.7.3.tgz",
"dependencies": {
"assert-plus": {
"version": "0.2.0",
"from": "assert-plus@>=0.2.0 <0.3.0",
"resolved": "https://registry.npmjs.org/assert-plus/-/assert-plus-0.2.0.tgz"
}
}
},
"stream-counter": {
"version": "0.1.0",
"from": "stream-counter@>=0.1.0 <0.2.0",
"resolved": "https://registry.npmjs.org/stream-counter/-/stream-counter-0.1.0.tgz",
"dependencies": {
"readable-stream": {
"version": "1.0.33",
"from": "readable-stream@>=1.0.2 <1.1.0",
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-1.0.33.tgz"
}
}
},
"string_decoder": {
"version": "0.10.31",
"from": "string_decoder@>=0.10.0 <0.11.0",
"resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz"
},
MDL-52127 js: check amd files with eslint grunt task I have spent quite a lot of time working through the current list of eslint options and configuring them for Moodle style and I think this is a very good basis to start us at (as well as taking some of out jshint options out with https://www.npmjs.com/package/polyjuice ). Thanks to Andrew Nicols, Mark Johnson and Frédéric Massart for some refinements. With this configuration the grunt build will fail if errors are present in the js (though you can of course tell jshint to ignore some errors, as I have done in admin/tool/lp/amd/src/competency_rule_points.js and defining the Y global in lib/amd/src/yui.js ). The grunt task will not report warnings by default, but a new --show-lint-warnings flag will help achieve that. Editor integrations/stanadalone eslint tool will surely be a better way of getting eslint errors rather than using the grunt task.
2016-05-11 10:19:30 +01:00
"string-width": {
"version": "1.0.1",
"from": "string-width@>=1.0.1 <2.0.0",
"resolved": "https://registry.npmjs.org/string-width/-/string-width-1.0.1.tgz"
},
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"stringstream": {
"version": "0.0.5",
"from": "stringstream@>=0.0.4 <0.1.0",
"resolved": "https://registry.npmjs.org/stringstream/-/stringstream-0.0.5.tgz"
},
"strip-ansi": {
MDL-52127 js: check amd files with eslint grunt task I have spent quite a lot of time working through the current list of eslint options and configuring them for Moodle style and I think this is a very good basis to start us at (as well as taking some of out jshint options out with https://www.npmjs.com/package/polyjuice ). Thanks to Andrew Nicols, Mark Johnson and Frédéric Massart for some refinements. With this configuration the grunt build will fail if errors are present in the js (though you can of course tell jshint to ignore some errors, as I have done in admin/tool/lp/amd/src/competency_rule_points.js and defining the Y global in lib/amd/src/yui.js ). The grunt task will not report warnings by default, but a new --show-lint-warnings flag will help achieve that. Editor integrations/stanadalone eslint tool will surely be a better way of getting eslint errors rather than using the grunt task.
2016-05-11 10:19:30 +01:00
"version": "3.0.1",
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"from": "strip-ansi@>=3.0.0 <4.0.0",
MDL-52127 js: check amd files with eslint grunt task I have spent quite a lot of time working through the current list of eslint options and configuring them for Moodle style and I think this is a very good basis to start us at (as well as taking some of out jshint options out with https://www.npmjs.com/package/polyjuice ). Thanks to Andrew Nicols, Mark Johnson and Frédéric Massart for some refinements. With this configuration the grunt build will fail if errors are present in the js (though you can of course tell jshint to ignore some errors, as I have done in admin/tool/lp/amd/src/competency_rule_points.js and defining the Y global in lib/amd/src/yui.js ). The grunt task will not report warnings by default, but a new --show-lint-warnings flag will help achieve that. Editor integrations/stanadalone eslint tool will surely be a better way of getting eslint errors rather than using the grunt task.
2016-05-11 10:19:30 +01:00
"resolved": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-3.0.1.tgz"
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
},
"strip-bom": {
"version": "2.0.0",
"from": "strip-bom@>=2.0.0 <3.0.0",
"resolved": "https://registry.npmjs.org/strip-bom/-/strip-bom-2.0.0.tgz"
},
"strip-indent": {
"version": "1.0.1",
"from": "strip-indent@>=1.0.1 <2.0.0",
"resolved": "https://registry.npmjs.org/strip-indent/-/strip-indent-1.0.1.tgz"
},
"strip-json-comments": {
"version": "1.0.4",
"from": "strip-json-comments@>=1.0.0 <1.1.0",
"resolved": "https://registry.npmjs.org/strip-json-comments/-/strip-json-comments-1.0.4.tgz"
},
"supports-color": {
"version": "2.0.0",
"from": "supports-color@>=2.0.0 <3.0.0",
"resolved": "https://registry.npmjs.org/supports-color/-/supports-color-2.0.0.tgz"
},
MDL-52127 js: check amd files with eslint grunt task I have spent quite a lot of time working through the current list of eslint options and configuring them for Moodle style and I think this is a very good basis to start us at (as well as taking some of out jshint options out with https://www.npmjs.com/package/polyjuice ). Thanks to Andrew Nicols, Mark Johnson and Frédéric Massart for some refinements. With this configuration the grunt build will fail if errors are present in the js (though you can of course tell jshint to ignore some errors, as I have done in admin/tool/lp/amd/src/competency_rule_points.js and defining the Y global in lib/amd/src/yui.js ). The grunt task will not report warnings by default, but a new --show-lint-warnings flag will help achieve that. Editor integrations/stanadalone eslint tool will surely be a better way of getting eslint errors rather than using the grunt task.
2016-05-11 10:19:30 +01:00
"table": {
"version": "3.7.8",
"from": "table@>=3.7.8 <4.0.0",
"resolved": "https://registry.npmjs.org/table/-/table-3.7.8.tgz",
"dependencies": {
"lodash": {
"version": "4.13.1",
MDL-54889 jshint: stop using for everything but shifter Now jshint has been replaced by eslint.
2016-06-28 10:41:18 +01:00
"from": "lodash@>=4.0.0 <5.0.0",
"resolved": "https://registry.npmjs.org/lodash/-/lodash-4.13.1.tgz"
MDL-52127 js: check amd files with eslint grunt task I have spent quite a lot of time working through the current list of eslint options and configuring them for Moodle style and I think this is a very good basis to start us at (as well as taking some of out jshint options out with https://www.npmjs.com/package/polyjuice ). Thanks to Andrew Nicols, Mark Johnson and Frédéric Massart for some refinements. With this configuration the grunt build will fail if errors are present in the js (though you can of course tell jshint to ignore some errors, as I have done in admin/tool/lp/amd/src/competency_rule_points.js and defining the Y global in lib/amd/src/yui.js ). The grunt task will not report warnings by default, but a new --show-lint-warnings flag will help achieve that. Editor integrations/stanadalone eslint tool will surely be a better way of getting eslint errors rather than using the grunt task.
2016-05-11 10:19:30 +01:00
}
}
},
"text-table": {
"version": "0.2.0",
"from": "text-table@>=0.2.0 <0.3.0",
"resolved": "https://registry.npmjs.org/text-table/-/text-table-0.2.0.tgz"
},
"through": {
"version": "2.3.8",
"from": "through@>=2.3.6 <3.0.0",
"resolved": "https://registry.npmjs.org/through/-/through-2.3.8.tgz"
},
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"timethat": {
"version": "0.0.3",
"from": "timethat@>=0.0.1 <0.1.0",
"resolved": "https://registry.npmjs.org/timethat/-/timethat-0.0.3.tgz"
},
"tiny-lr-fork": {
"version": "0.0.5",
"from": "tiny-lr-fork@0.0.5",
"resolved": "https://registry.npmjs.org/tiny-lr-fork/-/tiny-lr-fork-0.0.5.tgz",
"dependencies": {
"qs": {
"version": "0.5.6",
"from": "qs@>=0.5.2 <0.6.0",
"resolved": "https://registry.npmjs.org/qs/-/qs-0.5.6.tgz"
}
}
},
"tough-cookie": {
"version": "2.2.1",
"from": "tough-cookie@>=2.2.0 <2.3.0",
"resolved": "https://registry.npmjs.org/tough-cookie/-/tough-cookie-2.2.1.tgz"
},
"trim-newlines": {
"version": "1.0.0",
"from": "trim-newlines@>=1.0.0 <2.0.0",
"resolved": "https://registry.npmjs.org/trim-newlines/-/trim-newlines-1.0.0.tgz"
},
MDL-52127 js: check amd files with eslint grunt task I have spent quite a lot of time working through the current list of eslint options and configuring them for Moodle style and I think this is a very good basis to start us at (as well as taking some of out jshint options out with https://www.npmjs.com/package/polyjuice ). Thanks to Andrew Nicols, Mark Johnson and Frédéric Massart for some refinements. With this configuration the grunt build will fail if errors are present in the js (though you can of course tell jshint to ignore some errors, as I have done in admin/tool/lp/amd/src/competency_rule_points.js and defining the Y global in lib/amd/src/yui.js ). The grunt task will not report warnings by default, but a new --show-lint-warnings flag will help achieve that. Editor integrations/stanadalone eslint tool will surely be a better way of getting eslint errors rather than using the grunt task.
2016-05-11 10:19:30 +01:00
"tryit": {
"version": "1.0.2",
"from": "tryit@>=1.0.1 <2.0.0",
"resolved": "https://registry.npmjs.org/tryit/-/tryit-1.0.2.tgz"
},
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"tunnel-agent": {
"version": "0.4.2",
"from": "tunnel-agent@>=0.4.1 <0.5.0",
"resolved": "https://registry.npmjs.org/tunnel-agent/-/tunnel-agent-0.4.2.tgz"
},
MDL-52127 js: check amd files with eslint grunt task I have spent quite a lot of time working through the current list of eslint options and configuring them for Moodle style and I think this is a very good basis to start us at (as well as taking some of out jshint options out with https://www.npmjs.com/package/polyjuice ). Thanks to Andrew Nicols, Mark Johnson and Frédéric Massart for some refinements. With this configuration the grunt build will fail if errors are present in the js (though you can of course tell jshint to ignore some errors, as I have done in admin/tool/lp/amd/src/competency_rule_points.js and defining the Y global in lib/amd/src/yui.js ). The grunt task will not report warnings by default, but a new --show-lint-warnings flag will help achieve that. Editor integrations/stanadalone eslint tool will surely be a better way of getting eslint errors rather than using the grunt task.
2016-05-11 10:19:30 +01:00
"tv4": {
"version": "1.2.7",
"from": "tv4@>=1.2.7 <2.0.0",
"resolved": "https://registry.npmjs.org/tv4/-/tv4-1.2.7.tgz"
},
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"tweetnacl": {
"version": "0.13.3",
"from": "tweetnacl@>=0.13.0 <1.0.0",
"resolved": "https://registry.npmjs.org/tweetnacl/-/tweetnacl-0.13.3.tgz"
},
MDL-52127 js: check amd files with eslint grunt task I have spent quite a lot of time working through the current list of eslint options and configuring them for Moodle style and I think this is a very good basis to start us at (as well as taking some of out jshint options out with https://www.npmjs.com/package/polyjuice ). Thanks to Andrew Nicols, Mark Johnson and Frédéric Massart for some refinements. With this configuration the grunt build will fail if errors are present in the js (though you can of course tell jshint to ignore some errors, as I have done in admin/tool/lp/amd/src/competency_rule_points.js and defining the Y global in lib/amd/src/yui.js ). The grunt task will not report warnings by default, but a new --show-lint-warnings flag will help achieve that. Editor integrations/stanadalone eslint tool will surely be a better way of getting eslint errors rather than using the grunt task.
2016-05-11 10:19:30 +01:00
"type-check": {
"version": "0.3.2",
"from": "type-check@>=0.3.2 <0.4.0",
"resolved": "https://registry.npmjs.org/type-check/-/type-check-0.3.2.tgz"
},
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"typedarray": {
"version": "0.0.6",
"from": "typedarray@>=0.0.5 <0.1.0",
"resolved": "https://registry.npmjs.org/typedarray/-/typedarray-0.0.6.tgz"
},
"uglify-js": {
"version": "2.6.1",
"from": "uglify-js@>=2.6.0 <2.7.0",
"resolved": "https://registry.npmjs.org/uglify-js/-/uglify-js-2.6.1.tgz",
"dependencies": {
"async": {
"version": "0.2.10",
"from": "async@>=0.2.6 <0.3.0",
"resolved": "https://registry.npmjs.org/async/-/async-0.2.10.tgz"
MDL-52250 npm: shrinkwrap to lock down dependencies We've tried various approaches to lock down our dependencies and they have been flawed because dependencies in our included packages may not be locked down and previous attempts to do that have not been correct. With npm shrinkwrap we lock down versions so that any npm install will always install the exact same versions for all developers - see: https://docs.npmjs.com/cli/shrinkwrap (This is a lot like composer.lock for those more fluent with composer)
2015-12-03 17:00:50 +00:00
},
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"source-map": {
"version": "0.5.3",
"from": "source-map@>=0.5.1 <0.6.0",
"resolved": "https://registry.npmjs.org/source-map/-/source-map-0.5.3.tgz"
}
}
},
"uglify-to-browserify": {
"version": "1.0.2",
"from": "uglify-to-browserify@>=1.0.0 <1.1.0",
"resolved": "https://registry.npmjs.org/uglify-to-browserify/-/uglify-to-browserify-1.0.2.tgz"
},
"underscore": {
"version": "1.7.0",
"from": "underscore@>=1.7.0 <1.8.0",
"resolved": "https://registry.npmjs.org/underscore/-/underscore-1.7.0.tgz"
},
"underscore.string": {
"version": "2.2.1",
"from": "underscore.string@>=2.2.1 <2.3.0",
"resolved": "https://registry.npmjs.org/underscore.string/-/underscore.string-2.2.1.tgz"
},
"uri-path": {
"version": "1.0.0",
"from": "uri-path@>=1.0.0 <2.0.0",
"resolved": "https://registry.npmjs.org/uri-path/-/uri-path-1.0.0.tgz"
},
MDL-52127 js: check amd files with eslint grunt task I have spent quite a lot of time working through the current list of eslint options and configuring them for Moodle style and I think this is a very good basis to start us at (as well as taking some of out jshint options out with https://www.npmjs.com/package/polyjuice ). Thanks to Andrew Nicols, Mark Johnson and Frédéric Massart for some refinements. With this configuration the grunt build will fail if errors are present in the js (though you can of course tell jshint to ignore some errors, as I have done in admin/tool/lp/amd/src/competency_rule_points.js and defining the Y global in lib/amd/src/yui.js ). The grunt task will not report warnings by default, but a new --show-lint-warnings flag will help achieve that. Editor integrations/stanadalone eslint tool will surely be a better way of getting eslint errors rather than using the grunt task.
2016-05-11 10:19:30 +01:00
"user-home": {
"version": "2.0.0",
"from": "user-home@>=2.0.0 <3.0.0",
"resolved": "https://registry.npmjs.org/user-home/-/user-home-2.0.0.tgz"
},
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"util-deprecate": {
"version": "1.0.2",
"from": "util-deprecate@>=1.0.1 <1.1.0",
"resolved": "https://registry.npmjs.org/util-deprecate/-/util-deprecate-1.0.2.tgz"
},
"validate-npm-package-license": {
"version": "3.0.1",
"from": "validate-npm-package-license@>=3.0.1 <4.0.0",
"resolved": "https://registry.npmjs.org/validate-npm-package-license/-/validate-npm-package-license-3.0.1.tgz"
},
"verror": {
"version": "1.3.6",
"from": "verror@1.3.6",
"resolved": "https://registry.npmjs.org/verror/-/verror-1.3.6.tgz"
},
"walkdir": {
"version": "0.0.11",
"from": "walkdir@>=0.0.5 <0.1.0",
"resolved": "https://registry.npmjs.org/walkdir/-/walkdir-0.0.11.tgz"
},
"watch": {
"version": "0.8.0",
"from": "watch@>=0.8.0 <0.9.0",
"resolved": "https://registry.npmjs.org/watch/-/watch-0.8.0.tgz"
},
"which": {
"version": "1.0.9",
"from": "which@>=1.0.5 <1.1.0",
"resolved": "https://registry.npmjs.org/which/-/which-1.0.9.tgz"
},
"window-size": {
"version": "0.1.0",
"from": "window-size@0.1.0",
"resolved": "https://registry.npmjs.org/window-size/-/window-size-0.1.0.tgz"
},
"wordwrap": {
"version": "0.0.2",
"from": "wordwrap@0.0.2",
"resolved": "https://registry.npmjs.org/wordwrap/-/wordwrap-0.0.2.tgz"
},
MDL-52127 js: check amd files with eslint grunt task I have spent quite a lot of time working through the current list of eslint options and configuring them for Moodle style and I think this is a very good basis to start us at (as well as taking some of out jshint options out with https://www.npmjs.com/package/polyjuice ). Thanks to Andrew Nicols, Mark Johnson and Frédéric Massart for some refinements. With this configuration the grunt build will fail if errors are present in the js (though you can of course tell jshint to ignore some errors, as I have done in admin/tool/lp/amd/src/competency_rule_points.js and defining the Y global in lib/amd/src/yui.js ). The grunt task will not report warnings by default, but a new --show-lint-warnings flag will help achieve that. Editor integrations/stanadalone eslint tool will surely be a better way of getting eslint errors rather than using the grunt task.
2016-05-11 10:19:30 +01:00
"wrappy": {
"version": "1.0.2",
"from": "wrappy@>=1.0.0 <2.0.0",
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.2.tgz"
},
"write": {
"version": "0.2.1",
"from": "write@>=0.2.1 <0.3.0",
"resolved": "https://registry.npmjs.org/write/-/write-0.2.1.tgz"
},
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"xml2js": {
"version": "0.2.8",
"from": "xml2js@>=0.2.0 <0.3.0",
"resolved": "https://registry.npmjs.org/xml2js/-/xml2js-0.2.8.tgz"
},
MDL-52127 grunt: be aware of third party paths 1) Parse thirdpartylibs.xml and generate an array of third party file paths to use in grunt tasks 2) In the lint tasks, we filter third party files from being linted 3) We add a new task to generate ignore files - currently for eslint, but will be potentially useful for other things in the future 4) Remove .eslintignore from source control Why have the ability to generate a .eslintignore file? For tooling integration - by having the eslintignore file people can use other eslint tools without having to just use grunt (e.g. editor integrations).
2016-05-13 21:20:21 +01:00
"xmldom": {
"version": "0.1.22",
"from": "xmldom@latest",
"resolved": "https://registry.npmjs.org/xmldom/-/xmldom-0.1.22.tgz"
},
"xpath": {
"version": "0.0.23",
"from": "xpath@latest",
"resolved": "https://registry.npmjs.org/xpath/-/xpath-0.0.23.tgz"
},
MDL-52127 js: check amd files with eslint grunt task I have spent quite a lot of time working through the current list of eslint options and configuring them for Moodle style and I think this is a very good basis to start us at (as well as taking some of out jshint options out with https://www.npmjs.com/package/polyjuice ). Thanks to Andrew Nicols, Mark Johnson and Frédéric Massart for some refinements. With this configuration the grunt build will fail if errors are present in the js (though you can of course tell jshint to ignore some errors, as I have done in admin/tool/lp/amd/src/competency_rule_points.js and defining the Y global in lib/amd/src/yui.js ). The grunt task will not report warnings by default, but a new --show-lint-warnings flag will help achieve that. Editor integrations/stanadalone eslint tool will surely be a better way of getting eslint errors rather than using the grunt task.
2016-05-11 10:19:30 +01:00
"xregexp": {
"version": "3.1.1",
"from": "xregexp@>=3.0.0 <4.0.0",
"resolved": "https://registry.npmjs.org/xregexp/-/xregexp-3.1.1.tgz"
},
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"xtend": {
"version": "4.0.1",
"from": "xtend@>=4.0.0 <5.0.0",
"resolved": "https://registry.npmjs.org/xtend/-/xtend-4.0.1.tgz"
},
"yargs": {
"version": "3.10.0",
"from": "yargs@>=3.10.0 <3.11.0",
"resolved": "https://registry.npmjs.org/yargs/-/yargs-3.10.0.tgz",
"dependencies": {
"camelcase": {
"version": "1.2.1",
"from": "camelcase@>=1.0.2 <2.0.0",
"resolved": "https://registry.npmjs.org/camelcase/-/camelcase-1.2.1.tgz"
}
}
},
"ycssmin": {
"version": "1.0.1",
"from": "ycssmin@>=1.0.1",
"resolved": "https://registry.npmjs.org/ycssmin/-/ycssmin-1.0.1.tgz"
},
"yuglify": {
"version": "0.1.4",
"from": "yuglify@>=0.1.0 <0.2.0",
"resolved": "https://registry.npmjs.org/yuglify/-/yuglify-0.1.4.tgz",
"dependencies": {
"nopt": {
"version": "2.1.2",
"from": "nopt@>=2.1.1 <2.2.0",
"resolved": "https://registry.npmjs.org/nopt/-/nopt-2.1.2.tgz"
MDL-52250 npm: shrinkwrap to lock down dependencies We've tried various approaches to lock down our dependencies and they have been flawed because dependencies in our included packages may not be locked down and previous attempts to do that have not been correct. With npm shrinkwrap we lock down versions so that any npm install will always install the exact same versions for all developers - see: https://docs.npmjs.com/cli/shrinkwrap (This is a lot like composer.lock for those more fluent with composer)
2015-12-03 17:00:50 +00:00
},
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
"uglify-js": {
"version": "1.3.5",
"from": "uglify-js@>=1.3.4 <1.4.0",
"resolved": "https://registry.npmjs.org/uglify-js/-/uglify-js-1.3.5.tgz"
MDL-52250 npm: shrinkwrap to lock down dependencies We've tried various approaches to lock down our dependencies and they have been flawed because dependencies in our included packages may not be locked down and previous attempts to do that have not been correct. With npm shrinkwrap we lock down versions so that any npm install will always install the exact same versions for all developers - see: https://docs.npmjs.com/cli/shrinkwrap (This is a lot like composer.lock for those more fluent with composer)
2015-12-03 17:00:50 +00:00
}
}
MDL-49817 grunt: add watch task This allows files to be watched and automatically build when changed. Thanks to David Monllaó for the initial basis for this patch.
2016-01-14 13:22:28 +00:00
},
"yui-lint": {
"version": "0.2.0",
"from": "yui-lint@>=0.2.0 <0.3.0",
"resolved": "https://registry.npmjs.org/yui-lint/-/yui-lint-0.2.0.tgz"
},
"yuicompressor": {
"version": "2.4.7",
"from": "yuicompressor@2.4.7",
"resolved": "https://registry.npmjs.org/yuicompressor/-/yuicompressor-2.4.7.tgz"
},
"yuitest-coverage": {
"version": "0.0.6",
"from": "yuitest-coverage@>=0.0.5",
"resolved": "https://registry.npmjs.org/yuitest-coverage/-/yuitest-coverage-0.0.6.tgz"
MDL-52250 npm: shrinkwrap to lock down dependencies We've tried various approaches to lock down our dependencies and they have been flawed because dependencies in our included packages may not be locked down and previous attempts to do that have not been correct. With npm shrinkwrap we lock down versions so that any npm install will always install the exact same versions for all developers - see: https://docs.npmjs.com/cli/shrinkwrap (This is a lot like composer.lock for those more fluent with composer)
2015-12-03 17:00:50 +00:00
}
}
}
Reference in New Issue Copy Permalink