mirror_php/moodle
1
0
Fork 0
mirror of https://github.com/moodle/moodle.git synced 2025-01-18 05:58:34 +01:00
Code Issues Projects Releases Wiki Activity
moodle/package.json

28 lines
646 B
JSON
Raw Normal View History

MDL-49046 javascript: Add support for AMD modules and jquery. Grunt is the build tool.
2015-02-22 14:50:20 +08:00
{
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
"name": "Moodle",
"private": true,
"description": "Moodle",
"devDependencies": {
MDL-55048 grunt/npm: Update dependencies * We bump our minimum node version up to >=4. Although this isn't yet necessarily *required* it was spurred on because grunt dropped support for very early node versions and so it's likely some devs will have to upgrade their npm. We do it now which gives us more flexibility for tools going forward (especially for things like new theme/testing). And node has matured the ecosystem (especially supporting properly semver) so should result in less edge cases. * We make the minimum node version explicit in package.json. Though it doesn't help much for older versions of node because npm doesn't have the functionality to warn about it.. ;-) * Left async dependency as it was, because it's only on an RC: 2.0.0-rc.6
2016-06-28 17:45:11 +01:00
"async": "1.5.2",
MDL-59761 eslint: update to v4.6.1 The new versions got released while this issue was waiting for peer review.
2017-09-12 09:23:46 +01:00
"eslint": "4.6.1",
MDL-57139 eslint: enable eslint-plugin-promise rules For promise best practices
2016-12-16 10:13:25 +00:00
"eslint-plugin-promise": "3.5.0",
MDL-56519 behat: Lint gherkin files
2016-10-20 10:53:05 +01:00
"gherkin-lint": "1.1.3",
MDL-55048 grunt/npm: Update dependencies * We bump our minimum node version up to >=4. Although this isn't yet necessarily *required* it was spurred on because grunt dropped support for very early node versions and so it's likely some devs will have to upgrade their npm. We do it now which gives us more flexibility for tools going forward (especially for things like new theme/testing). And node has matured the ecosystem (especially supporting properly semver) so should result in less edge cases. * We make the minimum node version explicit in package.json. Though it doesn't help much for older versions of node because npm doesn't have the functionality to warn about it.. ;-) * Left async dependency as it was, because it's only on an RC: 2.0.0-rc.6
2016-06-28 17:45:11 +01:00
"grunt": "1.0.1",
"grunt-contrib-uglify": "1.0.1",
"grunt-contrib-watch": "1.0.0",
MDL-59761 eslint: update to v4.6.1 The new versions got released while this issue was waiting for peer review.
2017-09-12 09:23:46 +01:00
"grunt-eslint": "20.1.0",
MDL-59261 theme_boost: compiled css fallback
2018-06-21 17:56:30 +02:00
"grunt-sass": "2.1.0",
MDL-55167 grunt: add stylelint css linting
2016-07-05 15:56:53 +01:00
"grunt-stylelint": "0.6.0",
MDL-55856 grunt: fail gracefully when node version too old Unfortunately the engine requirement in packages.json is not a fatal error, so you can get unhelpful errors with grunt if using an unsupported version.
2016-09-05 14:54:01 +01:00
"semver": "5.3.0",
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
"shifter": "0.5.0",
MDL-57945 stylelint: Upgrade 7.12.0 This stylelint is consolodating and focusing the project so there are some rule deprecations without real alternatives yet.
2017-07-19 13:45:47 +01:00
"stylelint": "8.0.0",
MDL-55167 npm: add stylelint-checkstyle-formatter Useful for automations (like the Moodle prechecker)
2016-08-02 18:52:41 +01:00
"stylelint-checkstyle-formatter": "0.1.0",
MDL-57945 stylelint: use csstree to replace some rules Ironically we have to reverse the change from e63d89a5 because this linter is more clever..
2017-07-19 13:57:07 +01:00
"stylelint-csstree-validator": "1.1.1",
MDL-55048 grunt/npm: Update dependencies * We bump our minimum node version up to >=4. Although this isn't yet necessarily *required* it was spurred on because grunt dropped support for very early node versions and so it's likely some devs will have to upgrade their npm. We do it now which gives us more flexibility for tools going forward (especially for things like new theme/testing). And node has matured the ecosystem (especially supporting properly semver) so should result in less edge cases. * We make the minimum node version explicit in package.json. Though it doesn't help much for older versions of node because npm doesn't have the functionality to warn about it.. ;-) * Left async dependency as it was, because it's only on an RC: 2.0.0-rc.6
2016-06-28 17:45:11 +01:00
"xmldom": "0.1.22",
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
"xpath": "0.0.23"
MDL-55048 grunt/npm: Update dependencies * We bump our minimum node version up to >=4. Although this isn't yet necessarily *required* it was spurred on because grunt dropped support for very early node versions and so it's likely some devs will have to upgrade their npm. We do it now which gives us more flexibility for tools going forward (especially for things like new theme/testing). And node has matured the ecosystem (especially supporting properly semver) so should result in less edge cases. * We make the minimum node version explicit in package.json. Though it doesn't help much for older versions of node because npm doesn't have the functionality to warn about it.. ;-) * Left async dependency as it was, because it's only on an RC: 2.0.0-rc.6
2016-06-28 17:45:11 +01:00
},
"engines": {
MDL-61893 JavaScript: Accept any node version but Carbon (LTS)
2018-05-04 00:18:25 +02:00
"node": ">=8.9 <9"
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-49046 javascript: Add support for AMD modules and jquery. Grunt is the build tool.
2015-02-22 14:50:20 +08:00
}
Reference in New Issue Copy Permalink