ylqjgm
/
canvas-lms
mirror of https://github.com/instructure/canvas-lms.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
canvas-lms/package.json

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

480 lines
18 KiB
JSON
Raw Normal View History

AMD Conversion "Trivial" JavaScript / CoffeeScript changes -------------------------------------------------- For the most part, all javascript was simply wrapped in `require` or `define`. The dependencies were found with a script that matched regexes in the files, it errs on the side of listing too many dependencies, so its worth double checking each file's dependencies (over time, anyway). i18n API changes -------------------------------------------------- No longer have to do I18n.scoped calls, just list i18n as a dependency with the scope and it's imported already scoped require ['i18n!some_scope'], (I18n) -> I18n.t 'im_scoped', 'I'm scoped!' JS bundling now done with r.js, not Jammit -------------------------------------------------- We don't use jammit to bundle JS anymore. Simply list dependencies for your JS modules in the file and RequireJS handles the rest. To optimize the JavaScript, first make sure you have node.js 0.4.12+ installed and then run: $ rake js:build The app defaults to the optimized build in production. You can use non-optimized in production by putting ?debug_assets=true in the url just like before. You can also test the optimized JavaScript in development with ?optimized_js=true. Significant changes -------------------------------------------------- These files have "real" changes to them (unlike the JavaScript that is simply wrapped in require and define). Worth taking a really close look at: - app/helpers/application_helper.rb - app/views/layouts/application.html.erb - config/assets.yml - config/build.js - lib/handlebars/handlebars.rb - lib/i18n_extraction/js_extractor.rb - lib/tasks/canvas.rake - lib/tasks/i18n.rake - lib/tasks/js.rake Change-Id: I4bc5ecb1231f331aaded0fef2bcc1f3a9fe482a7 Reviewed-on: https://gerrit.instructure.com/6986 Tested-by: Hudson <hudson@instructure.com> Reviewed-by: Ryan Florence <ryanf@instructure.com>
2011-11-11 00:31:45 +08:00
{
"name": "canvas-lms",
upgrade karma everyone was getting build errors when they were npm install'ing. it was because karma 0.10 depended on an out-of-date version of chokiadr that does not compile against node 0.12 I also indicated that canvas is licenced agpl 3 so that you wouldn't always see an npm warning about not having one. also, let karma serve our css files so if any javascript references them in our quit tests, we don't see 404 warnings Change-Id: Iaa0377bc87b8f7ec8726d6cb82c0f8a103134b56 Reviewed-on: https://gerrit.instructure.com/58584 Tested-by: Jenkins Reviewed-by: Mike Nomitch <mnomitch@instructure.com> Reviewed-by: Clay Diffrient <cdiffrient@instructure.com> Product-Review: Ryan Shaw <ryan@instructure.com> QA-Review: Ryan Shaw <ryan@instructure.com>
2015-07-16 12:24:49 +08:00
"license": "AGPL-3.0",
AMD Conversion "Trivial" JavaScript / CoffeeScript changes -------------------------------------------------- For the most part, all javascript was simply wrapped in `require` or `define`. The dependencies were found with a script that matched regexes in the files, it errs on the side of listing too many dependencies, so its worth double checking each file's dependencies (over time, anyway). i18n API changes -------------------------------------------------- No longer have to do I18n.scoped calls, just list i18n as a dependency with the scope and it's imported already scoped require ['i18n!some_scope'], (I18n) -> I18n.t 'im_scoped', 'I'm scoped!' JS bundling now done with r.js, not Jammit -------------------------------------------------- We don't use jammit to bundle JS anymore. Simply list dependencies for your JS modules in the file and RequireJS handles the rest. To optimize the JavaScript, first make sure you have node.js 0.4.12+ installed and then run: $ rake js:build The app defaults to the optimized build in production. You can use non-optimized in production by putting ?debug_assets=true in the url just like before. You can also test the optimized JavaScript in development with ?optimized_js=true. Significant changes -------------------------------------------------- These files have "real" changes to them (unlike the JavaScript that is simply wrapped in require and define). Worth taking a really close look at: - app/helpers/application_helper.rb - app/views/layouts/application.html.erb - config/assets.yml - config/build.js - lib/handlebars/handlebars.rb - lib/i18n_extraction/js_extractor.rb - lib/tasks/canvas.rake - lib/tasks/i18n.rake - lib/tasks/js.rake Change-Id: I4bc5ecb1231f331aaded0fef2bcc1f3a9fe482a7 Reviewed-on: https://gerrit.instructure.com/6986 Tested-by: Hudson <hudson@instructure.com> Reviewed-by: Ryan Florence <ryanf@instructure.com>
2011-11-11 00:31:45 +08:00
"version": "0.0.0",
upgrade karma everyone was getting build errors when they were npm install'ing. it was because karma 0.10 depended on an out-of-date version of chokiadr that does not compile against node 0.12 I also indicated that canvas is licenced agpl 3 so that you wouldn't always see an npm warning about not having one. also, let karma serve our css files so if any javascript references them in our quit tests, we don't see 404 warnings Change-Id: Iaa0377bc87b8f7ec8726d6cb82c0f8a103134b56 Reviewed-on: https://gerrit.instructure.com/58584 Tested-by: Jenkins Reviewed-by: Mike Nomitch <mnomitch@instructure.com> Reviewed-by: Clay Diffrient <cdiffrient@instructure.com> Product-Review: Ryan Shaw <ryan@instructure.com> QA-Review: Ryan Shaw <ryan@instructure.com>
2015-07-16 12:24:49 +08:00
"engines": {
Update node requirement in package.json refs AE-485 flag = none Change-Id: I823a6a7c0913b94e928c546d4cec6c944d0e2506 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/329641 Reviewed-by: Jacob Burroughs <jburroughs@instructure.com> Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> QA-Review: Jackson Howe <jackson.howe@instructure.com> Product-Review: Jackson Howe <jackson.howe@instructure.com>
2023-10-07 00:18:37 +08:00
"node": ">=18.0.0",
[node12] bump "engines" in package.json refs FOO-1116 flag = none test plan: we can install `yarn install` Change-Id: I0e78958130368a11eb007d1ffddbd075f27d9380 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/254937 Reviewed-by: Jacob Burroughs <jburroughs@instructure.com> Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> QA-Review: Ahmad Amireh <ahmad@instructure.com> Product-Review: Ahmad Amireh <ahmad@instructure.com>
2020-12-12 01:32:26 +08:00
"yarn": "^1.19.1"
upgrade karma everyone was getting build errors when they were npm install'ing. it was because karma 0.10 depended on an out-of-date version of chokiadr that does not compile against node 0.12 I also indicated that canvas is licenced agpl 3 so that you wouldn't always see an npm warning about not having one. also, let karma serve our css files so if any javascript references them in our quit tests, we don't see 404 warnings Change-Id: Iaa0377bc87b8f7ec8726d6cb82c0f8a103134b56 Reviewed-on: https://gerrit.instructure.com/58584 Tested-by: Jenkins Reviewed-by: Mike Nomitch <mnomitch@instructure.com> Reviewed-by: Clay Diffrient <cdiffrient@instructure.com> Product-Review: Ryan Shaw <ryan@instructure.com> QA-Review: Ryan Shaw <ryan@instructure.com>
2015-07-16 12:24:49 +08:00
},
Use yarn workspaces Run `script/nuke_node.sh` to clean everything up Run `yarn install` it should install everything for everything Run `yarn build` and `yarn test` they should work exactly as before Change-Id: I11a27ff2d705c6cbb3b3f9029dd8b32138706146 Reviewed-on: https://gerrit.instructure.com/151356 Tested-by: Jenkins Reviewed-by: Brent Burgoyne <bburgoyne@instructure.com> Product-Review: Ryan Shaw <ryan@instructure.com> QA-Review: Ryan Shaw <ryan@instructure.com>
2018-05-25 00:09:03 +08:00
"private": true,
"workspaces": {
"packages": [
treat anything in gems/plugins/* as a workspace Fixes: https://github.com/instructure/canvas-lms/issues/1323 This lets open source users continue putting their own plugins with npm deps In gems/plugins. They will still have to have a forked version Of yarn.lock though since that will be different for them than a “Default” install. Also, this means that everyone will see a bunch of warnings like this Every time they yarn install: Warning: gems/plugins/academic_benchmark is a dir… no package.json Warning: gems/plugins/account_reports is a dir.. has no package.json Warning: gems/plugins/canvas_geoip is a …, but has no package.json Warning: gems/plugins/demo_site is a directory, but has no package.json Warning: gems/plugins/instructure_misc_plugin is … has no package.json Warning: gems/plugins/moodle_importer is a d.., but has no package.json Warning: gems/plugins/qti_exporter is a dir…, but has no package.json Warning: gems/plugins/respondus_soap_endpoint is … no package.json Warning: gems/plugins/simply_versioned is a …, but has no package.json Test plan: * yarn install should work Change-Id: Ie65c8faf8b1022210cfb7eda8c25107facfe83b5 Reviewed-on: https://gerrit.instructure.com/158043 Tested-by: Jenkins Reviewed-by: Clay Diffrient <cdiffrient@instructure.com> Product-Review: Ryan Shaw <ryan@instructure.com> QA-Review: Ryan Shaw <ryan@instructure.com>
2018-07-20 03:42:35 +08:00
"gems/plugins/*",
(webpack) unify tinymce installation refs FOO-2835 flag = none hoist tinymce to the top since we're using the same version as the RCE, this way we don't end up with 2 separate installations that strange CSS require() call has to be relative for a reason i don't have neither time nor desire to unravel there was a discrepancy in the noParse directive between our webpack config in test and outside of test: the test one was excluding the entirety of tinymce, which is fine for the main tinymce module but not so for the "icons" one that the rce package depends on. This was working OK because the test config was ignoring the top-level tinymce icons module, which is never required, but now that it's getting required, it fell apart. I kept to the non-test version where we exclude only the main module "tinymce.js", as there's no value beyond that. ~ test plan ~ the RCE still works (e.g. in assignment edit page) and looks OK Change-Id: I664930753189d8f3966ddec0d0340ba100af6ab3 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/294132 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Charley Kline <ckline@instructure.com> QA-Review: Charley Kline <ckline@instructure.com> Product-Review: Charley Kline <ckline@instructure.com>
2022-06-17 13:31:09 +08:00
"packages/*",
Proof of concept for new Canvas engine Refs FOO-2929 flag=none The replaces some of the functionality performed in the ui/index.js entrypoint with the new "engine" which will eventually hold all the startup helpers for standalone entrypoints (that don't boot via ui/index.js). For starters, we've done the loading of the translation file, the backfill of ENV.LOCALE from the ENV.LOCALES list, and the (possible) loading of locale polyfills for the Intl subsystems that are in use. Test plan: * Canvas pages come up normally * Try a locale that requires polyfilling (recommend Welsh (Cymraeg) in Chrome browser) * That should still work, you should see console messages affirming that the locale was polyfilled for the three Intl subsystems that we use Change-Id: Ie9b386d5006a03372583240afca06190a4f23ee2 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/294705 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Jacob Burroughs <jburroughs@instructure.com> QA-Review: Charley Kline <ckline@instructure.com> Product-Review: Charley Kline <ckline@instructure.com>
2022-06-22 07:49:54 +08:00
"ui/engine",
(webpack) unify tinymce installation refs FOO-2835 flag = none hoist tinymce to the top since we're using the same version as the RCE, this way we don't end up with 2 separate installations that strange CSS require() call has to be relative for a reason i don't have neither time nor desire to unravel there was a discrepancy in the noParse directive between our webpack config in test and outside of test: the test one was excluding the entirety of tinymce, which is fine for the main tinymce module but not so for the "icons" one that the rce package depends on. This was working OK because the test config was ignoring the top-level tinymce icons module, which is never required, but now that it's getting required, it fell apart. I kept to the non-test version where we exclude only the main module "tinymce.js", as there's no value beyond that. ~ test plan ~ the RCE still works (e.g. in assignment edit page) and looks OK Change-Id: I664930753189d8f3966ddec0d0340ba100af6ab3 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/294132 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Charley Kline <ckline@instructure.com> QA-Review: Charley Kline <ckline@instructure.com> Product-Review: Charley Kline <ckline@instructure.com>
2022-06-17 13:31:09 +08:00
"ui/shared/*"
Use yarn workspaces Run `script/nuke_node.sh` to clean everything up Run `yarn install` it should install everything for everything Run `yarn build` and `yarn test` they should work exactly as before Change-Id: I11a27ff2d705c6cbb3b3f9029dd8b32138706146 Reviewed-on: https://gerrit.instructure.com/151356 Tested-by: Jenkins Reviewed-by: Brent Burgoyne <bburgoyne@instructure.com> Product-Review: Ryan Shaw <ryan@instructure.com> QA-Review: Ryan Shaw <ryan@instructure.com>
2018-05-25 00:09:03 +08:00
]
},
move napa from "devDependencies" to "dependencies" Change-Id: I4dde9458868cd5c1c41b921414dff4b3dc9371de Reviewed-on: https://gerrit.instructure.com/29878 Reviewed-by: Simon Williams <simon@instructure.com> Reviewed-by: Jason Madsen <jmadsen@instructure.com> Product-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> QA-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Tested-by: Aaron Shafovaloff <ashafovaloff@instructure.com>
2014-02-11 02:29:11 +08:00
"dependencies": {
add @apollo/client to our dependencies refs VICE-2232 flag=none Test Plan: - N/A nothing has changed except adding in a new dependency Change-Id: I310623d0c35cca38d7a37a9a9c66a5f2f87df59a Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/277364 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Drake Harper <drake.harper@instructure.com> Reviewed-by: Davis Hyer <dhyer@instructure.com> Product-Review: Drake Harper <drake.harper@instructure.com> Product-Review: Davis Hyer <dhyer@instructure.com> QA-Review: Drake Harper <drake.harper@instructure.com> QA-Review: Davis Hyer <dhyer@instructure.com>
2021-11-04 00:38:26 +08:00
"@apollo/client": "^3.4.16",
replace node-sass with dart-sass refs FOO-1116 flag = none this switches brandable_css from using node-sass as an engine to dart-sass breaking changes that we had to accommodate (they are warnings at this point but obnoxiously noisy): - https://sass-lang.com/documentation/breaking-changes/slash-div - https://sass-lang.com/documentation/breaking-changes/color-units we have to make sure there are no regressions in the styles overall, and in the issue described in SIS-3125 in particular, since that was the reason we were stuck on node-sass@4.7.2 == TEST PLAN - rebuild your assets - verify there are no visual regressions , good luck Change-Id: I19bf204df760eb56ad23c14294ef42ec6103c017 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/253054 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: August Thornton <august@instructure.com> QA-Review: August Thornton <august@instructure.com> Product-Review: August Thornton <august@instructure.com>
2021-07-01 01:51:10 +08:00
"@instructure/brandable_css": "^3",
Upgrade Canvas to InstUI version 8 (second try) Refs FOO-3190 Refs FOO-3708 Refs FOO-3913 flag=none [fsc-max-nodes=30] [fsc-timeout=60] Uprevs InstUI and addresses all post-uprev tasks. Also now that InstUI is fully TypeScript, a bunch of type errors appeared which needed to be addressed. It builds against the commit of MRA that will have to merge concurrently with this. Still to do: theme -> themeOverride which is a separate commit off of this one that is ready to go. Test plan: * cross your fingers * (this will need some extensive review before merging) Change-Id: I45a1138530d415398b019cfedcf8a3b57a051912 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/329443 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Ryan Norton <rnorton@instructure.com> Reviewed-by: Isaac Moore <isaac.moore@instructure.com> Product-Review: Ryan Norton <rnorton@instructure.com> QA-Review: Charley Kline <ckline@instructure.com>
2023-08-31 00:16:52 +08:00
"@instructure/canvas-media": "*",
"@instructure/debounce": "^8",
"@instructure/emotion": "^8",
Update ui-media-player this should fix issues with the media player in safari closes LF-662 flag=none test plan: - in a Safari browser, add some media to a page using the rce - ensure that you can pause/play/pause again the video/audio as expected, both in the rce and after saving the page - ensure otherwise that the media player is still working normally Change-Id: I7431924592b5ae2d7c33e308673a6ca7466aacc9 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/327631 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Robin Kuss <rkuss@instructure.com> QA-Review: Robin Kuss <rkuss@instructure.com> Product-Review: Sarah Gerard <sarah.gerard@instructure.com>
2023-09-13 22:48:32 +08:00
"@instructure/media-capture": "^9.0.0",
upgrade 'media-capture-new' to rc.38 flag=speedgrader_studio_media_capture test plan: - tests pass Change-Id: I655570e0066cdbd10ddd6aacf43fdad2280fb789 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/343300 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Spencer Olson <solson@instructure.com> QA-Review: Derek Williams <derek.williams@instructure.com> Product-Review: Cameron Ray <cameron.ray@instructure.com>
2024-03-20 22:19:20 +08:00
"@instructure/media-capture-new": "npm:@instructure/media-capture@9.1.2-rc.38",
Upgrade to outcomes-ui 3.0.0 closes OUT-6112 OUT-5215 flag=outcome_alignment_non_scoring_content test plan: - confirm that alignments on canvas wiki pages continues to work by testing g/235665 Change-Id: I0677af6223090524746abb28bee01109c701d533 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/336828 QA-Review: Chrystal Langston <chrystal.langston@instructure.com> Reviewed-by: Kyle Rosenbaum <krosenbaum@instructure.com> Product-Review: Kyle Rosenbaum <krosenbaum@instructure.com> Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com>
2024-01-06 05:02:00 +08:00
"@instructure/outcomes-ui": "^3",
bump npm-run-all version Change-Id: Ieae7ac480124e52050c79ca83c99a7fe698c48d5 Reviewed-on: https://gerrit.instructure.com/173262 Reviewed-by: Clay Diffrient <cdiffrient@instructure.com> Tested-by: Jenkins QA-Review: Gary Mei <gmei@instructure.com> Product-Review: Gary Mei <gmei@instructure.com>
2018-11-27 02:20:33 +08:00
"@instructure/react-crop": "^5.0.1",
[node12] upgrade to node 12.19.1 (LTS) fixes FOO-1116 flag = none this upgrade was problematic mostly because of Node's support for ES modules (ESM) that is still fairly recent and introduces some complexity around packaging. This is also the reason for the considerable hack related to @instructure packages (see inline documentation) that can be removed once we fix things upstream | test plan | | --------- | - install node 12 if needed (e.g. not on docker) - purge your node modules: rm -rf {.,client_apps/*,gems/*,gems/plugins/*,packages/*}/node_modules - make sure you can still build locally (native/docker) bundle exec rake canvas:compile_assets Change-Id: If9605ac428f0ff228f8852f0becb9fbac750f1f2 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/253166 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Simon Williams <simon@instructure.com> Reviewed-by: Charley Kline <ckline@instructure.com> QA-Review: Simon Williams <simon@instructure.com> QA-Review: Charley Kline <ckline@instructure.com> Product-Review: Charley Kline <ckline@instructure.com>
2020-12-03 07:53:26 +08:00
"@instructure/reactour": "https://github.com/instructure/reactour#b908434fe544703e26bc67c67c4111252c401f92",
ensure workspace pkgs aren't fetched from registry refs SEC-4437 flag = none [pin-commit-respondus_lockdown_browser=8746ff2ccfd6e9ac1d7280687c88e9fa67c0f693] [pin-commit-multiple_root_accounts=7b11533084764b3a34f390e9a75df26e9dd871f9] rationale in the script file and more context in the accompanying ticket ~ test plan ~ edit package.json and modify one of the explicit workspace dependencies such as @instructure/ready to have a specifier other than "*", run the script and verify it exits with 1 yarn --silent workspaces info --json | \ node script/yarn-validate-workspace-deps.js 2>/dev/null Change-Id: I6624ada67a21d433477a7ad4d36acf5801853b7a Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/282948 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Ben Rinaca <brinaca@instructure.com> QA-Review: Ahmad Amireh <ahmad@instructure.com> Product-Review: Ahmad Amireh <ahmad@instructure.com>
2022-01-18 01:00:41 +08:00
"@instructure/ready": "*",
Upgrade Canvas to InstUI version 8 (second try) Refs FOO-3190 Refs FOO-3708 Refs FOO-3913 flag=none [fsc-max-nodes=30] [fsc-timeout=60] Uprevs InstUI and addresses all post-uprev tasks. Also now that InstUI is fully TypeScript, a bunch of type errors appeared which needed to be addressed. It builds against the commit of MRA that will have to merge concurrently with this. Still to do: theme -> themeOverride which is a separate commit off of this one that is ready to go. Test plan: * cross your fingers * (this will need some extensive review before merging) Change-Id: I45a1138530d415398b019cfedcf8a3b57a051912 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/329443 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Ryan Norton <rnorton@instructure.com> Reviewed-by: Isaac Moore <isaac.moore@instructure.com> Product-Review: Ryan Norton <rnorton@instructure.com> QA-Review: Charley Kline <ckline@instructure.com>
2023-08-31 00:16:52 +08:00
"@instructure/ui-a11y-content": "^8",
"@instructure/ui-a11y-utils": "^8",
"@instructure/ui-alerts": "^8",
"@instructure/ui-avatar": "^8",
"@instructure/ui-badge": "^8",
"@instructure/ui-billboard": "^8",
"@instructure/ui-breadcrumb": "^8",
"@instructure/ui-buttons": "^8",
"@instructure/ui-calendar": "^8",
"@instructure/ui-checkbox": "^8",
"@instructure/ui-date-input": "^8",
Bump instui to 8.45.0 Change-Id: I9d05c3a1bf1ef9d32025688b612543dd647d8d88 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/329627 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Ed Schiebel <eschiebel@instructure.com> Reviewed-by: Aaron Shafovaloff <ashafovaloff@instructure.com> Reviewed-by: Ryan Norton <rnorton@instructure.com> Reviewed-by: Charley Kline <ckline@instructure.com> QA-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Product-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Product-Review: Ryan Norton <rnorton@instructure.com> Product-Review: Charley Kline <ckline@instructure.com>
2023-10-06 22:00:35 +08:00
"@instructure/ui-date-time-input": "^8",
Upgrade Canvas to InstUI version 8 (second try) Refs FOO-3190 Refs FOO-3708 Refs FOO-3913 flag=none [fsc-max-nodes=30] [fsc-timeout=60] Uprevs InstUI and addresses all post-uprev tasks. Also now that InstUI is fully TypeScript, a bunch of type errors appeared which needed to be addressed. It builds against the commit of MRA that will have to merge concurrently with this. Still to do: theme -> themeOverride which is a separate commit off of this one that is ready to go. Test plan: * cross your fingers * (this will need some extensive review before merging) Change-Id: I45a1138530d415398b019cfedcf8a3b57a051912 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/329443 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Ryan Norton <rnorton@instructure.com> Reviewed-by: Isaac Moore <isaac.moore@instructure.com> Product-Review: Ryan Norton <rnorton@instructure.com> QA-Review: Charley Kline <ckline@instructure.com>
2023-08-31 00:16:52 +08:00
"@instructure/ui-decorator": "^8",
Add more new SideNav scaffolding flag=none test plan: build passes refs FOO-3642 Change-Id: I570f06af4cb85514801f8ff31eb050b5ffb283be Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/330985 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Martin Ochoa <martin.ochoa@instructure.com> Reviewed-by: Gustavo Bernardes <gustavo.bernardes@instructure.com> QA-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Product-Review: Aaron Shafovaloff <ashafovaloff@instructure.com>
2023-10-24 05:17:54 +08:00
"@instructure/ui-dialog": "^8",
Upgrade Canvas to InstUI version 8 (second try) Refs FOO-3190 Refs FOO-3708 Refs FOO-3913 flag=none [fsc-max-nodes=30] [fsc-timeout=60] Uprevs InstUI and addresses all post-uprev tasks. Also now that InstUI is fully TypeScript, a bunch of type errors appeared which needed to be addressed. It builds against the commit of MRA that will have to merge concurrently with this. Still to do: theme -> themeOverride which is a separate commit off of this one that is ready to go. Test plan: * cross your fingers * (this will need some extensive review before merging) Change-Id: I45a1138530d415398b019cfedcf8a3b57a051912 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/329443 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Ryan Norton <rnorton@instructure.com> Reviewed-by: Isaac Moore <isaac.moore@instructure.com> Product-Review: Ryan Norton <rnorton@instructure.com> QA-Review: Charley Kline <ckline@instructure.com>
2023-08-31 00:16:52 +08:00
"@instructure/ui-drawer-layout": "8",
"@instructure/ui-editable": "^8",
"@instructure/ui-file-drop": "^8",
"@instructure/ui-flex": "^8",
"@instructure/ui-focusable": "^8",
"@instructure/ui-form-field": "^8",
"@instructure/ui-grid": "^8",
"@instructure/ui-heading": "^8",
"@instructure/ui-i18n": "^8",
"@instructure/ui-icons": "^8",
"@instructure/ui-img": "^8",
"@instructure/ui-link": "^8",
"@instructure/ui-list": "^8",
Update ui-media-player this should fix issues with the media player in safari closes LF-662 flag=none test plan: - in a Safari browser, add some media to a page using the rce - ensure that you can pause/play/pause again the video/audio as expected, both in the rce and after saving the page - ensure otherwise that the media player is still working normally Change-Id: I7431924592b5ae2d7c33e308673a6ca7466aacc9 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/327631 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Robin Kuss <rkuss@instructure.com> QA-Review: Robin Kuss <rkuss@instructure.com> Product-Review: Sarah Gerard <sarah.gerard@instructure.com>
2023-09-13 22:48:32 +08:00
"@instructure/ui-media-player": "^9.0.0",
Upgrade Canvas to InstUI version 8 (second try) Refs FOO-3190 Refs FOO-3708 Refs FOO-3913 flag=none [fsc-max-nodes=30] [fsc-timeout=60] Uprevs InstUI and addresses all post-uprev tasks. Also now that InstUI is fully TypeScript, a bunch of type errors appeared which needed to be addressed. It builds against the commit of MRA that will have to merge concurrently with this. Still to do: theme -> themeOverride which is a separate commit off of this one that is ready to go. Test plan: * cross your fingers * (this will need some extensive review before merging) Change-Id: I45a1138530d415398b019cfedcf8a3b57a051912 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/329443 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Ryan Norton <rnorton@instructure.com> Reviewed-by: Isaac Moore <isaac.moore@instructure.com> Product-Review: Ryan Norton <rnorton@instructure.com> QA-Review: Charley Kline <ckline@instructure.com>
2023-08-31 00:16:52 +08:00
"@instructure/ui-menu": "^8",
"@instructure/ui-metric": "^8",
"@instructure/ui-modal": "^8",
"@instructure/ui-motion": "^8",
"@instructure/ui-navigation": "^8",
"@instructure/ui-number-input": "^8",
"@instructure/ui-overlays": "^8",
"@instructure/ui-pagination": "^8",
"@instructure/ui-pill": "^8",
"@instructure/ui-portal": "^8",
"@instructure/ui-progress": "^8",
"@instructure/ui-radio-input": "^8",
"@instructure/ui-rating": "^8",
"@instructure/ui-react-utils": "^8",
"@instructure/ui-responsive": "^8",
"@instructure/ui-select": "^8",
"@instructure/ui-simple-select": "^8",
"@instructure/ui-spinner": "^8",
"@instructure/ui-svg-images": "^8",
"@instructure/ui-table": "^8",
"@instructure/ui-tabs": "^8",
"@instructure/ui-tag": "^8",
"@instructure/ui-text": "^8",
"@instructure/ui-text-area": "^8",
"@instructure/ui-text-input": "^8",
"@instructure/ui-themes": "^8",
"@instructure/ui-time-select": "^8",
"@instructure/ui-toggle-details": "^8",
"@instructure/ui-tooltip": "^8",
Bump InstUI to 8.49 for new nav bar stuff Closes FOO-4017 flag=none Several bug fixes, plus this has the requested changes from InstUI for the new look and feel for the side and top navigation bars. Test plan: * automated tests pass Change-Id: I5292256e4e479c70837cc77b10b97dfaba235848 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/333822 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> QA-Review: Charley Kline <ckline@instructure.com> Product-Review: Charley Kline <ckline@instructure.com> Reviewed-by: Aaron Shafovaloff <ashafovaloff@instructure.com>
2023-11-28 03:59:57 +08:00
"@instructure/ui-top-nav-bar": "^8",
Upgrade Canvas to InstUI version 8 (second try) Refs FOO-3190 Refs FOO-3708 Refs FOO-3913 flag=none [fsc-max-nodes=30] [fsc-timeout=60] Uprevs InstUI and addresses all post-uprev tasks. Also now that InstUI is fully TypeScript, a bunch of type errors appeared which needed to be addressed. It builds against the commit of MRA that will have to merge concurrently with this. Still to do: theme -> themeOverride which is a separate commit off of this one that is ready to go. Test plan: * cross your fingers * (this will need some extensive review before merging) Change-Id: I45a1138530d415398b019cfedcf8a3b57a051912 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/329443 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Ryan Norton <rnorton@instructure.com> Reviewed-by: Isaac Moore <isaac.moore@instructure.com> Product-Review: Ryan Norton <rnorton@instructure.com> QA-Review: Charley Kline <ckline@instructure.com>
2023-08-31 00:16:52 +08:00
"@instructure/ui-tray": "^8",
"@instructure/ui-tree-browser": "^8",
"@instructure/ui-view": "^8",
"@instructure/uid": "^8",
Uprev @instructure/updown Refs FOO-2801 flag=none Turns out the updown package used a JS feature that is not 100% supported by all the supported Canvas browser. That was fixed in the package and this bumps the dep version to pull it in to Canvas. Test plan: * If you were getting "TypeError: Object.hasOwn is not a function" you should not get it any more. Change-Id: Ibdaf313492c762a0b65143269be0054f06f4b908 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/296686 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Jacob Burroughs <jburroughs@instructure.com> QA-Review: Charley Kline <ckline@instructure.com> Product-Review: Charley Kline <ckline@instructure.com>
2022-07-21 06:04:38 +08:00
"@instructure/updown": "^1.3",
update Microsoft Immersive Reader SDK closes LS-1377 flag = immersive_reader_wiki_pages Test Plan: - Enable immersive reader. - Because there doesn't seem to be a way to run this locally (without consul), I had to temporarily modify the immersive_reader_controller.rb and added prod creds to get this to test. see me for more details Change-Id: Ifaa7edfa94ff29856ae6b474548e0f450b9d4c6c Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/245869 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Ed Schiebel <eschiebel@instructure.com> QA-Review: Robin Kuss <rkuss@instructure.com> Product-Review: Clint Furse <cfurse@instructure.com>
2020-08-25 00:57:49 +08:00
"@microsoft/immersive-reader-sdk": "^1.1.0",
Fix DER-encoded LDAP CA's failing to parse This fixes an issue where DER-encoded LDAP root CA's were failing to parse, because they were incorrectly being interpreted as UTF-8. fixes AE-317 flag=none test plan: (1) upload a DER-encoded root CA - verify it continues to parse (2) upload a PEM-encoded root CA - verify it continues to parse (3) upload a PKCS7-encoded cert chain - verify the root CA continues to parse (4) repeat steps 3 and 4 with CRLF line endings Change-Id: I25b0fe902f37e5dc1c671555595504fef6a0b39e Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/319489 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Jacob Burroughs <jburroughs@instructure.com> QA-Review: Isaac Moore <isaac.moore@instructure.com> Product-Review: Isaac Moore <isaac.moore@instructure.com>
2023-06-02 04:04:12 +08:00
"@peculiar/asn1-schema": "^2.3.6",
Add internal CA upload to LDAP authentication providers This will allow an admin to specify an internal CA that they would like to trust when connecting to their configured LDAP instance. It also allows an admin to explicitly opt in to TLS certificate verification prior to our enforcement date. closes AE-180 flag=none test plan: - with the `verify_ldap_certs` flag disabled: - verify LDAP connections succeed with bad certs - upload a CA certificate - verify LDAP connections still succeed with bad certs - define the `ldap_validate_tls_cert_enforcement_date` setting - verify the "Verify TLS Certificate" checkbox is visible, and editable - verify the help text appears - enable the checkbox - verify connections fail with bad certs - verify connections succeed if the cert was issued by the uploaded CA - clear the `ldap_validate_tls_cert_enforcement_date` setting - verify the "Verify TLS Certificate" checkbox is hidden - with the `verify_ldap_certs` flag enabled: - verify LDAP connections do not succeed with bad certs - upload a CA certificate - verify LDAP connections succeed if the cert was issued by the uploaded CA - define the `ldap_validate_tls_cert_enforcement_date` setting - verify the "Verify TLS Certificate" checkbox is on, but disabled - verify the help text is hidden - clear the `ldap_validate_tls_cert_enforcement_date` setting - verify the "Verify TLS Certificate" checkbox is hidden Change-Id: I41536261bdc7e5554cbf5b9915638ced996192f3 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/315294 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> QA-Review: Isaac Moore <isaac.moore@instructure.com> Product-Review: Isaac Moore <isaac.moore@instructure.com> Reviewed-by: Jacob Burroughs <jburroughs@instructure.com> Migration-Review: Jacob Burroughs <jburroughs@instructure.com>
2023-04-13 12:19:01 +08:00
"@peculiar/x509": "^1.9.3",
Position and mount Mentions component refs VICE-1683 Test Plan 1. Enable Mentions Flag and Discussion Redesign Flag 2. Open Discussions and open an RCE 3. Type some text and then the @ symbol. 4. Notice, the menu should be positioned under the @ symbol populated with dummy data names (for now) Note: There is no filtering, selecting, or simple way to escape at the moment and will be coming in future reviews. Change-Id: Icd8fa583004db77313f3fb188933d1a202ef2e0c Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/269684 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Matthew Lemon <mlemon@instructure.com> QA-Review: Matthew Lemon <mlemon@instructure.com> Product-Review: Matthew Lemon <mlemon@instructure.com>
2021-07-12 09:26:47 +08:00
"@popperjs/core": "^2.9.2",
replace webpack with rspack test plan: - run rspack locally (as "webpack" for now) - ensure coverage data for crystalball - ensure build passes with skip-crystalball - ensure source maps for local dev - ensure bundle analysis is available and documented - ensure compile times are at least comparable refs CFA-32 [skip-crystalball] flag=none Change-Id: I8ad916ac7fbe9e3ecee5c690abcd78cdde748ab6 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/339401 Reviewed-by: Isaac Moore <isaac.moore@instructure.com> Build-Review: Isaac Moore <isaac.moore@instructure.com> Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> QA-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Product-Review: Aaron Shafovaloff <ashafovaloff@instructure.com>
2024-02-01 04:19:23 +08:00
"@rspack/cli": "^0.5.4",
"@rspack/core": "^0.5.4",
"@rspack/plugin-react-refresh": "^0.5.4",
Upgrade Sentry frontend packages Did not upgrade @sentry/fullstory flag=none Change-Id: I664a054e1d52366688de81f9dc61b82113500ac5 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/333285 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Isaac Moore <isaac.moore@instructure.com> QA-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Product-Review: Aaron Shafovaloff <ashafovaloff@instructure.com>
2023-11-21 03:00:15 +08:00
"@sentry/cli": "^2.21.5",
"@sentry/react": "^7.81.0",
replace webpack with rspack test plan: - run rspack locally (as "webpack" for now) - ensure coverage data for crystalball - ensure build passes with skip-crystalball - ensure source maps for local dev - ensure bundle analysis is available and documented - ensure compile times are at least comparable refs CFA-32 [skip-crystalball] flag=none Change-Id: I8ad916ac7fbe9e3ecee5c690abcd78cdde748ab6 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/339401 Reviewed-by: Isaac Moore <isaac.moore@instructure.com> Build-Review: Isaac Moore <isaac.moore@instructure.com> Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> QA-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Product-Review: Aaron Shafovaloff <ashafovaloff@instructure.com>
2024-02-01 04:19:23 +08:00
"@swc/cli": "^0.3.9",
"@swc/core": "1.3.105",
"@swc/helpers": "^0.5.6",
"@swc/jest": "^0.2.36",
Badge counts in SideNavBar test plan: badge counts show up in navbar items in new SideNavBar flag=instui_nav refs FOO-3880 refs FOO-3894 refs FOO-3895 Change-Id: Iea01d6d9b5aa6aed7afe129842b17b1a6463c9b1 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/331126 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Martin Ochoa <martin.ochoa@instructure.com> QA-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Product-Review: Aaron Shafovaloff <ashafovaloff@instructure.com>
2023-10-25 00:45:10 +08:00
"@tanstack/query-sync-storage-persister": "^4.36.1",
"@tanstack/react-query": "^4.36.1",
"@tanstack/react-query-persist-client": "^4.36.1",
upgrade msw flag=none closes CFA-35 closes LF-1117 Change-Id: I42e65f70ee74a2931a0a4439a4c9c0f22466ef62 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/336892 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Caleb Guanzon <cguanzon@instructure.com> Product-Review: Caleb Guanzon <cguanzon@instructure.com> QA-Review: Aaron Shafovaloff <ashafovaloff@instructure.com>
2024-01-08 09:23:15 +08:00
"@types/b-spline": "^2.0.4",
"@types/dagre": "^0.7.52",
Add @types/jquery.cookie dependency Change-Id: I9018ddc0f353aed6d87620e91a9a8629372174ec Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/308210 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Aaron Shafovaloff <ashafovaloff@instructure.com> Reviewed-by: Xander Moffatt <xmoffatt@instructure.com> QA-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Product-Review: Aaron Shafovaloff <ashafovaloff@instructure.com>
2023-01-06 02:43:53 +08:00
"@types/jquery.cookie": "^1.4.32",
Convert DashboardCard to TypeScript refs DE-1083 Change-Id: I2df4456fd58878dbed4366f52e32acdccd141aa5 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/286065 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Aaron Ogata <aogata@instructure.com> QA-Review: Isaac Moore <isaac.moore@instructure.com> Product-Review: Isaac Moore <isaac.moore@instructure.com>
2022-03-01 05:52:52 +08:00
"@types/react-dnd": "2.0.36",
Replace our homegrown link finder with twitter-text While I am at it, decaffinate and typescriptify TextHelper fixes FOO-2987 Change-Id: I0b8f33a610bee737ea79ad24d8aec8f8e8051c49 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/299013 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: August Thornton <august@instructure.com> Product-Review: August Thornton <august@instructure.com> QA-Review: Jacob Burroughs <jburroughs@instructure.com> Build-Review: Bobby Buten <bobby.buten@instructure.com>
2022-08-18 23:44:07 +08:00
"@types/twitter-text": "^3.1.2",
Add LTI postMessage usage tracking why: This will help us make informed decisions about what support we should apply to what messages, and also inform us on how clients are using our API. test plan: Add: frontend_data_collection_endpoint: 'https://canvas-frontend-data-edge.inseng.net/submit' to the development.private.canvas key of config/dynamic_settings.yml file, restart Canvas, and launch the 1.3 test tool, and send a valid postMessage back, i.e. you can send the message: { "subject": "lti.showAlert", "body": "This is a message" } Make sure that a PUT request is sent to https://canvas-frontend-data-edge.inseng.net/submit by looking at the network tab. fixes INTEROP-7911 flag=none Change-Id: Iae9572feace0c0dcc81662b3bec3dc5dcd88d515 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/308721 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Xander Moffatt <xmoffatt@instructure.com> QA-Review: Xander Moffatt <xmoffatt@instructure.com> Product-Review: Xander Moffatt <xmoffatt@instructure.com>
2023-01-13 05:31:29 +08:00
"@types/uuid": "^9.0.0",
upgrade vitest also: - more tests passing in vitests - specifies which folders are left to resolve in the vitest config test plan: - build passes Change-Id: I34fee1a8b44101fec4b801fa6f67b9562df0425c Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/335009 Reviewed-by: Cameron Ray <cameron.ray@instructure.com> QA-Review: Cameron Ray <cameron.ray@instructure.com> Product-Review: Cameron Ray <cameron.ray@instructure.com> Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com>
2023-12-10 22:47:24 +08:00
"@vitest/coverage-v8": "^1.0.4",
Begin SideNav implementation Test plan: - localStorage.instui_nav_dev = 'true' - visit /accounts/ - click on an account - the SideBar component should show flag=none refs FOO-3868 Change-Id: I0528dc0411a63d700905c7f8780e214585f0397a Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/328629 Reviewed-by: Michael Hulse <michael.hulse@instructure.com> Reviewed-by: Charley Kline <ckline@instructure.com> QA-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Product-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com>
2023-09-26 03:20:00 +08:00
"apollo-cache": "^1.3.2",
upgrade & dedupe node packages fixes FOO-2037 the result of removing yarn.lock and reinstalling packages according to the latest version within their specified range Change-Id: I1d2851d5a1a9fc6caeddc388492622ffd4f59379 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/255460 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Product-Review: Charley Kline <ckline@instructure.com> QA-Review: Charley Kline <ckline@instructure.com> Reviewed-by: Charley Kline <ckline@instructure.com>
2021-05-26 01:22:32 +08:00
"apollo-cache-inmemory": "^1.6.3",
persist apollo cache for discussions fixes VICE-1998 flag=react_discussions_post Test Plan: - Enable the apollo caching FF on siteadmin - You should see the apollo cache stored into local storage - Subsequent page visits/reloads should load from the cache first but still make a graphql network request to ensure we have fresh data - Test with slow network for fun time Change-Id: Ib82520a3877de5a4072e4896f33320bb1c1724bb Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/272603 Reviewed-by: Jeffrey Johnson <jeffrey.johnson@instructure.com> QA-Review: Jeffrey Johnson <jeffrey.johnson@instructure.com> Product-Review: Jeffrey Johnson <jeffrey.johnson@instructure.com> Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com>
2021-09-01 01:15:20 +08:00
"apollo-cache-persist": "^0.1.1",
upgrade react-apollo to 3.x.x closes COMMS-2316 TEST PLAN ------------------------------- all tests pass Change-Id: I0c270bb7a8d5dfa166641648841e619a1a21c0f4 Reviewed-on: https://gerrit.instructure.com/206348 Reviewed-by: Matthew Lemon <mlemon@instructure.com> Tested-by: Jenkins QA-Review: Ben Nelson <bnelson@instructure.com> Product-Review: Ben Nelson <bnelson@instructure.com>
2019-08-22 00:54:59 +08:00
"apollo-client": "^2.6.4",
Begin SideNav implementation Test plan: - localStorage.instui_nav_dev = 'true' - visit /accounts/ - click on an account - the SideBar component should show flag=none refs FOO-3868 Change-Id: I0528dc0411a63d700905c7f8780e214585f0397a Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/328629 Reviewed-by: Michael Hulse <michael.hulse@instructure.com> Reviewed-by: Charley Kline <ckline@instructure.com> QA-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Product-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com>
2023-09-26 03:20:00 +08:00
"apollo-link": "^1.2.3",
use apollo client instead of apollo boost This prepares us for using apollo's instrospection fragment matcher (which isn't supported with -boost). Test plan: pages that use graphql still work refs GQL-17 Change-Id: Ib6af304855e6c0e23b598344ac1d30f4d4aa03a5 Reviewed-on: https://gerrit.instructure.com/172936 Tested-by: Jenkins Reviewed-by: Carl Kibler <ckibler@instructure.com> QA-Review: Cameron Matheson <cameron@instructure.com> Product-Review: Cameron Matheson <cameron@instructure.com>
2018-11-20 04:17:17 +08:00
"apollo-link-error": "^1.1.1",
"apollo-link-http": "^1.5.5",
Display multiple modules in A2 student view This also adds support for apollo-link-state. We are using this to move data from the `ENV` into our apollo query results, to keep a single source of truth and easier unit tests. If there are more then two modules that an assignment belongs to (which is abnormal) we are only rendering the first two modules with an additional link to the modules page, indicating that there are more modules this assignment belongs to. Fixes COMMS-1800 Test Plan: - Create an assignment, and add it to four modules - Navigate to the assignment as a student - Notice that 2 of the four modules are displayed in the header Change-Id: I9b797486ba56c8b827e5f76114c5a08d2f969f41 Reviewed-on: https://gerrit.instructure.com/174837 Tested-by: Jenkins Reviewed-by: Steven Burnett <sburnett@instructure.com> QA-Review: Landon Gilbert-Bland <lbland@instructure.com> Product-Review: Landon Gilbert-Bland <lbland@instructure.com>
2018-12-11 03:56:24 +08:00
"apollo-link-state": "^0.4.2",
silence some yarn warnings caused by Apollo stuff Test plan: * run `yarn` * you should not see these warnings: warning " > react-apollo@3.0.1" has unmet peer dependency "@types/react@^16.8.0". warning "react-apollo > @apollo/react-common@3.0.1" has unmet peer dependency "@types/react@^16.8.0". warning "react-apollo > @apollo/react-common@3.0.1" has unmet peer dependency "apollo-utilities@^1.3.2". warning "react-apollo > @apollo/react-components@3.0.1" has unmet peer dependency "@types/react@^16.8.0". warning "react-apollo > @apollo/react-components@3.0.1" has unmet peer dependency "apollo-cache@^1.3.2". warning "react-apollo > @apollo/react-components@3.0.1" has unmet peer dependency "apollo-utilities@^1.3.2". warning "react-apollo > @apollo/react-hoc@3.0.1" has unmet peer dependency "@types/react@^16.8.0". warning "react-apollo > @apollo/react-hooks@3.0.1" has unmet peer dependency "@types/react@^16.8.0". warning " > @apollo/react-testing@3.0.1" has unmet peer dependency "apollo-utilities@^1.3.2". Change-Id: Icd38c4e742b00d3f31fe187b1bc915fd01169880 Reviewed-on: https://gerrit.instructure.com/207064 Tested-by: Jenkins QA-Review: Ryan Shaw <ryan@instructure.com> Product-Review: Ryan Shaw <ryan@instructure.com> Reviewed-by: Cameron Matheson <cameron@instructure.com>
2019-08-28 04:10:29 +08:00
"apollo-utilities": "^1.3.2",
Revert "Upgrade Canvas to InstUI version 8 (frd)" Refs FOO-3862 flag=none [pin-commit-multiple_root_accounts=9d1698853e352f7e023e196e80cc195215a2b98c] This reverts commit 448f1eebefc561fe3241781cd68739686fc5d100. Reason for revert: downgrade to InstUI 7 per engineering leadership Change-Id: I89c607d09c29885da77b4474b757c7f205e51f01 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/328102 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Aaron Shafovaloff <ashafovaloff@instructure.com> QA-Review: Charley Kline <ckline@instructure.com> Product-Review: Charley Kline <ckline@instructure.com>
2023-09-21 04:59:21 +08:00
"axios": "^0.21.1",
Begin SideNav implementation Test plan: - localStorage.instui_nav_dev = 'true' - visit /accounts/ - click on an account - the SideBar component should show flag=none refs FOO-3868 Change-Id: I0528dc0411a63d700905c7f8780e214585f0397a Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/328629 Reviewed-by: Michael Hulse <michael.hulse@instructure.com> Reviewed-by: Charley Kline <ckline@instructure.com> QA-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Product-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com>
2023-09-26 03:20:00 +08:00
"axios-cache-adapter": "^2.7.0",
upgrade msw flag=none closes CFA-35 closes LF-1117 Change-Id: I42e65f70ee74a2931a0a4439a4c9c0f22466ef62 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/336892 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Caleb Guanzon <cguanzon@instructure.com> Product-Review: Caleb Guanzon <cguanzon@instructure.com> QA-Review: Aaron Shafovaloff <ashafovaloff@instructure.com>
2024-01-08 09:23:15 +08:00
"b-spline": "^2.0.2",
move things from “devDeps” to “dependencies” Closes CNVS-39744 we used to only have the things needed to compile brandable_css in “Dependencies”. This was because, when we used to have to run brandable_css on a job server when someone pressed “preview” in the theme editor, we only wanted to have the minimum amount of node_modules installed there to do that. But now that we no longer have to do any brand-specific css compiling we can just do what is considered normal and put anything that actually goes on the page in “dependencies” and leave all the build tooling, linting, etc stuff in devDependencies. This also makes it so it is really easy to see the cases that we might be loading 2 versions of something in our webpack bundles by running `yarn install --prod --flat`. Whatever that prompts you about is something that will be included more than once in our webpack bundles. Test plan: * run `yarn install` * it should not generate a new yarn.lock because everything is the same versions as before. Change-Id: I87b88f50d2cdbe494f928e5418e8540da9cc084c Reviewed-on: https://gerrit.instructure.com/128244 Tested-by: Jenkins Reviewed-by: Felix Milea-Ciobanu <fmileaciobanu@instructure.com> Reviewed-by: Clay Diffrient <cdiffrient@instructure.com> Product-Review: Ryan Shaw <ryan@instructure.com> QA-Review: Ryan Shaw <ryan@instructure.com>
2017-10-04 01:05:04 +08:00
"backbone": "1.1.1",
maintain precision of grades in grade input fixes GRADE-1098 test plan: 1. Create an Assignment a. with Display Grade as Percentage b. worth 9.5 points 2. Open New Gradebook 3. Grade a student on this assignment twice a. once with 55 (interpreted as percentage) b. again with 55% (explicit percentage) 4. Verify grade is 55% 5. Verify score is 5.225 Change-Id: Ie48ec7d5b787e864bfd3379e8dc6a4dbebebc2e5 Reviewed-on: https://gerrit.instructure.com/148848 Tested-by: Jenkins Reviewed-by: Derek Bender <djbender@instructure.com> Reviewed-by: Shahbaz Javeed <sjaveed@instructure.com> QA-Review: Shahbaz Javeed <sjaveed@instructure.com> Product-Review: Matt Goodwin <mattg@instructure.com>
2018-05-02 04:54:56 +08:00
"big.js": "^5.0.3",
upgrade browserlist Change-Id: I65657dd53a2c570ac131eadbaf7d58983b3bd17d Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/337747 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Michael Hulse <michael.hulse@instructure.com> QA-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Product-Review: Aaron Shafovaloff <ashafovaloff@instructure.com>
2024-01-17 05:27:20 +08:00
"browserslist": "^4.22.2",
Update canvas_offline_course_viewer for new translations Test plan - Smoke test to ensure dependency pinning hasn't caused any issues Change-Id: I98f2feec9c56f98f530685fa9c94c106d9881c4c Reviewed-on: https://gerrit.instructure.com/122023 Reviewed-by: Jon Willesen <jonw+gerrit@instructure.com> Product-Review: Jon Willesen <jonw+gerrit@instructure.com> Tested-by: Jenkins QA-Review: Nathan Rogowski <nathan@instructure.com>
2017-08-09 03:40:06 +08:00
"canvas_offline_course_viewer": "https://github.com/instructure/canvas_offline_course_viewer.git#1.2.0",
Upgrade Canvas to InstUI version 8 (second try) Refs FOO-3190 Refs FOO-3708 Refs FOO-3913 flag=none [fsc-max-nodes=30] [fsc-timeout=60] Uprevs InstUI and addresses all post-uprev tasks. Also now that InstUI is fully TypeScript, a bunch of type errors appeared which needed to be addressed. It builds against the commit of MRA that will have to merge concurrently with this. Still to do: theme -> themeOverride which is a separate commit off of this one that is ready to go. Test plan: * cross your fingers * (this will need some extensive review before merging) Change-Id: I45a1138530d415398b019cfedcf8a3b57a051912 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/329443 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Ryan Norton <rnorton@instructure.com> Reviewed-by: Isaac Moore <isaac.moore@instructure.com> Product-Review: Ryan Norton <rnorton@instructure.com> QA-Review: Charley Kline <ckline@instructure.com>
2023-08-31 00:16:52 +08:00
"chart.js": "^3.9.1",
"chartjs-adapter-moment": "^1.0.0",
move things from “devDeps” to “dependencies” Closes CNVS-39744 we used to only have the things needed to compile brandable_css in “Dependencies”. This was because, when we used to have to run brandable_css on a job server when someone pressed “preview” in the theme editor, we only wanted to have the minimum amount of node_modules installed there to do that. But now that we no longer have to do any brand-specific css compiling we can just do what is considered normal and put anything that actually goes on the page in “dependencies” and leave all the build tooling, linting, etc stuff in devDependencies. This also makes it so it is really easy to see the cases that we might be loading 2 versions of something in our webpack bundles by running `yarn install --prod --flat`. Whatever that prompts you about is something that will be included more than once in our webpack bundles. Test plan: * run `yarn install` * it should not generate a new yarn.lock because everything is the same versions as before. Change-Id: I87b88f50d2cdbe494f928e5418e8540da9cc084c Reviewed-on: https://gerrit.instructure.com/128244 Tested-by: Jenkins Reviewed-by: Felix Milea-Ciobanu <fmileaciobanu@instructure.com> Reviewed-by: Clay Diffrient <cdiffrient@instructure.com> Product-Review: Ryan Shaw <ryan@instructure.com> QA-Review: Ryan Shaw <ryan@instructure.com>
2017-10-04 01:05:04 +08:00
"classnames": "^2.2.5",
"color-slicer": "0.8.0",
re-enable canvas javascript coverage report refs DE-989 flag=none TEST PLAN: confirm https://code-coverage.inseng.net/ is updated with new report Change-Id: I596ce0df04c920b096a875004bd765979dec344b Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/285861 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Aaron Ogata <aogata@instructure.com> QA-Review: Bobby Buten <bobby.buten@instructure.com> Product-Review: Bobby Buten <bobby.buten@instructure.com>
2022-02-24 05:18:06 +08:00
"coverage-istanbul-loader": "^3.0.5",
react 16: use createReactClass for things that can’t be es6 classes these components can’t be converted to the react es6 class syntax because they use Mixins which aren’t supported by es6 classes. Change-Id: I8541b08518cd335c7a711bab117efcda65ac6b2c Reviewed-on: https://gerrit.instructure.com/164135 Tested-by: Jenkins Reviewed-by: Steven Burnett <sburnett@instructure.com> Product-Review: Ryan Shaw <ryan@instructure.com> QA-Review: Ryan Shaw <ryan@instructure.com>
2018-09-12 13:29:44 +08:00
"create-react-class": "^15.6.3",
upgrade msw flag=none closes CFA-35 closes LF-1117 Change-Id: I42e65f70ee74a2931a0a4439a4c9c0f22466ef62 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/336892 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Caleb Guanzon <cguanzon@instructure.com> Product-Review: Caleb Guanzon <cguanzon@instructure.com> QA-Review: Aaron Shafovaloff <ashafovaloff@instructure.com>
2024-01-08 09:23:15 +08:00
"cross-fetch": "^4.0.0",
add encrypted forage for persistent graphql cache Test Plan: - Enable the apollo caching FF on siteadmin - Navigate to a discussion topic - In index db in the application tab in your dev tools you should see the key "apollo-cache-persist" and the value should be encrypted Change-Id: I7584c4ff1f50d0a324d2e2afeec6800671eea44d Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/274010 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Jeffrey Johnson <jeffrey.johnson@instructure.com> QA-Review: Jeffrey Johnson <jeffrey.johnson@instructure.com> Product-Review: Jeffrey Johnson <jeffrey.johnson@instructure.com>
2021-09-21 05:11:21 +08:00
"crypto-js": "^4.1.1",
upgrade d3 to latest 3.x version the previous version caused an error when building native dependencies during the yarn install when using node 8. refs CORE-704 test plan: - ensure d3 charts in gradezilla/OutcomeColumnView render correctly - ensure d3 charts in gradebook/OutcomeColumnView render correctly - ensure d3 charts in grade_summary/OutcomeLineGraphView render correctly - ensure d3 charts in client_apps/canvas_quizzes render correctly - yarn install runs without errors using latest node 8 lts Change-Id: Ib2f8d4acab6060795b50e545eb64f324587b6300 Reviewed-on: https://gerrit.instructure.com/134476 Tested-by: Jenkins Reviewed-by: Ryan Shaw <ryan@instructure.com> QA-Review: Leo Abner <rabner@instructure.com> Product-Review: Brent Burgoyne <bburgoyne@instructure.com>
2017-12-04 23:24:41 +08:00
"d3": "3.5.17",
upgrade msw flag=none closes CFA-35 closes LF-1117 Change-Id: I42e65f70ee74a2931a0a4439a4c9c0f22466ef62 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/336892 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Caleb Guanzon <cguanzon@instructure.com> Product-Review: Caleb Guanzon <cguanzon@instructure.com> QA-Review: Aaron Shafovaloff <ashafovaloff@instructure.com>
2024-01-08 09:23:15 +08:00
"dagre": "^0.8.5",
add submission comment emojis 🎉 closes EVAL-2302 flag=submission_comment_emojis Test Plan: 1. Verify a 'Emojis in Submission Comments' Course Feature Flag exists (needs to be enabled at SiteAdmin level before visible at account and course level). Enable the feature at the SiteAdmin account. 2. In the Account settings for your root account (not the SiteAdmin account), 'unlock' the feature. Then, go to settings for the root account and verify there is a 'Blocked Emojis' section. Click the emoji picker, select 😬, and then click 'Update Settings' at the bottom of the page. 3. Enable the feature flag in a course. 4. At the following pages, verify that the submission comment textarea now includes an emoji 'picker' (button that opens a menu to pick an emoji) and a emoji 'quick picker toolbar' (three emoji buttons below the textarea, that when clicked insert the pictured emoji into the textarea. The icons shown include the most recently used emoji and the two most popular emojis. By default, 👍, 👏, and 😀 are shown. Logged in as a student: - "Assignment Enhancement — Student" page - Submission Details page - "Submit Assignment" page (with "Assignment Enhancement — Student" disabled). Make sure to check the textarea for each submission type (easiest way to do this is to create an assignment and click the checkbox for every submission type). Logged in as a teacher: - Gradebook - SpeedGrader 5. Verify the 😬 emoji is not available in the emoji picker at any of those pages listed above. 6. Disable the feature flag and verify at the pages listed above that the emoji 'picker' and emoji 'quick picker toolbar' are no longer shown. Change-Id: I2c790904927a897bfb0ac30091a5bafb291fd115 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/286283 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Kai Bjorkman <kbjorkman@instructure.com> Reviewed-by: Eduardo Escobar <eduardo.escobar@instructure.com> QA-Review: Kai Bjorkman <kbjorkman@instructure.com> Product-Review: Jody Sailor
2022-03-02 08:06:40 +08:00
"emoji-mart": "^3.0.1",
Add page for managing internal settings This adds a new page where Site Admin users can manage `Setting`s (aka, "Internal Settings"). This can be done on the Site Admin settings page, on the "Internal Settings" tab. Only Site Admin users see and may access this tab. The table displayed renders each setting and its value, and offers the ability to edit or delete each setting. New settings may also be added. Settings denoted internally as `secret` will be displayed, but their values obscured. These settings may not be edited or deleted from the UI. There is also a "Download as..." button that allows all internal settings (except for secret ones) to be downloaded in JSON or CSV format. closes DE-1136 flag=none test plan: - confirm that, as a site admin, you can add, edit, and delete internal settings from the "Internal Settings" tab (note: you can edit a setting by clicking on its value) - confirm the table is sortable by clicking on the column headers - confirm the table is downloadable by choosing either the JSON or CSV options - confirm that your changes are reflected in the database, and in `Settings.get` once settings have been reloaded - confirm that, as a non-site admin user, you can not see the Internal Settings tab Change-Id: Ia143bf40e85b43a1db2f6fcc2791718179c351c4 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/290906 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Jeremy Stanley <jeremy@instructure.com> QA-Review: Jeremy Stanley <jeremy@instructure.com> Product-Review: Isaac Moore <isaac.moore@instructure.com>
2022-05-02 22:45:52 +08:00
"export-from-json": "^1.6.0",
Refactor EditGroupModal with react-final-form closes OUT-4312 flag = improved_outcomes_management Test plan: - Try to edit a group using Improved Outcomes Management and make sure no functionality was broken Change-Id: Ic7f7cf77189b7688187cfd530325aecc393a92c0 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/261655 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Pat Renner <prenner@instructure.com> QA-Review: Brian Watson <bwatson@instructure.com> Product-Review: Augusto Callejas <acallejas@instructure.com>
2021-03-26 00:11:03 +08:00
"final-form": "^4.20.2",
Handle dependent variables in the theme editor After the theme editor refactor dependant variables were not working. This fixes it. This also makes it so that override files are handled properly. closes CORE-1085 Test Plan: - Go to the theme editor with a new theme - Change the "Primary Brand Color" - "Primary Button" should change as well - Preview the changes - Change should be reflected after the preview loads - Repeat that again, the same behavior should occur. - Change the "Primary Button" color and preview - The two items should now be "unlinked" and they change independent of one another - Upload a js override - Preview changes - Upload a css override - Preview changes - Both the js and the css fields should be populated Change-Id: I61572a3c5bdf4f63c82078dff492dc504d0af7bf Reviewed-on: https://gerrit.instructure.com/142395 Tested-by: Jenkins Reviewed-by: Rob Orton <rob@instructure.com> Reviewed-by: Brent Burgoyne <bburgoyne@instructure.com> QA-Review: Tucker McKnight <tmcknight@instructure.com> Product-Review: Clay Diffrient <cdiffrient@instructure.com>
2018-03-02 07:12:40 +08:00
"formdata-polyfill": "^3.0.9",
upgrade to jquery 3.5 with jquery-migrate 3.4.1 (added to instructure_jquery_patches.js this time, as it wasn't being loaded soon enough for header usage in runOnEveryPageButDontBlockAnythingElse.jsx) this change also disables the assignment column resizing and reordering feature in the grid gradebook. The drag library used for this feature does not support jquery 3.x and it is a blocker refs FOO-4260 flag=none Test Plan: - Jenkins Passes [skip-crystalball] [fsc-max-nodes=18] [fsc-timeout=40] Change-Id: I56ff289813c532c98279766dbca19b9ec28c5d0c Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/341600 Product-Review: Ryan Norton <rnorton@instructure.com> QA-Review: August Thornton <august@instructure.com> Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Michael Hulse <michael.hulse@instructure.com>
2024-02-28 10:48:45 +08:00
"fullcalendar": "3.10.5",
bump graphiql to v1.7.2 Change-Id: Iebfa265faaeec0804c821d6549c55a70fd6ab327 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/345373 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Isaac Moore <isaac.moore@instructure.com> QA-Review: Aaron Ogata <aogata@instructure.com> Product-Review: Aaron Ogata <aogata@instructure.com>
2024-04-17 01:09:52 +08:00
"graphiql": "1.7.2",
Begin SideNav implementation Test plan: - localStorage.instui_nav_dev = 'true' - visit /accounts/ - click on an account - the SideBar component should show flag=none refs FOO-3868 Change-Id: I0528dc0411a63d700905c7f8780e214585f0397a Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/328629 Reviewed-by: Michael Hulse <michael.hulse@instructure.com> Reviewed-by: Charley Kline <ckline@instructure.com> QA-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Product-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com>
2023-09-26 03:20:00 +08:00
"graphiql-explorer": "^0.4.2",
bump graphql to latest 15.x try 2 Change-Id: I85d88d3d3d008f76aaed6aa93d88e85b21edce1f Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/345394 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> QA-Review: Aaron Ogata <aogata@instructure.com> Product-Review: Aaron Ogata <aogata@instructure.com> Reviewed-by: Isaac Moore <isaac.moore@instructure.com>
2024-04-17 01:45:51 +08:00
"graphql": "^15",
add rubric redesign react-query setup this commit adds the foundation for react-query to the rubrics redesign. it also uses new graphql queries to return rubric data to the front end. closes EVAL-3616 flag=enhanced_rubrics test plan: - navigate to /accounts/<id>/rubrics - verify that if the account has rubrics, they are displayed in the table - navigate to /courses/<id>/rubrics - verify that if the course has rubrics, they are displayed in the table Change-Id: Ib340a37ad1c3a3d28413b3e8cfce359aa3f5db7a Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/331718 Reviewed-by: Aaron Shafovaloff <ashafovaloff@instructure.com> Reviewed-by: Derek Williams <derek.williams@instructure.com> Reviewed-by: Cameron Ray <cameron.ray@instructure.com> Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> QA-Review: Derek Williams <derek.williams@instructure.com> Product-Review: Cameron Ray <cameron.ray@instructure.com>
2023-11-01 01:12:17 +08:00
"graphql-request": "^6.1.0",
Begin SideNav implementation Test plan: - localStorage.instui_nav_dev = 'true' - visit /accounts/ - click on an account - the SideBar component should show flag=none refs FOO-3868 Change-Id: I0528dc0411a63d700905c7f8780e214585f0397a Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/328629 Reviewed-by: Michael Hulse <michael.hulse@instructure.com> Reviewed-by: Charley Kline <ckline@instructure.com> QA-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Product-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com>
2023-09-26 03:20:00 +08:00
"graphql-tag": "^2.8.0",
Get i18n-js and i18nliner from npm, not vendor closes: CORE-1201 test plan: * the qunit & selenium tests that we have around this should still pass (except for that one that had to be changed because the spec was actually expecting the wrong thing and the old code was erroneous) * load the app in fully production build and make sure translations still work Change-Id: Id06c38f60c1670fb93e85d5479ec747035c1158b Reviewed-on: https://gerrit.instructure.com/143456 Tested-by: Jenkins Reviewed-by: Clay Diffrient <cdiffrient@instructure.com> QA-Review: Tucker McKnight <tmcknight@instructure.com> Product-Review: Ryan Shaw <ryan@instructure.com>
2018-03-14 04:10:14 +08:00
"i18n-js": "^3",
move things from “devDeps” to “dependencies” Closes CNVS-39744 we used to only have the things needed to compile brandable_css in “Dependencies”. This was because, when we used to have to run brandable_css on a job server when someone pressed “preview” in the theme editor, we only wanted to have the minimum amount of node_modules installed there to do that. But now that we no longer have to do any brand-specific css compiling we can just do what is considered normal and put anything that actually goes on the page in “dependencies” and leave all the build tooling, linting, etc stuff in devDependencies. This also makes it so it is really easy to see the cases that we might be loading 2 versions of something in our webpack bundles by running `yarn install --prod --flat`. Whatever that prompts you about is something that will be included more than once in our webpack bundles. Test plan: * run `yarn install` * it should not generate a new yarn.lock because everything is the same versions as before. Change-Id: I87b88f50d2cdbe494f928e5418e8540da9cc084c Reviewed-on: https://gerrit.instructure.com/128244 Tested-by: Jenkins Reviewed-by: Felix Milea-Ciobanu <fmileaciobanu@instructure.com> Reviewed-by: Clay Diffrient <cdiffrient@instructure.com> Product-Review: Ryan Shaw <ryan@instructure.com> QA-Review: Ryan Shaw <ryan@instructure.com>
2017-10-04 01:05:04 +08:00
"ic-ajax": "~2.0.1",
"ic-tabs": "0.1.3",
upgrade immer and immutability-helper npm deps here are 2->3 changes from immutability-helper Huge thanks to @jedmao for converting the library to typescript! New: TypeScript definitions are now generated from TypeScript source. meaning they will always be 100% in sync w/ the source code. New: exported Context class. Deprecated: stop using const myUpdate = newContext().update and start using const myContext = new Context(); myContext.update(...). Deprecated: stop using update.extend and start using import { extend } from 'immutability-helper' or const { extend } = new Context(). test plan: * the only thing that uses immer is the assignments_2 teacher stuff, that should still work * discussions, gradingPeriods, and the CreateOrUpdateUserModal use immutability-helper, those should still all work Change-Id: If6b62788be5d3929b5a0ddd64e1b63aa09916b84 Reviewed-on: https://gerrit.instructure.com/205773 Reviewed-by: Clay Diffrient <cdiffrient@instructure.com> Tested-by: Jenkins QA-Review: Ryan Shaw <ryan@instructure.com> Product-Review: Ryan Shaw <ryan@instructure.com>
2019-08-20 08:55:20 +08:00
"immer": "^3",
"immutability-helper": "^3",
Configurable proficiency ratings page closes OUT-1856, OUT-1858, OUT-2239, OUT-2148 This adds configurable proficiency ratings on the account rubrics page. Persisting these changes will occur in a future patchset (2252). Validating order will be in a separate patchset (2240). test plan: - with the "non-scoring rubrics" feature flag off, the account rubrics page should appear without the proficiency ratings tab - with the "non-scoring rubrics" feature flag on, the accounts rubrics page should appear with the proficiency tab, if visiting with an account with "manage_outcomes" permission (e.g. account admin) - create an account role that has "Create and edit assessing rubrics" permission enabled but "Manage learning outcomes" disabled by going to the account page, click on the "Permissions" link in the left menu, then select the "Account Roles" tab to then be able create the role and enable the permission above. - create an account user by going to the account page and then click on the "People" link in the left menu to then be able to click on "+ New User". you'll use the email address entered in the next step. - make that user an account admin by going to the account page, click on the "Settings" link in the left menu, then select the "Admins" tab, then click on "+ Account Admins". select the new role from the drop down menu and enter the email address you used in the preivous step - confirm with the feature flag enabled, that visiting the account rubrics page does not appear with the proficiency tab, if visiting with an account without "manage_outcomes" permission (e.g. masquerade as the user created above) - on the proficiency tab, test error handling: * description is required * points is required, should be a valid number * when saving changes, all fields with errors should be labelled with an error text, with the first field receiving focus Change-Id: Ic52ef9fe9c58cfb215216b3a505ef1fb4b851c68 Reviewed-on: https://gerrit.instructure.com/150841 Reviewed-by: Michael Brewer-Davis <mbd@instructure.com> Reviewed-by: Frank Murphy <fmurphy@instructure.com> Tested-by: Jenkins QA-Review: Dariusz Dzien <ddzien@instructure.com> Product-Review: Sidharth Oberoi <soberoi@instructure.com>
2018-04-10 09:20:00 +08:00
"immutable": "^3.8.2",
specify invariant import this is included in yarn.lock, and imported in various files. it should also be in package.json flag=none Change-Id: I4a16b16e750280892ac0c9b7e960036524a58055 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/335917 QA-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Product-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Reviewed-by: Michael Hulse <michael.hulse@instructure.com> Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com>
2023-12-23 07:04:13 +08:00
"invariant": "^2.2.2",
upgrade some NPM dependencies Change-Id: If2a90959713e292a46c9d5e9c75c89a37f7316b6 Reviewed-on: https://gerrit.instructure.com/205007 Tested-by: Jenkins Reviewed-by: Cameron Matheson <cameron@instructure.com> QA-Review: Ryan Shaw <ryan@instructure.com> Product-Review: Ryan Shaw <ryan@instructure.com>
2019-08-14 13:36:39 +08:00
"is-valid-domain": "^0.0.11",
upgrade to jquery 3.5 with jquery-migrate 3.4.1 (added to instructure_jquery_patches.js this time, as it wasn't being loaded soon enough for header usage in runOnEveryPageButDontBlockAnythingElse.jsx) this change also disables the assignment column resizing and reordering feature in the grid gradebook. The drag library used for this feature does not support jquery 3.x and it is a blocker refs FOO-4260 flag=none Test Plan: - Jenkins Passes [skip-crystalball] [fsc-max-nodes=18] [fsc-timeout=40] Change-Id: I56ff289813c532c98279766dbca19b9ec28c5d0c Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/341600 Product-Review: Ryan Norton <rnorton@instructure.com> QA-Review: August Thornton <august@instructure.com> Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Michael Hulse <michael.hulse@instructure.com>
2024-02-28 10:48:45 +08:00
"jquery-migrate": "3.4.1",
move things from “devDeps” to “dependencies” Closes CNVS-39744 we used to only have the things needed to compile brandable_css in “Dependencies”. This was because, when we used to have to run brandable_css on a job server when someone pressed “preview” in the theme editor, we only wanted to have the minimum amount of node_modules installed there to do that. But now that we no longer have to do any brand-specific css compiling we can just do what is considered normal and put anything that actually goes on the page in “dependencies” and leave all the build tooling, linting, etc stuff in devDependencies. This also makes it so it is really easy to see the cases that we might be loading 2 versions of something in our webpack bundles by running `yarn install --prod --flat`. Whatever that prompts you about is something that will be included more than once in our webpack bundles. Test plan: * run `yarn install` * it should not generate a new yarn.lock because everything is the same versions as before. Change-Id: I87b88f50d2cdbe494f928e5418e8540da9cc084c Reviewed-on: https://gerrit.instructure.com/128244 Tested-by: Jenkins Reviewed-by: Felix Milea-Ciobanu <fmileaciobanu@instructure.com> Reviewed-by: Clay Diffrient <cdiffrient@instructure.com> Product-Review: Ryan Shaw <ryan@instructure.com> QA-Review: Ryan Shaw <ryan@instructure.com>
2017-10-04 01:05:04 +08:00
"jquery-ui-touch-punch": "^0.2.3",
"jquery.cookie": "^1.4.1",
Update yarn/npm dependencies this will make it so we can use karma with the latest node. once the commit to upgrade d3 is merged, that was the only other thing we needed to do to have everything working on node 8. Change-Id: I820b27ee3da38818b69554c6e409a2177370ca34 Reviewed-on: https://gerrit.instructure.com/136752 Tested-by: Jenkins Reviewed-by: Brent Burgoyne <bburgoyne@instructure.com> Product-Review: Ryan Shaw <ryan@instructure.com> QA-Review: Ryan Shaw <ryan@instructure.com>
2018-01-03 06:24:44 +08:00
"jquery.elastic": "1.0.0",
patch format-message to fix CJS issue Change-Id: Id955360efbd116835f51fe48c53ff8cf221f956c Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/338375 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Michael Hulse <michael.hulse@instructure.com> QA-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Product-Review: Aaron Shafovaloff <ashafovaloff@instructure.com>
2024-01-23 07:00:30 +08:00
"jquery3": "npm:jquery@^3.7.1",
add encrypted forage for persistent graphql cache Test Plan: - Enable the apollo caching FF on siteadmin - Navigate to a discussion topic - In index db in the application tab in your dev tools you should see the key "apollo-cache-persist" and the value should be encrypted Change-Id: I7584c4ff1f50d0a324d2e2afeec6800671eea44d Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/274010 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Jeffrey Johnson <jeffrey.johnson@instructure.com> QA-Review: Jeffrey Johnson <jeffrey.johnson@instructure.com> Product-Review: Jeffrey Johnson <jeffrey.johnson@instructure.com>
2021-09-21 05:11:21 +08:00
"localforage": "^1.10.0",
get window.location.orgin polyfill from npm …instead of the copy-pasta’ed one in our repo Test plan: Make sure the files search results page works in ie11 Change-Id: I61433363eda53d44b897bf1f88837cef7c239f87 Reviewed-on: https://gerrit.instructure.com/135141 Tested-by: Jenkins Reviewed-by: Brent Burgoyne <bburgoyne@instructure.com> Product-Review: Ryan Shaw <ryan@instructure.com> QA-Review: Ryan Shaw <ryan@instructure.com>
2017-12-09 08:32:58 +08:00
"location-origin": "^1.1.4",
upgrade & dedupe node packages fixes FOO-2037 the result of removing yarn.lock and reinstalling packages according to the latest version within their specified range Change-Id: I1d2851d5a1a9fc6caeddc388492622ffd4f59379 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/255460 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Product-Review: Charley Kline <ckline@instructure.com> QA-Review: Charley Kline <ckline@instructure.com> Reviewed-by: Charley Kline <ckline@instructure.com>
2021-05-26 01:22:32 +08:00
"lodash": "^4.17.21",
move things from “devDeps” to “dependencies” Closes CNVS-39744 we used to only have the things needed to compile brandable_css in “Dependencies”. This was because, when we used to have to run brandable_css on a job server when someone pressed “preview” in the theme editor, we only wanted to have the minimum amount of node_modules installed there to do that. But now that we no longer have to do any brand-specific css compiling we can just do what is considered normal and put anything that actually goes on the page in “dependencies” and leave all the build tooling, linting, etc stuff in devDependencies. This also makes it so it is really easy to see the cases that we might be loading 2 versions of something in our webpack bundles by running `yarn install --prod --flat`. Whatever that prompts you about is something that will be included more than once in our webpack bundles. Test plan: * run `yarn install` * it should not generate a new yarn.lock because everything is the same versions as before. Change-Id: I87b88f50d2cdbe494f928e5418e8540da9cc084c Reviewed-on: https://gerrit.instructure.com/128244 Tested-by: Jenkins Reviewed-by: Felix Milea-Ciobanu <fmileaciobanu@instructure.com> Reviewed-by: Clay Diffrient <cdiffrient@instructure.com> Product-Review: Ryan Shaw <ryan@instructure.com> QA-Review: Ryan Shaw <ryan@instructure.com>
2017-10-04 01:05:04 +08:00
"md5": "^2.2.1",
Upgrade mediaelement to latest master of our fork Fixes: CORE-1091 show controls when they receive focus (#39) if controls are visibly hidden, they should still be tabbable for accessibility, and when they get keyboard-focused, they should become visible again. See: https://github.com/instructure/mediaelement/commit/0402b2b76 Change-Id: Ic655d43a64d111662f8d7368f21032664a8aee74 Reviewed-on: https://gerrit.instructure.com/142693 Tested-by: Jenkins Reviewed-by: Simon Williams <simon@instructure.com> Product-Review: Ryan Shaw <ryan@instructure.com> QA-Review: Ryan Shaw <ryan@instructure.com>
2018-03-07 00:03:37 +08:00
"mediaelement": "https://github.com/instructure/mediaelement.git#master",
replace mime-types package with mime - ESM compatible - Built-in Typescript types flag=none refs CFA-32 Change-Id: I97acf576dc14151fc00a870765cdc19926426e10 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/336024 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Cameron Ray <cameron.ray@instructure.com> Product-Review: Cameron Ray <cameron.ray@instructure.com> QA-Review: Aaron Shafovaloff <ashafovaloff@instructure.com>
2023-12-28 23:30:36 +08:00
"mime": "^4.0.1",
include minimatch in main package.json Change-Id: I3661ac887967c3d6a4b13ba93262f79c9bb1f2cb Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/336040 Reviewed-by: Michael Hulse <michael.hulse@instructure.com> QA-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Product-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com>
2023-12-30 07:08:03 +08:00
"minimatch": "~3.0.4",
Upgrade moment Change-Id: Iafdd31a8c02a5918c6b68c234df661ed90d24032 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/335007 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Drake Harper <drake.harper@instructure.com> Product-Review: Drake Harper <drake.harper@instructure.com> QA-Review: Aaron Shafovaloff <ashafovaloff@instructure.com>
2023-12-10 22:40:44 +08:00
"moment": "^2.29.4",
update moment-timezone to 0.5.45 refs FOO-4337 flag=none Change-Id: I31de7c11d645e92dd624a01788693bb3c748abbe Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/344219 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> QA-Review: Ajmal Esa <ajmal.esa@instructure.com> Product-Review: Ajmal Esa <ajmal.esa@instructure.com> Reviewed-by: August Thornton <august@instructure.com>
2024-04-02 07:14:18 +08:00
"moment-timezone": "^0.5.45",
Change inbox avatar to use inst-ui Test Plan: -inspect avatar on inbox message is rendered from inst-ui fixes VICE-17 flag=none Change-Id: I92941e079b63a3a60468e1e894059c20e15b1251 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/241435 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Jeffrey Johnson <jeffrey.johnson@instructure.com> QA-Review: Jeffrey Johnson <jeffrey.johnson@instructure.com> Product-Review: Jeffrey Johnson <jeffrey.johnson@instructure.com>
2020-06-30 02:23:26 +08:00
"nanoid": "^3.1.10",
Backport instUI fix to allow themeable w/ `class`es We made this change in @instructure/ui-themeable in g/203714 but that is for the current master on instUI 6, we need it now even though we are still on instUI 5 so this will back port it in so we can use it now. Test plan: * Things that use `themeable` should work both with and without the “Drop ie11” commit applied. Specifically: bin/rspec ./spec/selenium/dashboard/planner/student_planner_assignments_spec.rb:88 Should not fail with TypeError: Class constructor Yr cannot be invoked without 'new' Change-Id: I7ef8ef9eda1057badabbb08fcdd6875ad8064e89 Reviewed-on: https://gerrit.instructure.com/203950 Reviewed-by: Steven Burnett <sburnett@instructure.com> QA-Review: Steven Burnett <sburnett@instructure.com> Tested-by: Jenkins Product-Review: Ryan Shaw <ryan@instructure.com>
2019-08-06 06:43:39 +08:00
"newless": "^0.3.0",
upgrade some NPM dependencies Change-Id: If2a90959713e292a46c9d5e9c75c89a37f7316b6 Reviewed-on: https://gerrit.instructure.com/205007 Tested-by: Jenkins Reviewed-by: Cameron Matheson <cameron@instructure.com> QA-Review: Ryan Shaw <ryan@instructure.com> Product-Review: Ryan Shaw <ryan@instructure.com>
2019-08-14 13:36:39 +08:00
"normalize-scroll-left": "^0.2",
files: turn off page.js click handler because it prevents preventDefault on file links (sometimes) then use it explicitly where we need it, on the left/right preview buttons test plan: - go to user files (/files) - have multiple image files in a folder - reload the page, then click an image file - it should preview, not download - clicking the left/right arrows at the side of the preview window should go to the previous/next image without reloading the page fixes ADMIN-2923 Change-Id: Ib97d25d51e7c94fb962e5d24d3c763554e7fcdd4 Reviewed-on: https://gerrit.instructure.com/212876 Tested-by: Jenkins Reviewed-by: Clay Diffrient <cdiffrient@instructure.com> QA-Review: Carl Kibler <ckibler@instructure.com> Product-Review: Jeremy Stanley <jeremy@instructure.com>
2019-10-11 22:32:01 +08:00
"page": "^1.11",
update parse-decimal-number to 1.0.0 A hack can be removed for parsing numbers now that 1.0.0 incorporates the needed behavior. test plan: * verify Jenkins passes Change-Id: Ifaea8fd348f4f804e9a6042fb392c699badeea6e Reviewed-on: https://gerrit.instructure.com/138046 Tested-by: Jenkins Reviewed-by: Derek Bender <djbender@instructure.com> Reviewed-by: Ryan Shaw <ryan@instructure.com> Product-Review: Jeremy Neander <jneander@instructure.com> QA-Review: Jeremy Neander <jneander@instructure.com>
2018-01-17 00:52:42 +08:00
"parse-decimal-number": "1.0.0",
Put parse-link-header back in package.json …since we use it in our code It used to be there, but somehow someone deleted it on accident Change-Id: Id516fdb8507887ffed9450869654fc42a4afc415 Reviewed-on: https://gerrit.instructure.com/151898 Reviewed-by: Steven Burnett <sburnett@instructure.com> Tested-by: Jenkins Product-Review: Ryan Shaw <ryan@instructure.com> QA-Review: Ryan Shaw <ryan@instructure.com>
2018-05-31 02:03:31 +08:00
"parse-link-header": "^1",
[npm dependencies] update all our npm dependencies This is just the regular “update all the things” commit. For things in package.json that we just want the latest version of, I changed them to a simple major with a carat. (Eg: “8^” or “4^”), that way you can see easier which things are specifically locked down To a specific version (or range of versions) for a reason. Test plan: * automated specs & build tasks should work Change-Id: Id7a3f853bd0f7537cc0f08d7dba8d6726b836c44 Reviewed-on: https://gerrit.instructure.com/141653 Tested-by: Jenkins Reviewed-by: Brent Burgoyne <bburgoyne@instructure.com> QA-Review: Brent Burgoyne <bburgoyne@instructure.com> Product-Review: Brent Burgoyne <bburgoyne@instructure.com>
2018-02-23 03:58:38 +08:00
"prop-types": "^15",
update qs dependency test plan: * Verify Jenkins passes? Change-Id: If472d2f898e4241d0d10dfd7f1ca5094ecf9d811 Reviewed-on: https://gerrit.instructure.com/184039 Tested-by: Jenkins Reviewed-by: KC Naegle <knaegle@instructure.com> Reviewed-by: Cody Cutrer <cody@instructure.com> QA-Review: Anju Reddy <areddy@instructure.com> Product-Review: Jeremy Neander <jneander@instructure.com>
2019-03-07 00:43:35 +08:00
"qs": "^6.6.0",
Begin SideNav implementation Test plan: - localStorage.instui_nav_dev = 'true' - visit /accounts/ - click on an account - the SideBar component should show flag=none refs FOO-3868 Change-Id: I0528dc0411a63d700905c7f8780e214585f0397a Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/328629 Reviewed-by: Michael Hulse <michael.hulse@instructure.com> Reviewed-by: Charley Kline <ckline@instructure.com> QA-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Product-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com>
2023-09-26 03:20:00 +08:00
"react": "^16.13.1",
upgrade & dedupe node packages fixes FOO-2037 the result of removing yarn.lock and reinstalling packages according to the latest version within their specified range Change-Id: I1d2851d5a1a9fc6caeddc388492622ffd4f59379 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/255460 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Product-Review: Charley Kline <ckline@instructure.com> QA-Review: Charley Kline <ckline@instructure.com> Reviewed-by: Charley Kline <ckline@instructure.com>
2021-05-26 01:22:32 +08:00
"react-apollo": "~3.0.1",
drag and drop rubric criteria and ratings closes EVAL-3635 flag=enhanced_rubrics Test Plan: - Create a new rubric - Add a criteria with some ratings - ensure you can add and drag around the ratings to different indexes, but the point values stay fixed on the left. - ensure you can save the criteria and edit it again and the order and ratings are preserved. - Also ensure that when the long description is two long the box expands, but everything in the rating row is aligned vertically(center). - ensure when dragging around ratings that the add rating button is hidden when dragging and reappears when you stop dragging. -ensure the saved rating order is also correctly displayed on the criteria index page. - ensure you can also drag around the criteria themselves and the points and ratings move with them. Change-Id: I08fe4d9a09933509deefed0fb62523068a38ad5a Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/341590 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Derek Williams <derek.williams@instructure.com> QA-Review: Christopher Soto <christopher.soto@instructure.com> Product-Review: Ravi Koll <ravi.koll@instructure.com>
2024-02-27 09:04:10 +08:00
"react-beautiful-dnd": "^13.1.1",
Upgrade react-dnd to v6.0 I tried v7.5.0, the last version before the api became soley react hook based, but it didn't work closes LF-46 flag=none test plan: - you can drag cards around on the card dashbaord - you can drag discussions around on the /discussion_topics page - check Mastery Paths in course settings - create a couple assignments - edit an assignmenet and go to the Mastery Paths tab - put a couple assignments in there - you can drag assignments between sections - you can drag an assignment on top of another and they will be joined together - you can drag them apart Change-Id: Iedf956e45ebd995e6b30e7df0a993bffb3a96f4f Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/327233 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Robin Kuss <rkuss@instructure.com> QA-Review: Robin Kuss <rkuss@instructure.com> Product-Review: Ed Schiebel <eschiebel@instructure.com>
2023-09-09 00:29:10 +08:00
"react-dnd": "6.0",
Begin SideNav implementation Test plan: - localStorage.instui_nav_dev = 'true' - visit /accounts/ - click on an account - the SideBar component should show flag=none refs FOO-3868 Change-Id: I0528dc0411a63d700905c7f8780e214585f0397a Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/328629 Reviewed-by: Michael Hulse <michael.hulse@instructure.com> Reviewed-by: Charley Kline <ckline@instructure.com> QA-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Product-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com>
2023-09-26 03:20:00 +08:00
"react-dnd-html5-backend": "6.0",
upgrade & dedupe node packages fixes FOO-2037 the result of removing yarn.lock and reinstalling packages according to the latest version within their specified range Change-Id: I1d2851d5a1a9fc6caeddc388492622ffd4f59379 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/255460 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Product-Review: Charley Kline <ckline@instructure.com> QA-Review: Charley Kline <ckline@instructure.com> Reviewed-by: Charley Kline <ckline@instructure.com>
2021-05-26 01:22:32 +08:00
"react-dom": "^16.13.1",
Refactor EditGroupModal with react-final-form closes OUT-4312 flag = improved_outcomes_management Test plan: - Try to edit a group using Improved Outcomes Management and make sure no functionality was broken Change-Id: Ic7f7cf77189b7688187cfd530325aecc393a92c0 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/261655 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Pat Renner <prenner@instructure.com> QA-Review: Brian Watson <bwatson@instructure.com> Product-Review: Augusto Callejas <acallejas@instructure.com>
2021-03-26 00:11:03 +08:00
"react-final-form": "^6.5.3",
create anonymous discussion avatar identicons fixes VICE-2280 flag=discussion_anonymity Test Plan: - Open storybook - Navigate to the anonymous avatar component - Note that changing the seed string generates a new identicon avatar Change-Id: I13624cc0a86d435780b9d96c21cdcd91993a5333 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/280191 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Omar Soto-Fortuño <omar.soto@instructure.com> QA-Review: Omar Soto-Fortuño <omar.soto@instructure.com> Product-Review: Omar Soto-Fortuño <omar.soto@instructure.com>
2021-12-03 05:07:31 +08:00
"react-identicons": "^1.2.5",
fix expand/contract all buttons in new sLMGB closes OUT-2232 Test plan: - enable non-scoring rubrics - load student LMGB with multiple outcome groups, outcomes, and outcome results - verify that expanding and contracting the groups and outcomes works as expected - verify that after contracting a group and then re-expanding, the outcomes within the group are contracted - verify that the expand all and contract all buttons at the top of the page are enabled and disabled at the appropriate times - expand all: should be enabled when any element is contracted - contract all: should be enabled when any element is expanded - verify that the expand all/contract all buttons work as expected Change-Id: Ifbe02e900459faed8d411afb2bb9410a885a2237 Reviewed-on: https://gerrit.instructure.com/152103 Tested-by: Jenkins Reviewed-by: Matt Berns <mberns@instructure.com> Reviewed-by: Frank Murphy <fmurphy@instructure.com> QA-Review: Dariusz Dzien <ddzien@instructure.com> Product-Review: Sidharth Oberoi <soberoi@instructure.com>
2018-06-01 05:13:10 +08:00
"react-immutable-proptypes": "^2.1.0",
Upgrade react-lazy-load to v4.0.1 refs LS-3841 flag = none Test plan: specs pass Change-Id: I3cba7bea13041731e993cfc531273abf433c4cbf Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/314518 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Davis Hyer <dhyer@instructure.com> QA-Review: Davis Hyer <dhyer@instructure.com> Product-Review: Davis Hyer <dhyer@instructure.com>
2023-03-29 08:40:46 +08:00
"react-lazy-load": "^4.0.1",
Upgrade react-modal so it works with react 16 I know I said that the way forward was to just not use react-modal and use instUI modal instead but there are a bunch of things that _are_ Using it and I don’t want changing all those to be blockers for react16 if this will work. I still want us to get rid of react-modal, just don’t want it to be a blocker for react 16 Test plan: Things that use react-modal should still work the same as before. Check: * the color picker used on the calendar sidebar * the external apps stuff that has modals * the file preview modal in files * the “find appointment” modal in scheduler Change-Id: I606eda110782cd3300fcbb2f8052681fa5048050 Reviewed-on: https://gerrit.instructure.com/164232 Tested-by: Jenkins Reviewed-by: Steven Burnett <sburnett@instructure.com> Product-Review: Ryan Shaw <ryan@instructure.com> QA-Review: Ryan Shaw <ryan@instructure.com>
2018-09-13 03:05:43 +08:00
"react-modal": "^3",
Position and mount Mentions component refs VICE-1683 Test Plan 1. Enable Mentions Flag and Discussion Redesign Flag 2. Open Discussions and open an RCE 3. Type some text and then the @ symbol. 4. Notice, the menu should be positioned under the @ symbol populated with dummy data names (for now) Note: There is no filtering, selecting, or simple way to escape at the moment and will be coming in future reviews. Change-Id: Icd8fa583004db77313f3fb188933d1a202ef2e0c Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/269684 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Matthew Lemon <mlemon@instructure.com> QA-Review: Matthew Lemon <mlemon@instructure.com> Product-Review: Matthew Lemon <mlemon@instructure.com>
2021-07-12 09:26:47 +08:00
"react-popper": "^2.2.5",
Update react-redux to 5.1.1 test plan: - automated tests pass Change-Id: I6c1034ec8f443d10d39b5b551c1b7207e5191411 Reviewed-on: https://gerrit.instructure.com/173814 Tested-by: Jenkins Product-Review: Clay Diffrient <cdiffrient@instructure.com> Reviewed-by: Brent Burgoyne <bburgoyne@instructure.com> QA-Review: Tucker Mcknight <tmcknight@instructure.com>
2018-11-30 08:54:31 +08:00
"react-redux": "^5.1.1",
Consolidate browser router test plan: - Ensure that Account Grading Settings tabs still work - Ensure that "Act as..." page still works - Ensure that group dropdown in Student Groups pages still renders flag=none Change-Id: If04a5faab051fab7301f0550637fd9ae489b58e8 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/328746 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Charley Kline <ckline@instructure.com> QA-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Product-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Build-Review: James Butters <jbutters@instructure.com>
2023-09-27 04:30:51 +08:00
"react-router-dom": "^6.16.0",
upgrade react-token-input so it supports react 16 closes: CORE-1885 Test plan: * make sure the token input that appears when you edit assignment due date Overrides on the assignment overrides page still works Like it did before. Here’s it’s original test plan: new due dates selection UI - on assignments, quizzes & discussions pages - with DA on and off - assign various due dates/(un)lock dates to source sections, individuals, and everybody - these should create overrides that properly take students/sections and dates - validations should work for all dates as normal and not let empty overrides get created (with no students or sections) - the names of overrides should properly update as students change - as more overrides get created, saving assignments should not slow down significantly - the student/section selector should be intuitive * the “new grading period set” form should work as it did before. Here’s it’s original test plan: A new button "+ Add Grading Period Set" is on the Grading Period Sets page. This allows a new set to be named and associated with as many terms as needed. To begin, visit the Grading page for an account (e.g. /accounts/1/grading_standards) and click "+ Set of Grading Period" and within this form ensure the following: 1. Given no name in the "Set name" field, when clicking the "Create" button a flash message is displayed and the set is not saved 2. Given no enrollment terms in the "Attach terms", when clicking the "Create" button a flash message is displayed and the set is not saved 3. Given a name and at least one attached enrollment term, when clicking the "Create" button an AJAX call successfully persists to the database and the new set is displayed on the page along with a successful flash message 4. When the form is open, the "+ Set of Grading Periods" button is disabled 5. When the form is in the process of creating a new set, the "Create" and "Cancel" button is disabled 6. Clicking close at any other time closes the form and re-enables the "+ Set of Grading Periods" button and all data in the form is cleared Change-Id: Ibb0290202b5dcf00ec42a4bb6d1c3d2e3d7a3b2b Reviewed-on: https://gerrit.instructure.com/164492 Reviewed-by: Clay Diffrient <cdiffrient@instructure.com> Tested-by: Jenkins Product-Review: Ryan Shaw <ryan@instructure.com> QA-Review: Ryan Shaw <ryan@instructure.com>
2018-09-14 23:20:08 +08:00
"react-tokeninput": "^2.5.0",
bump npm-run-all version Change-Id: Ieae7ac480124e52050c79ca83c99a7fe698c48d5 Reviewed-on: https://gerrit.instructure.com/173262 Reviewed-by: Clay Diffrient <cdiffrient@instructure.com> Tested-by: Jenkins QA-Review: Gary Mei <gmei@instructure.com> Product-Review: Gary Mei <gmei@instructure.com>
2018-11-27 02:20:33 +08:00
"react-transition-group": "^1",
Add option to embed K5 subject view in a hybrid manner This change adds an `embed` param to the K5 subject `show` action that, when set to `true`, hides global nav, the K5 Hero header, and the K5 tab bar. Navigation between tabs is still possible by changing the hash fragment at the end of the URL. closes LS-2590 flag=none test plan: - browse to a k5 subject - append `?embed=true` to the URL - verify that the global nav and subject tabs disappear - navigate between different subject tabs by modifying the hash fragment at the end of the URL (#home, #grades, #modules, #resources, #groups, #schedule) - verify that the content changes appropriately - remove `embed=true`, and click between the subject tabs - verify that navigation in non-embed mode still works correctly Change-Id: I9a3bbdf4e5d4fd4da5e98bd8c85133ff2498cefb Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/273352 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Nate Armstrong <narmstrong@instructure.com> QA-Review: Nate Armstrong <narmstrong@instructure.com> Product-Review: Isaac Moore <isaac.moore@instructure.com>
2021-09-28 03:46:18 +08:00
"react-use": "^17.3.1",
Begin SideNav implementation Test plan: - localStorage.instui_nav_dev = 'true' - visit /accounts/ - click on an account - the SideBar component should show flag=none refs FOO-3868 Change-Id: I0528dc0411a63d700905c7f8780e214585f0397a Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/328629 Reviewed-by: Michael Hulse <michael.hulse@instructure.com> Reviewed-by: Charley Kline <ckline@instructure.com> QA-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Product-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com>
2023-09-26 03:20:00 +08:00
"redux": "^4.0.1",
Update redux-actions to 2.6.4 test plan: - automated tests pass Change-Id: I82969f661e78370c8a2f9035c2bca7d2397fb377 Reviewed-on: https://gerrit.instructure.com/173815 Tested-by: Jenkins Product-Review: Clay Diffrient <cdiffrient@instructure.com> Reviewed-by: Brent Burgoyne <bburgoyne@instructure.com> QA-Review: Tucker Mcknight <tmcknight@instructure.com>
2018-11-30 08:57:55 +08:00
"redux-actions": "^2.6.4",
move planner to ui/shared test plan: - smoke test of planner - build passes flag=none Change-Id: I1ccab60a53269adaa4247658696ee080e4e03fae Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/323860 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> QA-Review: Caleb Guanzon <cguanzon@instructure.com> QA-Review: Michael Hulse <michael.hulse@instructure.com> Product-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Reviewed-by: Ed Schiebel <eschiebel@instructure.com>
2023-07-29 01:57:25 +08:00
"redux-promise": "^0.6",
"redux-saga": "^0.16.0",
upgrade redux-thunk flag=none closes CFA-30 Change-Id: Ibdca0a4d89e2b82859dfc551227bbfe53bad0131 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/335971 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Michael Hulse <michael.hulse@instructure.com> Reviewed-by: Jackson Huang <jackson.huang@instructure.com> QA-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Product-Review: Aaron Shafovaloff <ashafovaloff@instructure.com>
2023-12-26 20:07:15 +08:00
"redux-thunk": "^3.1.0",
Initial pace plans import This change brings in the basic pace plans frontend with styled-components and several other smaller libraries replaced with InstUI 7 components. It also adds the 'reselect' library as a direct dependency (which we already had through @instructure/outcomes-ui) and 'tsc-files' for type-checking of staged TS files on commit. There were also some tweaks to typescript and eslint configs, mostly to get both up to speed with the typescript code. Finally, this also adds a `pace_plans` endpoint to `courses_controller` to bootstrap the frontend-- this will get moved to `pace_plans_controller` once it has been merged. It's also worth noting that no frontend tests are included with this change-- the existing tests were written with enzyme and are heavily snapshot-based, so we will be replacing those with @testing-library/react tests in later updates (in keeping with current testing best practices at Instructure). closes LS-2431, LS-2432, LS-2433, LS-2434, LS-2452 flag = pace_plans Test plan: - Set up a course with at least one module and several module items - Turn on the pace_plans feature flag in the account associated with that course - Turn on the "Enable pace plans" setting in course settings - Create a pace plan for the course via the Rails console: c = Course.find<id> pp = c.pace_plans.create! workflow_state: 'active' c.context_module_tags.each_with_index do |t, i| pp.pace_plan_module_items.create! module_item: t, duration: i*2 end - Go to the course as a teacher or admin - Expect to see a "Pace Plans" link in the course navigation - Click it, expect the pace plan you created earlier to load and render - Expect to be able to pick dates, change durations, and toggle checkboxes (although saves will fail, since there is no API yet). - Expect to not see the "Pace Plans" course nav link when the feature flag or course setting is off - Expect /courses/<id>/pace_plans to return a 404 when the feature flag or course setting is off - Expect to not see the "Pace Plans" course nav link as a student - Expect /courses/<id>/pace_plans to display an "Unauthorized" page as a student Change-Id: If4dc5d17f2c6a2109d4b4cb652c9e9ef00d7cc33 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/271650 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Ed Schiebel <eschiebel@instructure.com> QA-Review: Ed Schiebel <eschiebel@instructure.com> Product-Review: Jeff Largent <jeff.largent@instructure.com>
2021-08-18 05:14:24 +08:00
"reselect": "^4.0.0",
replace webpack with rspack test plan: - run rspack locally (as "webpack" for now) - ensure coverage data for crystalball - ensure build passes with skip-crystalball - ensure source maps for local dev - ensure bundle analysis is available and documented - ensure compile times are at least comparable refs CFA-32 [skip-crystalball] flag=none Change-Id: I8ad916ac7fbe9e3ecee5c690abcd78cdde748ab6 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/339401 Reviewed-by: Isaac Moore <isaac.moore@instructure.com> Build-Review: Isaac Moore <isaac.moore@instructure.com> Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> QA-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Product-Review: Aaron Shafovaloff <ashafovaloff@instructure.com>
2024-02-01 04:19:23 +08:00
"rspack-manifest-plugin": "^5.0.0-alpha0",
direct share user selection modal closes ADMIN-2839 flag=direct_share test plan: - as a user with course management permissions (such as a teacher) go to the discussions index page and select "Send To..." from a discussion's kabob menu. - this should open a modal where you can search for and select other course users who have course management permissions. - clicking on the "Send" button only does a console log at the moment. Change-Id: I67f823d0820283fd90e2aa6e3ae3ea5fe54d9b3d Reviewed-on: https://gerrit.instructure.com/205967 Tested-by: Jenkins Reviewed-by: Carl Kibler <ckibler@instructure.com> QA-Review: Carl Kibler <ckibler@instructure.com> Product-Review: Jon Willesen <jonw+gerrit@instructure.com>
2019-08-21 07:12:19 +08:00
"shallow-equal": "^1.2.0",
move things from “devDeps” to “dependencies” Closes CNVS-39744 we used to only have the things needed to compile brandable_css in “Dependencies”. This was because, when we used to have to run brandable_css on a job server when someone pressed “preview” in the theme editor, we only wanted to have the minimum amount of node_modules installed there to do that. But now that we no longer have to do any brand-specific css compiling we can just do what is considered normal and put anything that actually goes on the page in “dependencies” and leave all the build tooling, linting, etc stuff in devDependencies. This also makes it so it is really easy to see the cases that we might be loading 2 versions of something in our webpack bundles by running `yarn install --prod --flat`. Whatever that prompts you about is something that will be included more than once in our webpack bundles. Test plan: * run `yarn install` * it should not generate a new yarn.lock because everything is the same versions as before. Change-Id: I87b88f50d2cdbe494f928e5418e8540da9cc084c Reviewed-on: https://gerrit.instructure.com/128244 Tested-by: Jenkins Reviewed-by: Felix Milea-Ciobanu <fmileaciobanu@instructure.com> Reviewed-by: Clay Diffrient <cdiffrient@instructure.com> Product-Review: Ryan Shaw <ryan@instructure.com> QA-Review: Ryan Shaw <ryan@instructure.com>
2017-10-04 01:05:04 +08:00
"spin.js": "2.3.2",
replace babel with swc in canvas-lms test plan: - build passes - ensure bundles are not much larger - canvas still works in dev environment - smoke test in Safari - smoke test in Firefox closes CFA-38 flag=none [skip-crystalball] Change-Id: I7879b1e7274b9ce47c3aa1985a6a22e5e3659f25 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/337103 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Isaac Moore <isaac.moore@instructure.com> Build-Review: Isaac Moore <isaac.moore@instructure.com> QA-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Product-Review: Aaron Shafovaloff <ashafovaloff@instructure.com>
2024-01-09 12:16:28 +08:00
"swc-loader": "^0.2.3",
install swc-coverage-instrument Change-Id: I96bc976f89c6906e7ab35d90fa6915f6eec4b963 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/337269 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Michael Hulse <michael.hulse@instructure.com> QA-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Product-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Build-Review: Isaac Moore <isaac.moore@instructure.com>
2024-01-11 06:43:31 +08:00
"swc-plugin-coverage-instrument": "^0.0.20",
move things from “devDeps” to “dependencies” Closes CNVS-39744 we used to only have the things needed to compile brandable_css in “Dependencies”. This was because, when we used to have to run brandable_css on a job server when someone pressed “preview” in the theme editor, we only wanted to have the minimum amount of node_modules installed there to do that. But now that we no longer have to do any brand-specific css compiling we can just do what is considered normal and put anything that actually goes on the page in “dependencies” and leave all the build tooling, linting, etc stuff in devDependencies. This also makes it so it is really easy to see the cases that we might be loading 2 versions of something in our webpack bundles by running `yarn install --prod --flat`. Whatever that prompts you about is something that will be included more than once in our webpack bundles. Test plan: * run `yarn install` * it should not generate a new yarn.lock because everything is the same versions as before. Change-Id: I87b88f50d2cdbe494f928e5418e8540da9cc084c Reviewed-on: https://gerrit.instructure.com/128244 Tested-by: Jenkins Reviewed-by: Felix Milea-Ciobanu <fmileaciobanu@instructure.com> Reviewed-by: Clay Diffrient <cdiffrient@instructure.com> Product-Review: Ryan Shaw <ryan@instructure.com> QA-Review: Ryan Shaw <ryan@instructure.com>
2017-10-04 01:05:04 +08:00
"swfobject": "^2.2.1",
"tablesorter": "^2.28.5",
update timezone library to 1.0.29 refs FOO-4337 flag=none Change-Id: Id5334e9282bcc3516eb00d3718a08ffd670d8e42 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/344220 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> QA-Review: Ajmal Esa <ajmal.esa@instructure.com> Product-Review: Ajmal Esa <ajmal.esa@instructure.com> Reviewed-by: August Thornton <august@instructure.com>
2024-04-02 07:50:33 +08:00
"timezone": "npm:@instructure/timezone@1.0.29",
move things from “devDeps” to “dependencies” Closes CNVS-39744 we used to only have the things needed to compile brandable_css in “Dependencies”. This was because, when we used to have to run brandable_css on a job server when someone pressed “preview” in the theme editor, we only wanted to have the minimum amount of node_modules installed there to do that. But now that we no longer have to do any brand-specific css compiling we can just do what is considered normal and put anything that actually goes on the page in “dependencies” and leave all the build tooling, linting, etc stuff in devDependencies. This also makes it so it is really easy to see the cases that we might be loading 2 versions of something in our webpack bundles by running `yarn install --prod --flat`. Whatever that prompts you about is something that will be included more than once in our webpack bundles. Test plan: * run `yarn install` * it should not generate a new yarn.lock because everything is the same versions as before. Change-Id: I87b88f50d2cdbe494f928e5418e8540da9cc084c Reviewed-on: https://gerrit.instructure.com/128244 Tested-by: Jenkins Reviewed-by: Felix Milea-Ciobanu <fmileaciobanu@instructure.com> Reviewed-by: Clay Diffrient <cdiffrient@instructure.com> Product-Review: Ryan Shaw <ryan@instructure.com> QA-Review: Ryan Shaw <ryan@instructure.com>
2017-10-04 01:05:04 +08:00
"tinycolor2": "1.4.1",
Replace our homegrown link finder with twitter-text While I am at it, decaffinate and typescriptify TextHelper fixes FOO-2987 Change-Id: I0b8f33a610bee737ea79ad24d8aec8f8e8051c49 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/299013 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: August Thornton <august@instructure.com> Product-Review: August Thornton <august@instructure.com> QA-Review: Jacob Burroughs <jburroughs@instructure.com> Build-Review: Bobby Buten <bobby.buten@instructure.com>
2022-08-18 23:44:07 +08:00
"twitter-text": "^3.1.0",
removes underscore-lodash shim temporarily includes real underscore for those that use require('underscore') in custom JS flag=none closes CFA-33 Change-Id: I62e10b7c4ab3bed67484ae98a729b6e7d381ed08 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/337045 Reviewed-by: Paul Gray <paul.gray@instructure.com> Reviewed-by: Drake Harper <drake.harper@instructure.com> Build-Review: Aaron Ogata <aogata@instructure.com> QA-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Product-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com>
2024-01-09 03:13:14 +08:00
"underscore": "^1.13.6",
basic direct share course selection tray Note: There appears to be an issue with VoiceOver not announcing the aria live updates. Going to ignore this for now and see if it is still a problem when InstUI 6 lands. Another ticket will be created to check and fix. refs ADMIN-2811 flag=direct_share test plan: - should be able to search by name for courses you manage in the direct share course selection tray. - copy button disabled until you select a course - after selecting a course, the copy button just logs to the console - cancel button closes the tray - generally accessible, except for VO reading alerts. - could check the flash_screenreader_holder div in the inspector if you want to watch the DOM changes that should trigger the alert. Change-Id: I5c102b25d277204a9929f780adbe94b9d3e46bcb Reviewed-on: https://gerrit.instructure.com/205371 Tested-by: Jenkins QA-Review: Anju Reddy <areddy@instructure.com> Product-Review: Jon Willesen <jonw+gerrit@instructure.com> Reviewed-by: Carl Kibler <ckibler@instructure.com>
2019-08-16 04:39:59 +08:00
"use-debounce": "^3",
Add use-media-set responsive React hook to package.json Refs USERS-549 flag=none This will be used in places where responsive components may have performance issues due to complexity. Test plan: * build passes Change-Id: Icce432352b5eb5118fc258b7c2f0e3c730eaae86 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/236255 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Pat Renner <prenner@instructure.com> Reviewed-by: Augusto Callejas <acallejas@instructure.com> QA-Review: Charley Kline <ckline@instructure.com> Product-Review: Charley Kline <ckline@instructure.com>
2020-04-30 23:40:56 +08:00
"use-media-set": "^1.1",
Fix root unable to run npx deduplicate-yarn refs MAT-241 flag=none Test Plan: - docker-compose run --rm -u 0 web bash - verify "yarn dedupe-yarn" succeeds Change-Id: I517a420724aa548e294920da8ed93464cb744077 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/276051 Reviewed-by: August Thornton <august@instructure.com> Product-Review: August Thornton <august@instructure.com> QA-Review: August Thornton <august@instructure.com> Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com>
2021-10-16 00:46:44 +08:00
"uuid": "^3.2.1",
move planner to ui/shared test plan: - smoke test of planner - build passes flag=none Change-Id: I1ccab60a53269adaa4247658696ee080e4e03fae Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/323860 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> QA-Review: Caleb Guanzon <cguanzon@instructure.com> QA-Review: Michael Hulse <michael.hulse@instructure.com> Product-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Reviewed-by: Ed Schiebel <eschiebel@instructure.com>
2023-07-29 01:57:25 +08:00
"velocity-animate": "^1.5.0",
Auto-retry chunk load failures Uses the webpack-retry-chunk-load-plugin module Test plan: - Use the chunk URL feature in devtools to block a chunk - Reload the page - Unblock the chunk URL before webpack stops trying to reload it Refs EVAL-2053 flag=none Change-Id: I7bbc0374183f300c8ce96a258cef48c56c594f06 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/311956 QA-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Reviewed-by: Isaac Moore <isaac.moore@instructure.com> Reviewed-by: Christopher Soto <christopher.soto@instructure.com> Reviewed-by: Spencer Olson <solson@instructure.com> Reviewed-by: Drake Harper <drake.harper@instructure.com> Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Build-Review: Isaac Moore <isaac.moore@instructure.com> Product-Review: Cameron Ray <cameron.ray@instructure.com>
2023-02-25 02:33:43 +08:00
"webpack-retry-chunk-load-plugin": "^3.1.1",
Create, update, delete enhanced filters Test plan: - With the enhanced gradebook filters flag enabled - Create an ad hoc filter and do not press Save - When applied, the filter should take effect - Reload the page - The adhoc filter should no long appear - Create, apply, and save a filter - The filter should take effect - Reload the page - The saved filter should still appear and apply - Create, apply, and save a filter - Delete the filter - Reload the page - The adhoc filter should no long appear To do in subsequent commit: - More exact conformity to designs with save and rename UI flag=enhanced_gradebook_filters Closes EVAL-2171 Closes EVAL-2172 Closes EVAL-2173 Refs EVAL-1934 Change-Id: Id1c5be631b37e77e7a2f9a3bdd05d366ca44952f Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/283572 Reviewed-by: Eduardo Escobar <eduardo.escobar@instructure.com> Reviewed-by: Spencer Olson <solson@instructure.com> QA-Review: Eduardo Escobar <eduardo.escobar@instructure.com> Product-Review: Jody Sailor Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com>
2022-01-28 02:10:56 +08:00
"yarn-deduplicate": "^3.0.1",
install zod closes CFA-8 Change-Id: I65791dfa6bbe1d823bc1518d0b1b6955a0c432b2 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/337240 Reviewed-by: Omar Soto-Fortuño <omar.soto@instructure.com> Reviewed-by: Keith Garner <kgarner@instructure.com> QA-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Product-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com>
2024-01-11 02:50:03 +08:00
"zod": "^3.22.4",
upgrade msw flag=none closes CFA-35 closes LF-1117 Change-Id: I42e65f70ee74a2931a0a4439a4c9c0f22466ef62 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/336892 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Caleb Guanzon <cguanzon@instructure.com> Product-Review: Caleb Guanzon <cguanzon@instructure.com> QA-Review: Aaron Shafovaloff <ashafovaloff@instructure.com>
2024-01-08 09:23:15 +08:00
"zustand": "3.7.2"
move napa from "devDependencies" to "dependencies" Change-Id: I4dde9458868cd5c1c41b921414dff4b3dc9371de Reviewed-on: https://gerrit.instructure.com/29878 Reviewed-by: Simon Williams <simon@instructure.com> Reviewed-by: Jason Madsen <jmadsen@instructure.com> Product-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> QA-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Tested-by: Aaron Shafovaloff <ashafovaloff@instructure.com>
2014-02-11 02:29:11 +08:00
},
AMD Conversion "Trivial" JavaScript / CoffeeScript changes -------------------------------------------------- For the most part, all javascript was simply wrapped in `require` or `define`. The dependencies were found with a script that matched regexes in the files, it errs on the side of listing too many dependencies, so its worth double checking each file's dependencies (over time, anyway). i18n API changes -------------------------------------------------- No longer have to do I18n.scoped calls, just list i18n as a dependency with the scope and it's imported already scoped require ['i18n!some_scope'], (I18n) -> I18n.t 'im_scoped', 'I'm scoped!' JS bundling now done with r.js, not Jammit -------------------------------------------------- We don't use jammit to bundle JS anymore. Simply list dependencies for your JS modules in the file and RequireJS handles the rest. To optimize the JavaScript, first make sure you have node.js 0.4.12+ installed and then run: $ rake js:build The app defaults to the optimized build in production. You can use non-optimized in production by putting ?debug_assets=true in the url just like before. You can also test the optimized JavaScript in development with ?optimized_js=true. Significant changes -------------------------------------------------- These files have "real" changes to them (unlike the JavaScript that is simply wrapped in require and define). Worth taking a really close look at: - app/helpers/application_helper.rb - app/views/layouts/application.html.erb - config/assets.yml - config/build.js - lib/handlebars/handlebars.rb - lib/i18n_extraction/js_extractor.rb - lib/tasks/canvas.rake - lib/tasks/i18n.rake - lib/tasks/js.rake Change-Id: I4bc5ecb1231f331aaded0fef2bcc1f3a9fe482a7 Reviewed-on: https://gerrit.instructure.com/6986 Tested-by: Hudson <hudson@instructure.com> Reviewed-by: Ryan Florence <ryanf@instructure.com>
2011-11-11 00:31:45 +08:00
"devDependencies": {
upgrade & dedupe node packages fixes FOO-2037 the result of removing yarn.lock and reinstalling packages according to the latest version within their specified range Change-Id: I1d2851d5a1a9fc6caeddc388492622ffd4f59379 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/255460 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Product-Review: Charley Kline <ckline@instructure.com> QA-Review: Charley Kline <ckline@instructure.com> Reviewed-by: Charley Kline <ckline@instructure.com>
2021-05-26 01:22:32 +08:00
"@apollo/react-common": "~3.0.1",
"@apollo/react-components": "~3.0.1",
"@apollo/react-hoc": "~3.0.1",
"@apollo/react-hooks": "~3.0.1",
"@apollo/react-ssr": "~3.0.1",
Position and mount Mentions component refs VICE-1683 Test Plan 1. Enable Mentions Flag and Discussion Redesign Flag 2. Open Discussions and open an RCE 3. Type some text and then the @ symbol. 4. Notice, the menu should be positioned under the @ symbol populated with dummy data names (for now) Note: There is no filtering, selecting, or simple way to escape at the moment and will be coming in future reviews. Change-Id: Icd8fa583004db77313f3fb188933d1a202ef2e0c Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/269684 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Matthew Lemon <mlemon@instructure.com> QA-Review: Matthew Lemon <mlemon@instructure.com> Product-Review: Matthew Lemon <mlemon@instructure.com>
2021-07-12 09:26:47 +08:00
"@apollo/react-testing": "~3.0.1",
Upgrade to babel 7 & allow any js file to be themeable closes: CORE-2699 CORE-2700 UIDEV-99 This commit gets canvas-lms itself upgraded to babel 7. To do that we also had to upgrade jest to v24. We had already got canvas-rce and canvas-planner on jest24/babel7 but now this gets everything to babel 7. so you will see a lot of things removed from yarn.lock since we don’t don’t have to have different versions of everything for babel and jest The other major thing this does is make it so any JS file in canvas can become an @instructure/ui-themeable themeable component. This means you no longer should have to put your css in app/stylesheets for any new react components that you are writing. Test plan: 1. Make sure that the perf of `yarn build:js` is on-par with what it was before. We pass everything through the themeable babel transform now so there is a chance it is slower. If it is majorly slower, we’ll have to figure something out. 2. run a production weback build. The common (or any bundle for that matter should get output exactly the same as it did before) things to manually qa check: * in a NODE_ENV=production enviornment, go to /accounts/site_admin/developer_keys * click the "+ Developer Key" button, it should open the modal. (there are selenium tests that do this, but it was one thing that had to be fixed to get jenkins to pass) * on a course that is set up as a master course, click on the thing that opens the blueprint courses tray. * verify that when you click "Associations" and "Sync History" links in that tray, that they dynamically load the webpack chunk for the modal contents for that thing and then the modal is shown (again, there are selenium specs that test that exact thing but it is always good to manually test it too) Change-Id: I802584228962b54480a500f8fe422f45c2dcac4c Reviewed-on: https://gerrit.instructure.com/183965 Tested-by: Jenkins Reviewed-by: Clay Diffrient <cdiffrient@instructure.com> QA-Review: Ryan Shaw <ryan@instructure.com> Product-Review: Ryan Shaw <ryan@instructure.com>
2019-03-06 05:20:27 +08:00
"@babel/cli": "^7.0.0",
"@babel/core": "^7.0.0",
Now that i18nliner can understand it, turn back on fragments The previous commit makes it so i18nliner can understand <> instead of <React.Fragment>, so this turns back on the eslint rule we had to turn Off Test plan: * run bin/rake i18n:generate_js (or let the Jenkins builds run) * it should pass Change-Id: Ia3204cd6c3147eb52ca612adbb3b20b2df8c6921 Reviewed-on: https://gerrit.instructure.com/205378 Tested-by: Jenkins Reviewed-by: Ed Schiebel <eschiebel@instructure.com> QA-Review: Ryan Shaw <ryan@instructure.com> Product-Review: Ryan Shaw <ryan@instructure.com>
2019-08-16 05:46:07 +08:00
"@babel/parser": "^7",
babel independence(2): karma refs FOO-2697 flag = none webpack config for karma is also independent now and no longer tied to the main build config, you can find it under ui-build/webpack-for-karma there are no notable changes outside of breaking that config into a few files ~ TEST PLAN ~ +-=---------! - karma/QUnit suite actually runs and passes Change-Id: Iff474a3d0068441dc8a7c4de605765d936e8ab6d Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/283377 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Charley Kline <ckline@instructure.com> Reviewed-by: Sean Scally <sean.scally@instructure.com> QA-Review: Charley Kline <ckline@instructure.com> Product-Review: Charley Kline <ckline@instructure.com>
2022-01-22 09:14:14 +08:00
"@babel/plugin-proposal-class-properties": "^7",
babel independence(3): jest refs FOO-2697 flag = none on "babel-plugin-transform-imports": the behavior of this plugin was surprising to me in that it not only rewrote the specifiers to point to the CommonJS instead of the ESM variants, but it actually changed the specifiers to point to the exact file that exports the symbol through a mixture of fs globbing and guesses. Consider the following import: import { DateTime } from '@instructure/ui-i18n' Normally, you'd think we'll be loading the {main,module,browser} file of the @instructure/ui-i18n package and refer to the `DateTime` symbol exported by that file. With the plugin activated, however, the import *itself* changes to: import DateTime from '@instructure/ui-i18n/lib/DateTime.js' This is no longer merely a variant rewrite in any way as we're no longer loading the same file. This caused new problems to surface that up to this point were not encountered, as now we're actually loading the entrypoints as specified. An example of this is in that specific package where it (its entrypoint) loads a package `decimal.js` whose ESM variant doesn't work as-is but its CJS variant does -- something neither we nor the InstUI team were privy to as the plugin was simply clobbering this piece of information. ~ test plan ~ - jest suite runs and passes Change-Id: I55d7db1ede742e0f588a84d54a761b7aba03729f Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/283543 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Aaron Shafovaloff <ashafovaloff@instructure.com> QA-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Product-Review: Ahmad Amireh <ahmad@instructure.com>
2022-01-25 23:25:15 +08:00
"@babel/plugin-proposal-optional-chaining": "^7",
babel independence(2): karma refs FOO-2697 flag = none webpack config for karma is also independent now and no longer tied to the main build config, you can find it under ui-build/webpack-for-karma there are no notable changes outside of breaking that config into a few files ~ TEST PLAN ~ +-=---------! - karma/QUnit suite actually runs and passes Change-Id: Iff474a3d0068441dc8a7c4de605765d936e8ab6d Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/283377 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Charley Kline <ckline@instructure.com> Reviewed-by: Sean Scally <sean.scally@instructure.com> QA-Review: Charley Kline <ckline@instructure.com> Product-Review: Charley Kline <ckline@instructure.com>
2022-01-22 09:14:14 +08:00
"@babel/plugin-transform-modules-commonjs": "^7",
bump babel to latest v7.x refs DE-1274 Change-Id: I2b3a678761a03b71b97659ec585b3023223329e6 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/296262 Reviewed-by: Andrea Cirulli <andrea.cirulli@instructure.com> QA-Review: Aaron Ogata <aogata@instructure.com> Product-Review: Aaron Ogata <aogata@instructure.com> Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com>
2022-07-16 01:11:46 +08:00
"@babel/plugin-transform-react-constant-elements": "^7",
"@babel/plugin-transform-react-inline-elements": "^7",
"@babel/plugin-transform-runtime": "^7",
"@babel/preset-env": "^7",
"@babel/preset-react": "^7",
"@babel/preset-typescript": "^7",
upgrade graphql-tools to v7 Change-Id: Id0c390336ccc0a42f0ae82d591f2fa44d43322fd Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/345426 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Isaac Moore <isaac.moore@instructure.com> QA-Review: Aaron Ogata <aogata@instructure.com> Product-Review: Aaron Ogata <aogata@instructure.com>
2024-04-17 07:46:44 +08:00
"@graphql-tools/mock": "^7",
"@graphql-tools/schema": "^7",
rename canvas-supported-browsers to browserslist-config-canvas-lms this is to get it to work with how browserslist/autoprefixer/babel/ @instructure/ui-babel-preset expect things to work. We had to change the name because https://github.com/browserslist/browserslist#shareable-configs Says: For security reasons, external configuration only supports packages that have the browserslist-config- prefix. npm scoped packages are also supported, by naming or prefixing the module with @scope/browserslist-config, such as @scope/browserslist-config or @scope/browserslist-config-mycompany And we have to add: "browserslist": ["extends @instructure/browserslist-config-canvas-lms"], to all of our package.jsons that use @instructure/ui-babel-preset because that by default will use "extends @instructure/browserslist-config-instructure—ui" which would still do all the stuff for IE11 Test plan: * run `yarn` * all those errors about browserslist and postcss should not show uo * look at the code in public/dist for canvas-planner, * It should not include regenerator-runtime and you should see native `async` functions Change-Id: Ic84c13ac59d58963c12b8365b3068b5da3ee618d Reviewed-on: https://gerrit.instructure.com/204251 Tested-by: Jenkins Reviewed-by: Cameron Matheson <cameron@instructure.com> QA-Review: Ryan Shaw <ryan@instructure.com> Product-Review: Ryan Shaw <ryan@instructure.com>
2019-08-08 03:10:17 +08:00
"@instructure/browserslist-config-canvas-lms": ">=2",
(i18n-js:4) use i18nliner-canvas from npm refs FOO-2801 flag = none [change-merged][build-registry-path=jenkins/canvas-lms/foo-2801] gems/canvas_i18nliner is now a package @instructure/i18nliner-canvas and lives in the same repo on github along with the 3 other i18nliner libraries.. this was done to make it easier for maintainers to deal with this code, since changing one part may break the other due to how they're architected the source on github: https://github.com/instructure/i18nliner-js ~ test plan ~ build is still OK, this only affects the generation of files, and those i manually verified to be identical before and after Change-Id: I78afa8a808f1699c10aced8466cfade066848bc9 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/294209 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Charley Kline <ckline@instructure.com> QA-Review: Charley Kline <ckline@instructure.com> Product-Review: Charley Kline <ckline@instructure.com>
2022-06-19 18:52:13 +08:00
"@instructure/i18nliner": "^3",
remove coffeescript from package.json and yarn.lock test plan: - existing tests pass flag=none closes EVAL-3058 closes EVAL-3072 Change-Id: I7dd9ae41f23c7b1fb8f16f752bf17af192e15f30 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/316585 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> QA-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Product-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Reviewed-by: Jacob Burroughs <jburroughs@instructure.com>
2023-12-26 19:23:15 +08:00
"@instructure/i18nliner-canvas": "^1.3",
(i18n-js:4) use i18nliner-canvas from npm refs FOO-2801 flag = none [change-merged][build-registry-path=jenkins/canvas-lms/foo-2801] gems/canvas_i18nliner is now a package @instructure/i18nliner-canvas and lives in the same repo on github along with the 3 other i18nliner libraries.. this was done to make it easier for maintainers to deal with this code, since changing one part may break the other due to how they're architected the source on github: https://github.com/instructure/i18nliner-js ~ test plan ~ build is still OK, this only affects the generation of files, and those i manually verified to be identical before and after Change-Id: I78afa8a808f1699c10aced8466cfade066848bc9 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/294209 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Charley Kline <ckline@instructure.com> QA-Review: Charley Kline <ckline@instructure.com> Product-Review: Charley Kline <ckline@instructure.com>
2022-06-19 18:52:13 +08:00
"@instructure/i18nliner-handlebars": "^2",
Bump i18nliner again Change-Id: I3e67f7feafe50063329d28b0306734a97f669f92 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/298279 Reviewed-by: Charley Kline <ckline@instructure.com> Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> QA-Review: Jacob Burroughs <jburroughs@instructure.com> Product-Review: Jacob Burroughs <jburroughs@instructure.com>
2022-08-11 01:49:43 +08:00
"@instructure/i18nliner-runtime": "^1.0.2",
upgrade prettier test plan: specs pass Change-Id: I81883f8dc88f9ae96fc45fc0899d2f500abe56f2 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/258174 Reviewed-by: Ahmad Amireh <ahmad@instructure.com> QA-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Product-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com>
2021-02-05 02:32:55 +08:00
"@prettier/plugin-ruby": "^1.5.2",
A2: implement delete button closes ADMIN-2233 test plan: - click the delete button which will open a confirmation dialog that roughly matches the design - a11y for the dialog should make sense - the close button should dismiss the dialog with no effect - the cancel button should dismiss the dialog with no effect - the delete button should start a delete operation - when the delete operation completes, you should be redirected to the assignment index screen with a message indicating the assignment has been deleted - if your user does not have permission to delete the assignment, or some other error occurs, then the in-development error screen should be shown Change-Id: I0c3304360d3c389296bd0910d02d8215bdb0ac9e Reviewed-on: https://gerrit.instructure.com/177754 Reviewed-by: Carl Kibler <ckibler@instructure.com> Tested-by: Jenkins QA-Review: Carl Kibler <ckibler@instructure.com> Product-Review: Jon Willesen <jonw+gerrit@instructure.com>
2019-01-15 01:33:05 +08:00
"@sheerun/mutationobserver-shim": "0.3.2",
upgrade @testing-library to latest supported refs DE-1265 Change-Id: If73ca0be128b12c2ae6c7e9a12a72a9aa2971d2e Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/296007 Reviewed-by: Andrea Cirulli <andrea.cirulli@instructure.com> Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> QA-Review: Aaron Ogata <aogata@instructure.com> Product-Review: Aaron Ogata <aogata@instructure.com>
2022-07-13 05:54:21 +08:00
"@testing-library/dom": "^8",
Upgrade @testing-library dependencies to latest Most of the upgrades were backwards-compatible, but I made a few changes: * Replaced usages of wait, waitForElement, and waitForDomChange with waitFor as recommended here, since they are deprecated: https://testing-library.com/docs/dom-testing-library/api-async/#deprecated-methods * Replaced '@testing-library/react-hooks' imports with '@testing-library/react-hooks/dom' as recommended here: https://react-hooks-testing-library.com/installation#being-specific * Fixed some issues with @testing-library/jest-dom's toBeDisabled matcher not checking for the disabled attribute on parent elements-- e.g. changing this: `expect(getByText('Button Text')).toBeDisabled()` to this: `expect(getByRole('button', {name: 'Button Text'})).toBeDisabled()` closes LS-1831 flag = none Test plan: tests pass in Jenkins Change-Id: Ia549950dade5fd5b2597a3002b11f4f0a6f740f2 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/258923 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Charley Kline <ckline@instructure.com> QA-Review: Charley Kline <ckline@instructure.com> Product-Review: Charley Kline <ckline@instructure.com>
2021-02-18 02:07:07 +08:00
"@testing-library/jest-dom": "^5",
upgrade @testing-library to latest supported refs DE-1265 Change-Id: If73ca0be128b12c2ae6c7e9a12a72a9aa2971d2e Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/296007 Reviewed-by: Andrea Cirulli <andrea.cirulli@instructure.com> Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> QA-Review: Aaron Ogata <aogata@instructure.com> Product-Review: Aaron Ogata <aogata@instructure.com>
2022-07-13 05:54:21 +08:00
"@testing-library/react": "^12",
Upgrade @testing-library dependencies to latest Most of the upgrades were backwards-compatible, but I made a few changes: * Replaced usages of wait, waitForElement, and waitForDomChange with waitFor as recommended here, since they are deprecated: https://testing-library.com/docs/dom-testing-library/api-async/#deprecated-methods * Replaced '@testing-library/react-hooks' imports with '@testing-library/react-hooks/dom' as recommended here: https://react-hooks-testing-library.com/installation#being-specific * Fixed some issues with @testing-library/jest-dom's toBeDisabled matcher not checking for the disabled attribute on parent elements-- e.g. changing this: `expect(getByText('Button Text')).toBeDisabled()` to this: `expect(getByRole('button', {name: 'Button Text'})).toBeDisabled()` closes LS-1831 flag = none Test plan: tests pass in Jenkins Change-Id: Ia549950dade5fd5b2597a3002b11f4f0a6f740f2 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/258923 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Charley Kline <ckline@instructure.com> QA-Review: Charley Kline <ckline@instructure.com> Product-Review: Charley Kline <ckline@instructure.com>
2021-02-18 02:07:07 +08:00
"@testing-library/react-hooks": "^5",
Upgrade @testing-library/user-event to v14 Removes user-event from canvas-media since its not actually used there, and bumps the version in canvas-rce as well. The only non-spec files that this commit touches are: package.json, canvas-media/package.json, canvas-rce/package.json, and yarn.lock. The remainder of the changes are changes to jest spec files to resolve breaking changes in the user-event API. The vast majority of the changes make usages of user-event adhere to the new API which returns a promise, so calls now need to be explicitely `await`ed. This change also exposed a couple of synchronicity issues in test code which were rectified. 6 total specs were skipped across 3 files: action_button.test.tsx, FilterNav.test.tsx, and CreateCourseModal.test.jsx. These will be addressed in follow-up commits by owning teams who have more context about how the underlying component should behave. closes LF-1289 flag = none Test plan: specs pass Change-Id: If8f9db685593e906da9b2af5ae8d39fc63fe8c7c Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/340719 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Ed Schiebel <eschiebel@instructure.com> QA-Review: Jackson Howe <jackson.howe@instructure.com> Product-Review: Jackson Howe <jackson.howe@instructure.com>
2024-02-17 03:06:46 +08:00
"@testing-library/user-event": "^14",
Install Vitest This does not yet change our build process Demo: - yarn run test:vitest:watch ui/features/theme_editor/ Test plan: - build passes Closes CFA-17 flag=none Change-Id: I6eac4684af62525829e36f5dd0c64bb80c638ca3 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/333130 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Martin Ochoa <martin.ochoa@instructure.com> Reviewed-by: Gustavo Bernardes <gustavo.bernardes@instructure.com> QA-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Product-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Build-Review: Andrea Cirulli <andrea.cirulli@instructure.com>
2023-11-17 20:54:42 +08:00
"@types/enzyme": "^3.10.16",
"@types/enzyme-adapter-react-16": "^1.0.9",
Convert `axios` usage to `fetch` in Pace Plans closes LS-2624 flag=pace_plans test plan: - with pace plans enabled, navigate to the pace plans view - select the settings cog, and toggle the "Skip Weekends" option - verify that the network request succeeds Change-Id: I0fbbc4236167bbcc9d4d665b734736b88988ef1f Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/273658 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Nate Armstrong <narmstrong@instructure.com> QA-Review: Nate Armstrong <narmstrong@instructure.com> Product-Review: Isaac Moore <isaac.moore@instructure.com>
2021-09-16 04:53:42 +08:00
"@types/jquery": "^3.5.6",
Harden & TypeScriptify SpeedGrader This brings out lint warnings and errors in SpeedGrader to 0. It brings TypeScript to SpeedGrader. This will make working in speed_grader.tsx easier. test plan: - all automated tests pass flag=none Refs EVAL-2220 Change-Id: If889723923f78061c9908ef780542debb1b289a5 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/284307 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> QA-Review: Kai Bjorkman <kbjorkman@instructure.com> Product-Review: Syed Hussain <shussain@instructure.com> Reviewed-by: Spencer Olson <solson@instructure.com> Reviewed-by: Eduardo Escobar <eduardo.escobar@instructure.com>
2022-02-03 10:49:28 +08:00
"@types/jqueryui": "^1.12.16",
Add new Pace Plan picker component This change adds a new fly-out drop-down component for selecting a type of pace plan to work with, replacing the old two components. As part of this change, the "selectedPlanType" state was replaced with "selectedContextType" and "selectedContextId". The change also contains some refactoring to ensure that all IDs are treated as strings everywhere (instead of "number | string"). closes LS-2591 flag = pace_plans Test plan: - Enable pace plans on a course (account-level feature flag and course-level setting) - Ensure the course has several enrollments and at least a couple of sections - Create a pace plan for the course via the Rails console: c = Course.find<id> pp = c.pace_plans.create! workflow_state: 'active' c.context_module_tags.each_with_index do |t, i| pp.pace_plan_module_items.create! module_item: t, duration: i*2 end - Go to the pace plans page in the course - Expect to see a single drop-down defaulting to "Course Pace Plan" - Expect to see all sections listed alphabetically under "Sections" - Expect to see all students listed alphabetically by sortable_name under "Students" - Click on "Course Pace Plan", expect to see a network request in dev tools for latest_draft_for?context_type=Course&context_id=<id> (with the ID of the course) - Click on a section, expect to see a network request in dev tools for latest_draft_for?context_type=Section&context_id=<id> (with the ID of the section) - Click on a student, expect to see a network request in dev tools for latest_draft_for?context_type=Enrollment&context_id=<id> (with the ID of the enrollment) - Expect to get error messages for these requests, since the associated API endpoint doesn't exist yet Change-Id: Iae03d6e3e853bf2c1fe5d0638ab1ae8e79f146e1 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/272802 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Nate Armstrong <narmstrong@instructure.com> QA-Review: Nate Armstrong <narmstrong@instructure.com> Product-Review: Peyton Craighill <pcraighill@instructure.com>
2021-09-03 00:08:08 +08:00
"@types/lodash": "^4.14.72",
Convert `axios` usage to `fetch` in Pace Plans closes LS-2624 flag=pace_plans test plan: - with pace plans enabled, navigate to the pace plans view - select the settings cog, and toggle the "Skip Weekends" option - verify that the network request succeeds Change-Id: I0fbbc4236167bbcc9d4d665b734736b88988ef1f Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/273658 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Nate Armstrong <narmstrong@instructure.com> QA-Review: Nate Armstrong <narmstrong@instructure.com> Product-Review: Isaac Moore <isaac.moore@instructure.com>
2021-09-16 04:53:42 +08:00
"@types/parse-link-header": "^1.0.0",
Harden SpeedGrader with TypeScript Test plan: - Build passes flag=none Change-Id: Ic3ad7b7d27659741197e37169158ff4806a1dbeb Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/327246 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Kai Bjorkman <kbjorkman@instructure.com> Reviewed-by: Derek Williams <derek.williams@instructure.com> QA-Review: Kai Bjorkman <kbjorkman@instructure.com> Product-Review: Aaron Shafovaloff <ashafovaloff@instructure.com>
2023-09-09 03:11:48 +08:00
"@types/qs": "^6.9.8",
Initial pace plans import This change brings in the basic pace plans frontend with styled-components and several other smaller libraries replaced with InstUI 7 components. It also adds the 'reselect' library as a direct dependency (which we already had through @instructure/outcomes-ui) and 'tsc-files' for type-checking of staged TS files on commit. There were also some tweaks to typescript and eslint configs, mostly to get both up to speed with the typescript code. Finally, this also adds a `pace_plans` endpoint to `courses_controller` to bootstrap the frontend-- this will get moved to `pace_plans_controller` once it has been merged. It's also worth noting that no frontend tests are included with this change-- the existing tests were written with enzyme and are heavily snapshot-based, so we will be replacing those with @testing-library/react tests in later updates (in keeping with current testing best practices at Instructure). closes LS-2431, LS-2432, LS-2433, LS-2434, LS-2452 flag = pace_plans Test plan: - Set up a course with at least one module and several module items - Turn on the pace_plans feature flag in the account associated with that course - Turn on the "Enable pace plans" setting in course settings - Create a pace plan for the course via the Rails console: c = Course.find<id> pp = c.pace_plans.create! workflow_state: 'active' c.context_module_tags.each_with_index do |t, i| pp.pace_plan_module_items.create! module_item: t, duration: i*2 end - Go to the course as a teacher or admin - Expect to see a "Pace Plans" link in the course navigation - Click it, expect the pace plan you created earlier to load and render - Expect to be able to pick dates, change durations, and toggle checkboxes (although saves will fail, since there is no API yet). - Expect to not see the "Pace Plans" course nav link when the feature flag or course setting is off - Expect /courses/<id>/pace_plans to return a 404 when the feature flag or course setting is off - Expect to not see the "Pace Plans" course nav link as a student - Expect /courses/<id>/pace_plans to display an "Unauthorized" page as a student Change-Id: If4dc5d17f2c6a2109d4b4cb652c9e9ef00d7cc33 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/271650 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Ed Schiebel <eschiebel@instructure.com> QA-Review: Ed Schiebel <eschiebel@instructure.com> Product-Review: Jeff Largent <jeff.largent@instructure.com>
2021-08-18 05:14:24 +08:00
"@types/react": "^17.0.19",
drag and drop rubric criteria and ratings closes EVAL-3635 flag=enhanced_rubrics Test Plan: - Create a new rubric - Add a criteria with some ratings - ensure you can add and drag around the ratings to different indexes, but the point values stay fixed on the left. - ensure you can save the criteria and edit it again and the order and ratings are preserved. - Also ensure that when the long description is two long the box expands, but everything in the rating row is aligned vertically(center). - ensure when dragging around ratings that the add rating button is hidden when dragging and reappears when you stop dragging. -ensure the saved rating order is also correctly displayed on the criteria index page. - ensure you can also drag around the criteria themselves and the points and ratings move with them. Change-Id: I08fe4d9a09933509deefed0fb62523068a38ad5a Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/341590 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Derek Williams <derek.williams@instructure.com> QA-Review: Christopher Soto <christopher.soto@instructure.com> Product-Review: Ravi Koll <ravi.koll@instructure.com>
2024-02-27 09:04:10 +08:00
"@types/react-beautiful-dnd": "^13.1.8",
Initial pace plans import This change brings in the basic pace plans frontend with styled-components and several other smaller libraries replaced with InstUI 7 components. It also adds the 'reselect' library as a direct dependency (which we already had through @instructure/outcomes-ui) and 'tsc-files' for type-checking of staged TS files on commit. There were also some tweaks to typescript and eslint configs, mostly to get both up to speed with the typescript code. Finally, this also adds a `pace_plans` endpoint to `courses_controller` to bootstrap the frontend-- this will get moved to `pace_plans_controller` once it has been merged. It's also worth noting that no frontend tests are included with this change-- the existing tests were written with enzyme and are heavily snapshot-based, so we will be replacing those with @testing-library/react tests in later updates (in keeping with current testing best practices at Instructure). closes LS-2431, LS-2432, LS-2433, LS-2434, LS-2452 flag = pace_plans Test plan: - Set up a course with at least one module and several module items - Turn on the pace_plans feature flag in the account associated with that course - Turn on the "Enable pace plans" setting in course settings - Create a pace plan for the course via the Rails console: c = Course.find<id> pp = c.pace_plans.create! workflow_state: 'active' c.context_module_tags.each_with_index do |t, i| pp.pace_plan_module_items.create! module_item: t, duration: i*2 end - Go to the course as a teacher or admin - Expect to see a "Pace Plans" link in the course navigation - Click it, expect the pace plan you created earlier to load and render - Expect to be able to pick dates, change durations, and toggle checkboxes (although saves will fail, since there is no API yet). - Expect to not see the "Pace Plans" course nav link when the feature flag or course setting is off - Expect /courses/<id>/pace_plans to return a 404 when the feature flag or course setting is off - Expect to not see the "Pace Plans" course nav link as a student - Expect /courses/<id>/pace_plans to display an "Unauthorized" page as a student Change-Id: If4dc5d17f2c6a2109d4b4cb652c9e9ef00d7cc33 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/271650 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Ed Schiebel <eschiebel@instructure.com> QA-Review: Ed Schiebel <eschiebel@instructure.com> Product-Review: Jeff Largent <jeff.largent@instructure.com>
2021-08-18 05:14:24 +08:00
"@types/react-dom": "^17.0.9",
reduce JS linting noise flag=none flag=none Change-Id: I54e0c3e4403b14ead4476937aba2a0db24c40f37 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/336817 Reviewed-by: Jeremy Stanley <jeremy@instructure.com> Reviewed-by: Kai Bjorkman <kbjorkman@instructure.com> QA-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Product-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com>
2024-01-06 03:25:13 +08:00
"@typescript-eslint/eslint-plugin": "^6.17.0",
"@typescript-eslint/parser": "^5.62.0",
upgrade msw flag=none closes CFA-35 closes LF-1117 Change-Id: I42e65f70ee74a2931a0a4439a4c9c0f22466ef62 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/336892 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Caleb Guanzon <cguanzon@instructure.com> Product-Review: Caleb Guanzon <cguanzon@instructure.com> QA-Review: Aaron Shafovaloff <ashafovaloff@instructure.com>
2024-01-08 09:23:15 +08:00
"@vitest/ui": "^1.0.4",
A script to just update instUI Closes: CORE-1709 This is what our Jenkins job to pull in every instui RC commit will use Test plan: * run `yarn upgrade-instructure-ui` * it should make a commit that has new entries in yarn.lock for all the instUI packages that uses the latest rc version on the npm registry * it should not affect anything else besides yarn.lock Change-Id: I78cce6e801015819c4e4b27e26ede352deceebb9 Reviewed-on: https://gerrit.instructure.com/160435 Tested-by: Jenkins Reviewed-by: Brent Burgoyne <bburgoyne@instructure.com> Product-Review: Ryan Shaw <ryan@instructure.com> QA-Review: Ryan Shaw <ryan@instructure.com>
2018-08-11 00:22:49 +08:00
"@yarnpkg/lockfile": "^1.0.2",
add progress bar and errors to asmt bulk edit closes LA-898 flag=assignment_bulk_edit test plan: - Edit many dates and save - The job should start and a progress bar should be displayed next to the cancel button - The job progress should be polled and the progress bar updated - When the job completes, polling stops (see network tab), the progress bar should be at 100%, and a success message should be displayed. - There should be appropriate screen reader announcements. - If there are any errors during the job, polling should stop and the error messages should be displayed. Change-Id: Ifd9ec6224318a003317a66ce2460ccf3e9d45efa Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/233136 Reviewed-by: Jeremy Stanley <jeremy@instructure.com> QA-Review: Jeremy Stanley <jeremy@instructure.com> Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Product-Review: Jon Willesen <jonw+gerrit@instructure.com>
2020-04-07 06:07:18 +08:00
"array-flat-polyfill": "^1.0.1",
[npm dependencies] update all our npm dependencies This is just the regular “update all the things” commit. For things in package.json that we just want the latest version of, I changed them to a simple major with a carat. (Eg: “8^” or “4^”), that way you can see easier which things are specifically locked down To a specific version (or range of versions) for a reason. Test plan: * automated specs & build tasks should work Change-Id: Id7a3f853bd0f7537cc0f08d7dba8d6726b836c44 Reviewed-on: https://gerrit.instructure.com/141653 Tested-by: Jenkins Reviewed-by: Brent Burgoyne <bburgoyne@instructure.com> QA-Review: Brent Burgoyne <bburgoyne@instructure.com> Product-Review: Brent Burgoyne <bburgoyne@instructure.com>
2018-02-23 03:58:38 +08:00
"axe-core": "~2.1.7",
Upgrade canvas-planner & rce to not use ui-presets This gets canvas planner and canvas-rce on babel 7, which is a prerequisite to canvas doing the same. Also, by not depending on the Kitchen sink of ui-presets, it cleans a ton of unused stuff from our node_modules/yarn.lock. It was originally 2 different commits but in order to get the yarn.lock right, we have to do them all as one. This also made it so we needed to have less “resolutions” in our package.json since the newer versions of those things work fine with the newer version of babel So there are 2 test plan areas: 1. Canvas-planner Closes: CORE-2575 Test plan: * smoke test to make sure everything in canvas-planner still works/looks like it used to in the canvas ui * make sure the translation task (yarn check-transifex) still works canvas-rce: upgrade to babel 7 & @instructure/ui-babel-preset 2. canvas-rce Closes: CORE-2576 Test plan: * smoke test the RCE editor * theming should still work/look exactly as before * make sure all the various build tasks (eg yarn test, test:coverage, debug, lint, extract, etc) all still work as before Change-Id: Id896687e3905f4df4627b181cad3f67ffe4417a5 Reviewed-on: https://gerrit.instructure.com/183877 Tested-by: Jenkins Reviewed-by: Jon Willesen <jonw+gerrit@instructure.com> Reviewed-by: Steven Burnett <sburnett@instructure.com> QA-Review: Brent Burgoyne <bburgoyne@instructure.com> Product-Review: Ryan Shaw <ryan@instructure.com>
2019-03-06 02:30:44 +08:00
"babel-eslint": "^10",
upgrade jest to v28 refs DE-1284 Change-Id: I6f91f5d986d51d73a809cba9fd93355a6f8de7a4 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/296476 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Andrea Cirulli <andrea.cirulli@instructure.com> QA-Review: Aaron Ogata <aogata@instructure.com> Product-Review: Aaron Ogata <aogata@instructure.com>
2022-07-19 06:07:53 +08:00
"babel-jest": "^28",
upgrade babel-loader Change-Id: I1520db81e141135c42799ee895d1de01ad0f9ce8 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/335006 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Drake Harper <drake.harper@instructure.com> Product-Review: Drake Harper <drake.harper@instructure.com> QA-Review: Aaron Shafovaloff <ashafovaloff@instructure.com>
2023-12-10 22:37:48 +08:00
"babel-loader": "^9.1.3",
[npm dependencies] update all our npm dependencies This is just the regular “update all the things” commit. For things in package.json that we just want the latest version of, I changed them to a simple major with a carat. (Eg: “8^” or “4^”), that way you can see easier which things are specifically locked down To a specific version (or range of versions) for a reason. Test plan: * automated specs & build tasks should work Change-Id: Id7a3f853bd0f7537cc0f08d7dba8d6726b836c44 Reviewed-on: https://gerrit.instructure.com/141653 Tested-by: Jenkins Reviewed-by: Brent Burgoyne <bburgoyne@instructure.com> QA-Review: Brent Burgoyne <bburgoyne@instructure.com> Product-Review: Brent Burgoyne <bburgoyne@instructure.com>
2018-02-23 03:58:38 +08:00
"babel-plugin-transform-react-remove-prop-types": "^0.4",
Upgrade babel-plugin-typescript-to-proptypes flag=none Change-Id: I19d4fc30e80d07354bad664e084eeb8b795d7315 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/333531 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Gustavo Bernardes <gustavo.bernardes@instructure.com> QA-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Product-Review: Aaron Shafovaloff <ashafovaloff@instructure.com>
2023-11-22 22:36:48 +08:00
"babel-plugin-typescript-to-proptypes": "^2.1.0",
modernize canvas_quizzes fixes FOO-1409 flag = none no more client_apps, canvas_quizzes now lives as part of canvas-lms proper inside app/jsx/, which makes the build leaner and leaves us with one less thing to reason about logical changes: - converted from AMD to ES modules - upgraded to recent react + react-router - dropped RSVP in favor of native Promises - used CanvasModal instead of home-grown Dialog - removed dead code; notifications in particular were fishy as there had no dependents at all and did not even show up in the graph - ported tests to Jest, added more unit ones and two integration ones - removed "config.onError" and now throws errors where appropriate - disabled console statements in non-dev :: test plan :: - create a (old-school) quiz containing all types of questions - as 3 distinct students, take the quiz and try to randomize your answers at this point it's helpful to have a reference to compare the screens; I replicated the quiz on my production sandbox for this - go to /courses/:id/quizzes/:id/submissions/:id/log - verify it looks OK - click on a specific question in the stream and verify the question inspector widget works OK - go back to stream and push "View table" - verify the table and its controls are OK - go to /courses/:id/quizzes/:id/statistics - verify it looks OK - click on ? in the discrimination index chart and verify it displays a dialog with help content - click on "X respondents" in one of the charts and verify it displays a dialog with the respondent names - verify the interactive charts do interact as expected (no logic changed here so just a quick glance) - link to "View in SpeedGrader" for essay-like questions works Change-Id: I79af5ff4f1479503b5e2528b613255dde5bc45d3 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/256118 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Simon Williams <simon@instructure.com> QA-Review: Simon Williams <simon@instructure.com> Product-Review: Simon Williams <simon@instructure.com>
2021-01-02 07:58:12 +08:00
"chai-assert-change": "^2.0.0",
move planner to ui/shared test plan: - smoke test of planner - build passes flag=none Change-Id: I1ccab60a53269adaa4247658696ee080e4e03fae Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/323860 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> QA-Review: Caleb Guanzon <cguanzon@instructure.com> QA-Review: Michael Hulse <michael.hulse@instructure.com> Product-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Reviewed-by: Ed Schiebel <eschiebel@instructure.com>
2023-07-29 01:57:25 +08:00
"change-case": "3.0.1",
Yarn.lock: update all our npm dependencies closes: CORE-1909 This is the result of running: `yarn upgrade-and-dedupe` and then fixing any specs/changes that needed to happen as a result of the new versions Test plan: * automated tests should pass Change-Id: I79ec63d8eb9d7bce4d48af0cff7cee369be58884 Reviewed-on: https://gerrit.instructure.com/164790 Reviewed-by: Brent Burgoyne <bburgoyne@instructure.com> Tested-by: Jenkins Product-Review: Ryan Shaw <ryan@instructure.com> QA-Review: Ryan Shaw <ryan@instructure.com>
2018-09-18 07:08:57 +08:00
"concurrently": "^4",
babel independence(1): webpack refs FOO-2697 flag = none stop relying on @instructure/ui-babel-preset and instead use exactly the transforms that we still need today from Babel transformations that appear to be no longer necessary: - plugin-transform-destructuring - plugin-proposal-decorators - plugin-proposal-class-properties - plugin-proposal-export-default-from - plugin-proposal-object-rest-spread - plugin-proposal-optional-chaining - plugin-syntax-dynamic-import - plugin-proposal-private-methods - postcss et al (we only import 3-4 css sources and they all come from node_modules, we don't use themeable on core) transformations that i don't think are necessary: - babel-plugin-transform-undefined-to-void: because if there is code that is re-assigning `undefined`, the solution would be not to humor it but to stop using it and perhaps file a lawsuit babel deps were pinned to avoid semver upgrading, because upgrading within the 7 line is already breaking us and i'll deal with that another day ~ TEST PLAN ~ \ ---- ---- / - you can run webpack locally and see no visual artifacts Change-Id: I64eb9a7ac94e17f730686f579cf67cd8bd4e12f2 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/283142 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Sean Scally <sean.scally@instructure.com> Reviewed-by: Charley Kline <ckline@instructure.com> Product-Review: Charley Kline <ckline@instructure.com> QA-Review: Charley Kline <ckline@instructure.com>
2022-01-19 06:25:07 +08:00
"core-js": "^3.20.3",
upgrade some NPM dependencies Change-Id: If2a90959713e292a46c9d5e9c75c89a37f7316b6 Reviewed-on: https://gerrit.instructure.com/205007 Tested-by: Jenkins Reviewed-by: Cameron Matheson <cameron@instructure.com> QA-Review: Ryan Shaw <ryan@instructure.com> Product-Review: Ryan Shaw <ryan@instructure.com>
2019-08-14 13:36:39 +08:00
"core-js-builder": "^3",
"css-loader": "^3",
use web pack closes CNVS-24124 makes working with web pack possible in canvas instead of require-js. See doc/working_with_webpack.md for instructions. TEST PLAN: Nothing should change in non-webpack'd behavior Things should mostly work when you use the USE_WEBPACK environment variable, but make sure to document and ticket things that don't Change-Id: I493a259a609e9e183950bc57aa5876df70108547 Reviewed-on: https://gerrit.instructure.com/64386 Tested-by: Jenkins Reviewed-by: Clay Diffrient <cdiffrient@instructure.com> Product-Review: Ethan Vizitei <evizitei@instructure.com> QA-Review: Ethan Vizitei <evizitei@instructure.com>
2015-10-01 11:16:11 +08:00
"ember-template-compiler": "^1.8.0",
upgrade enzyme to 3.x Closes: CORE-1758 After this commit, if you or your team have any specs that import from old-enzyme-2.x-you-need-to-upgrade-this-spec-to-enzyme-3.x-by-importing-just-enzyme That means you need to upgrade those spec files to use the new enzyme by changing that to `import {mount, shallow, whatever} from ‘enzyme’`. Refer to http://airbnb.io/enzyme/docs/guides/migration-from-2-to-3.html for details Test plan: * all linters-and-js-specs should pass * since this only effects js specs, that is all that really matters. no app code to QA Change-Id: I46c5d815e9d95683832d70b64e31526b943d07e5 Reviewed-on: https://gerrit.instructure.com/135136 Tested-by: Jenkins Reviewed-by: Clay Diffrient <cdiffrient@instructure.com> Product-Review: Ryan Shaw <ryan@instructure.com> QA-Review: Ryan Shaw <ryan@instructure.com>
2017-12-09 01:29:42 +08:00
"enzyme": "^3",
Install Vitest This does not yet change our build process Demo: - yarn run test:vitest:watch ui/features/theme_editor/ Test plan: - build passes Closes CFA-17 flag=none Change-Id: I6eac4684af62525829e36f5dd0c64bb80c638ca3 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/333130 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Martin Ochoa <martin.ochoa@instructure.com> Reviewed-by: Gustavo Bernardes <gustavo.bernardes@instructure.com> QA-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Product-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Build-Review: Andrea Cirulli <andrea.cirulli@instructure.com>
2023-11-17 20:54:42 +08:00
"enzyme-adapter-react-16": "^1.15.7",
add enzyme snapshot serializer to jest converts all the existing `expect(component.debug()).toMatchSnapshot()` to: `expect(component).toMatchSnapshot()` which creates more detailed and more diff-able snapshots test plan: - specs pass -- this only affects js test code Change-Id: Ib6dbcc1e3f87e61a251e4635dc68353aca57aeac Reviewed-on: https://gerrit.instructure.com/167651 Tested-by: Jenkins Reviewed-by: Ryan Shaw <ryan@instructure.com> QA-Review: Ryan Shaw <ryan@instructure.com> Product-Review: Ryan Shaw <ryan@instructure.com>
2018-10-10 03:36:49 +08:00
"enzyme-to-json": "^3.3.4",
Update eslint to v7 so it stops complaining about the ?. operator, among other things closes MAT-45 flag=none test plan: - npx eslint ./path/to/a.js on a file with ?. in it doesn't complain Change-Id: I6056e25ce9c53a8e652d6e4eec1280057369cf26 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/265387 Reviewed-by: Guilherme Baron <gbaron@instructure.com> QA-Review: Guilherme Baron <gbaron@instructure.com> Product-Review: Ed Schiebel <eschiebel@instructure.com> Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com>
2021-05-21 00:54:30 +08:00
"eslint": "^7",
upgrade eslint & don’t use unique one in canvas-rce instead of having our own eslint in canvas-rce, and maintaining all future rules like react hooks and stuff we can just use the same one that the rest of the repo uses. test plan: * cd packages/canvas-rce * `yarn lint` should run Change-Id: Idbe8af533f7a19035d1998538d2d6fd1a711f164 Reviewed-on: https://gerrit.instructure.com/204998 Tested-by: Jenkins Reviewed-by: Clay Diffrient <cdiffrient@instructure.com> QA-Review: Clay Diffrient <cdiffrient@instructure.com> Product-Review: Clay Diffrient <cdiffrient@instructure.com>
2019-08-14 09:31:44 +08:00
"eslint-config-airbnb": "^18",
"eslint-config-prettier": "^6",
Update eslint rules to allow optional chaining closes LA-973 flag=none test plan: - code with a?.b does not report no-unused-expressions eslint error Change-Id: If31b5545c31a9a095176cee74a2173ba0eeceab8 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/235941 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> QA-Review: Anju Reddy <areddy@instructure.com> Product-Review: Ed Schiebel <eschiebel@instructure.com> Reviewed-by: Augusto Callejas <acallejas@instructure.com>
2020-05-01 21:34:22 +08:00
"eslint-plugin-babel": "^5",
ESLint standardization This commit introduces a better more reasonable ESLint configuration. It removes all concerns with styling in favor of using prettier to handle those things. closes CORE-2096 Test Plan: - ESLint works Change-Id: I50b90b7191b576bce4817d885d14f18c4c72d208 Reviewed-on: https://gerrit.instructure.com/170874 Tested-by: Jenkins Reviewed-by: Steven Burnett <sburnett@instructure.com> Reviewed-by: Brent Burgoyne <bburgoyne@instructure.com> QA-Review: Clay Diffrient <cdiffrient@instructure.com> Product-Review: Clay Diffrient <cdiffrient@instructure.com>
2018-11-03 01:48:59 +08:00
"eslint-plugin-eslint-comments": "^3.0.1",
[npm dependencies] update all our npm dependencies This is just the regular “update all the things” commit. For things in package.json that we just want the latest version of, I changed them to a simple major with a carat. (Eg: “8^” or “4^”), that way you can see easier which things are specifically locked down To a specific version (or range of versions) for a reason. Test plan: * automated specs & build tasks should work Change-Id: Id7a3f853bd0f7537cc0f08d7dba8d6726b836c44 Reviewed-on: https://gerrit.instructure.com/141653 Tested-by: Jenkins Reviewed-by: Brent Burgoyne <bburgoyne@instructure.com> QA-Review: Brent Burgoyne <bburgoyne@instructure.com> Product-Review: Brent Burgoyne <bburgoyne@instructure.com>
2018-02-23 03:58:38 +08:00
"eslint-plugin-import": "^2",
Upgrade to babel 7 & allow any js file to be themeable closes: CORE-2699 CORE-2700 UIDEV-99 This commit gets canvas-lms itself upgraded to babel 7. To do that we also had to upgrade jest to v24. We had already got canvas-rce and canvas-planner on jest24/babel7 but now this gets everything to babel 7. so you will see a lot of things removed from yarn.lock since we don’t don’t have to have different versions of everything for babel and jest The other major thing this does is make it so any JS file in canvas can become an @instructure/ui-themeable themeable component. This means you no longer should have to put your css in app/stylesheets for any new react components that you are writing. Test plan: 1. Make sure that the perf of `yarn build:js` is on-par with what it was before. We pass everything through the themeable babel transform now so there is a chance it is slower. If it is majorly slower, we’ll have to figure something out. 2. run a production weback build. The common (or any bundle for that matter should get output exactly the same as it did before) things to manually qa check: * in a NODE_ENV=production enviornment, go to /accounts/site_admin/developer_keys * click the "+ Developer Key" button, it should open the modal. (there are selenium tests that do this, but it was one thing that had to be fixed to get jenkins to pass) * on a course that is set up as a master course, click on the thing that opens the blueprint courses tray. * verify that when you click "Associations" and "Sync History" links in that tray, that they dynamically load the webpack chunk for the modal contents for that thing and then the modal is shown (again, there are selenium specs that test that exact thing but it is always good to manually test it too) Change-Id: I802584228962b54480a500f8fe422f45c2dcac4c Reviewed-on: https://gerrit.instructure.com/183965 Tested-by: Jenkins Reviewed-by: Clay Diffrient <cdiffrient@instructure.com> QA-Review: Ryan Shaw <ryan@instructure.com> Product-Review: Ryan Shaw <ryan@instructure.com>
2019-03-06 05:20:27 +08:00
"eslint-plugin-jest": "^22",
[npm dependencies] update all our npm dependencies This is just the regular “update all the things” commit. For things in package.json that we just want the latest version of, I changed them to a simple major with a carat. (Eg: “8^” or “4^”), that way you can see easier which things are specifically locked down To a specific version (or range of versions) for a reason. Test plan: * automated specs & build tasks should work Change-Id: Id7a3f853bd0f7537cc0f08d7dba8d6726b836c44 Reviewed-on: https://gerrit.instructure.com/141653 Tested-by: Jenkins Reviewed-by: Brent Burgoyne <bburgoyne@instructure.com> QA-Review: Brent Burgoyne <bburgoyne@instructure.com> Product-Review: Brent Burgoyne <bburgoyne@instructure.com>
2018-02-23 03:58:38 +08:00
"eslint-plugin-jsx-a11y": "^6",
upgrade eslint & don’t use unique one in canvas-rce instead of having our own eslint in canvas-rce, and maintaining all future rules like react hooks and stuff we can just use the same one that the rest of the repo uses. test plan: * cd packages/canvas-rce * `yarn lint` should run Change-Id: Idbe8af533f7a19035d1998538d2d6fd1a711f164 Reviewed-on: https://gerrit.instructure.com/204998 Tested-by: Jenkins Reviewed-by: Clay Diffrient <cdiffrient@instructure.com> QA-Review: Clay Diffrient <cdiffrient@instructure.com> Product-Review: Clay Diffrient <cdiffrient@instructure.com>
2019-08-14 09:31:44 +08:00
"eslint-plugin-lodash": "^6",
"eslint-plugin-notice": "^0.8",
the regular “update all the npm things” commit this updates all the stuff we get from npm that we _can_ upgrade to the newest versions available. test plan: * all the builds should pass Change-Id: Icf1cc3cd02d66e6e1f999ea5f5fc3b5b28775881 Reviewed-on: https://gerrit.instructure.com/167282 Reviewed-by: Steven Burnett <sburnett@instructure.com> Tested-by: Jenkins QA-Review: Ryan Shaw <ryan@instructure.com> Product-Review: Ryan Shaw <ryan@instructure.com>
2018-10-04 07:01:30 +08:00
"eslint-plugin-prettier": "^3",
"eslint-plugin-promise": "^4",
"eslint-plugin-qunit": "^4",
Upgrade eslint packages, clean up ignores Update some eslint packages removing the need for some eslint-disable directives. Changed react/no-unknown-property to warning since we have several instances of it already in the codebase. Refs CFA-5 flag=none Test plan: - Automated tests pass Change-Id: I4967d53477de7c4effe8861ee71e735be33f6b14 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/317894 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Aaron Shafovaloff <ashafovaloff@instructure.com> QA-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Product-Review: Aaron Shafovaloff <ashafovaloff@instructure.com>
2023-05-11 03:36:39 +08:00
"eslint-plugin-react": "^7.32.2",
add react-hooks linting and update react dep Update the react dependency to 16.8 since we're starting to use react hooks, which requires that version at minimum. test plan: - linting still works - intentionally create a violation of rules-of-hooks. Linting should find and report the error. Change-Id: I0baccd64397b31118b96eb390462acf56daeca96 Reviewed-on: https://gerrit.instructure.com/199053 Reviewed-by: Ryan Shaw <ryan@instructure.com> QA-Review: Ryan Shaw <ryan@instructure.com> Product-Review: Ryan Shaw <ryan@instructure.com> Tested-by: Jenkins
2019-06-26 05:24:47 +08:00
"eslint-plugin-react-hooks": "^1",
[npm dependencies] update all our npm dependencies This is just the regular “update all the things” commit. For things in package.json that we just want the latest version of, I changed them to a simple major with a carat. (Eg: “8^” or “4^”), that way you can see easier which things are specifically locked down To a specific version (or range of versions) for a reason. Test plan: * automated specs & build tasks should work Change-Id: Id7a3f853bd0f7537cc0f08d7dba8d6726b836c44 Reviewed-on: https://gerrit.instructure.com/141653 Tested-by: Jenkins Reviewed-by: Brent Burgoyne <bburgoyne@instructure.com> QA-Review: Brent Burgoyne <bburgoyne@instructure.com> Product-Review: Brent Burgoyne <bburgoyne@instructure.com>
2018-02-23 03:58:38 +08:00
"exports-loader": "^0.7",
remove "exports" from all @instructure/ packages refs FOO-1331 refs LS-1657 flag = none test plan: canvas-rce mocha tests work after upgrading to inst-ui 7 Change-Id: Ibe8d94fdd5a994fda2c7b9703dccfb77a62415ca Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/256766 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Ed Schiebel <eschiebel@instructure.com> QA-Review: Ed Schiebel <eschiebel@instructure.com> Product-Review: Simon Williams <simon@instructure.com>
2021-01-15 05:29:41 +08:00
"fast-glob": "^3.2.4",
upgrade fetch-mock flag=none closes CFA-36 Change-Id: I472d3474e743ca8867ea3434154aa598293f1db1 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/336880 Reviewed-by: Paul Gray <paul.gray@instructure.com> QA-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Product-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com>
2024-01-07 23:29:44 +08:00
"fetch-mock": "^9",
upgrade some NPM dependencies Change-Id: If2a90959713e292a46c9d5e9c75c89a37f7316b6 Reviewed-on: https://gerrit.instructure.com/205007 Tested-by: Jenkins Reviewed-by: Cameron Matheson <cameron@instructure.com> QA-Review: Ryan Shaw <ryan@instructure.com> Product-Review: Ryan Shaw <ryan@instructure.com>
2019-08-14 13:36:39 +08:00
"file-loader": "^4",
catch and report on rogue imports fixes FOO-2422 this patch codifies the access rules between modules in the new UI file structure: packages/ can be accessed by everyone ui/shared/ can only be accessed by Canvas packages and features ui/features/ can only be accessed by boot ui/boot/ can only be accessed by entrypoint ui/index.js can only be accessed by Rails additionally, the specifiers used for importing may no longer be arbitrary; generally, every enapsulated folder must use relative specifiers for intra-imports, and bare specifiers for inter-imports ui/features/a/a.js => ui/features/a/b.js [via] ./b.js ui/features/a/a.js => ui/shared/a/a.js [via] @canvas/a/a ui/features/a/a.js => packages/a/a.js [via] a/a the rules are defined in the webpack config file, there are currently 37 violations that we have to address, for now I added a plugin to ignore them (see frontend_build/existingEncapsulationErrors.json) violations are reported with a detailed description of what exactly caused the violation, what is being violated, along with a suggestion on how to address it - see https://github.com/instructure/esmac for the tool that applies the rules - see https://github.com/instructure/webpack-encapsulation-plugin for the webpack implementation of that tool ~ test plan ~ ~~~^ ^~~~ \m/ edit frontend_build/existingEncapsulationErrors.json and remove entries from there, or alternatively just disable the IgnoreErrors plugin to get all the errors displayed, then rerun webpack against the offending source file to view the error report - for example: npx webpack --entry=$PWD/packages/backbone-identity-map/index.js # or, if u chose to disable the plugin npx webpack the messages should be clear and helpful; there are currently 4 scenarios for access violation, and 4 scenarios for specifier mismatche Change-Id: Ibae4245122e2c015ccbd47d73ac8689e0a386d86 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/275200 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Charley Kline <ckline@instructure.com> QA-Review: Charley Kline <ckline@instructure.com> Product-Review: Charley Kline <ckline@instructure.com>
2021-10-02 07:28:20 +08:00
"find-up": "^5.0.0",
update gglobby npm dep refs: CNVS-29725 test plan: * run `node script/xsslint.js` * it should work (this is ran by jenkins so reall if it passes, it is good) Change-Id: Ib9b68e486c32c91e3c430cea095a628daf51db2b Reviewed-on: https://gerrit.instructure.com/87181 Tested-by: Jenkins Reviewed-by: Clay Diffrient <cdiffrient@instructure.com> Product-Review: Ryan Shaw <ryan@instructure.com> QA-Review: Ryan Shaw <ryan@instructure.com>
2016-08-09 07:39:19 +08:00
"gglobby": "0.0.3",
[npm dependencies] update all our npm dependencies This is just the regular “update all the things” commit. For things in package.json that we just want the latest version of, I changed them to a simple major with a carat. (Eg: “8^” or “4^”), that way you can see easier which things are specifically locked down To a specific version (or range of versions) for a reason. Test plan: * automated specs & build tasks should work Change-Id: Id7a3f853bd0f7537cc0f08d7dba8d6726b836c44 Reviewed-on: https://gerrit.instructure.com/141653 Tested-by: Jenkins Reviewed-by: Brent Burgoyne <bburgoyne@instructure.com> QA-Review: Brent Burgoyne <bburgoyne@instructure.com> Product-Review: Brent Burgoyne <bburgoyne@instructure.com>
2018-02-23 03:58:38 +08:00
"glob": "^7",
[node12] upgrade gulp refs FOO-1116 flag = none verified contents of public/dist/ are intact across versions with a cmd like this: find ./public/dist -type f -exec md5sum {} + | awk '{print $1}' | md5sum == TEST PLAN run "npx gulp rev" and verify it still works == BONUS TEST PLAN wipe out node_modules/, run "rake canvas compile:assets" and verify that still works. Change-Id: Ie072e415a89478e58a98b04b7826f974ba63f904 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/253041 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Simon Williams <simon@instructure.com> QA-Review: Simon Williams <simon@instructure.com> Product-Review: Simon Williams <simon@instructure.com>
2020-10-15 04:59:13 +08:00
"gulp": "^4",
[npm dependencies] update all our npm dependencies This is just the regular “update all the things” commit. For things in package.json that we just want the latest version of, I changed them to a simple major with a carat. (Eg: “8^” or “4^”), that way you can see easier which things are specifically locked down To a specific version (or range of versions) for a reason. Test plan: * automated specs & build tasks should work Change-Id: Id7a3f853bd0f7537cc0f08d7dba8d6726b836c44 Reviewed-on: https://gerrit.instructure.com/141653 Tested-by: Jenkins Reviewed-by: Brent Burgoyne <bburgoyne@instructure.com> QA-Review: Brent Burgoyne <bburgoyne@instructure.com> Product-Review: Brent Burgoyne <bburgoyne@instructure.com>
2018-02-23 03:58:38 +08:00
"gulp-file": "^0.4",
[node12] upgrade gulp refs FOO-1116 flag = none verified contents of public/dist/ are intact across versions with a cmd like this: find ./public/dist -type f -exec md5sum {} + | awk '{print $1}' | md5sum == TEST PLAN run "npx gulp rev" and verify it still works == BONUS TEST PLAN wipe out node_modules/, run "rake canvas compile:assets" and verify that still works. Change-Id: Ie072e415a89478e58a98b04b7826f974ba63f904 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/253041 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Simon Williams <simon@instructure.com> QA-Review: Simon Williams <simon@instructure.com> Product-Review: Simon Williams <simon@instructure.com>
2020-10-15 04:59:13 +08:00
"gulp-filter": "^6",
[npm dependencies] update all our npm dependencies This is just the regular “update all the things” commit. For things in package.json that we just want the latest version of, I changed them to a simple major with a carat. (Eg: “8^” or “4^”), that way you can see easier which things are specifically locked down To a specific version (or range of versions) for a reason. Test plan: * automated specs & build tasks should work Change-Id: Id7a3f853bd0f7537cc0f08d7dba8d6726b836c44 Reviewed-on: https://gerrit.instructure.com/141653 Tested-by: Jenkins Reviewed-by: Brent Burgoyne <bburgoyne@instructure.com> QA-Review: Brent Burgoyne <bburgoyne@instructure.com> Product-Review: Brent Burgoyne <bburgoyne@instructure.com>
2018-02-23 03:58:38 +08:00
"gulp-insert": "^0.5",
[node12] upgrade gulp refs FOO-1116 flag = none verified contents of public/dist/ are intact across versions with a cmd like this: find ./public/dist -type f -exec md5sum {} + | awk '{print $1}' | md5sum == TEST PLAN run "npx gulp rev" and verify it still works == BONUS TEST PLAN wipe out node_modules/, run "rake canvas compile:assets" and verify that still works. Change-Id: Ie072e415a89478e58a98b04b7826f974ba63f904 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/253041 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Simon Williams <simon@instructure.com> QA-Review: Simon Williams <simon@instructure.com> Product-Review: Simon Williams <simon@instructure.com>
2020-10-15 04:59:13 +08:00
"gulp-load-plugins": "^2",
"gulp-rename": "^2",
"gulp-rev": "^9",
[npm dependencies] update all our npm dependencies This is just the regular “update all the things” commit. For things in package.json that we just want the latest version of, I changed them to a simple major with a carat. (Eg: “8^” or “4^”), that way you can see easier which things are specifically locked down To a specific version (or range of versions) for a reason. Test plan: * automated specs & build tasks should work Change-Id: Id7a3f853bd0f7537cc0f08d7dba8d6726b836c44 Reviewed-on: https://gerrit.instructure.com/141653 Tested-by: Jenkins Reviewed-by: Brent Burgoyne <bburgoyne@instructure.com> QA-Review: Brent Burgoyne <bburgoyne@instructure.com> Product-Review: Brent Burgoyne <bburgoyne@instructure.com>
2018-02-23 03:58:38 +08:00
"gulp-sourcemaps": "^2",
"gulp-uglify": "^3",
Upgrade instructure-ui to 1.0 fixes CNVS-34969 test plan: - go /profile/settings and turn on high contrast - go to the course people page (/courses/#/users) - click on the +People button > expected result: the modal honors high contrast - enter some text in he text area > expected result: nothing bad happens, as the event handler for TextArea has changed. - there's a TextArea in MessageStudents also, but I don't know where to find it in the UI. You should probalby test it doesn't blow up either. Change-Id: Ia8102dacfa2b01ee043002ee0f5c27943abe5743 Reviewed-on: https://gerrit.instructure.com/102133 Tested-by: Jenkins Reviewed-by: Ryan Shaw <ryan@instructure.com> QA-Review: Dan Sasaki Product-Review: Ryan Shaw <ryan@instructure.com> Product-Review: Ed Schiebel <eschiebel@instructure.com>
2017-02-15 05:54:51 +08:00
"handlebars": "1.3.0",
Install Vitest This does not yet change our build process Demo: - yarn run test:vitest:watch ui/features/theme_editor/ Test plan: - build passes Closes CFA-17 flag=none Change-Id: I6eac4684af62525829e36f5dd0c64bb80c638ca3 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/333130 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Martin Ochoa <martin.ochoa@instructure.com> Reviewed-by: Gustavo Bernardes <gustavo.bernardes@instructure.com> QA-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Product-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Build-Review: Andrea Cirulli <andrea.cirulli@instructure.com>
2023-11-17 20:54:42 +08:00
"happy-dom": "^12.10.3",
[npm dependencies] update all our npm dependencies This is just the regular “update all the things” commit. For things in package.json that we just want the latest version of, I changed them to a simple major with a carat. (Eg: “8^” or “4^”), that way you can see easier which things are specifically locked down To a specific version (or range of versions) for a reason. Test plan: * automated specs & build tasks should work Change-Id: Id7a3f853bd0f7537cc0f08d7dba8d6726b836c44 Reviewed-on: https://gerrit.instructure.com/141653 Tested-by: Jenkins Reviewed-by: Brent Burgoyne <bburgoyne@instructure.com> QA-Review: Brent Burgoyne <bburgoyne@instructure.com> Product-Review: Brent Burgoyne <bburgoyne@instructure.com>
2018-02-23 03:58:38 +08:00
"imports-loader": "^0.8",
Add a way to generate better js coverage This should pick up coverage from both karma and jest in Canvas proper. It should also pick up coverage from anything under packages/* closes CORE-1265 Test Plan: - Run `COVERAGE=true yarn test` - Coverage reports (coverage-final.json) should generate in all packages such as (canvas-planner) as well as in coverage-karma and coverage-jest - Run `yarn run test:coverage` - coverage-js folder should be generated. Opening index.html should show the full coverage report - Remove coverage-{js, karma, jest} and packages/canvas-planner/coverage as well as .nyc_output to get back to a clean state - Run `RUN_TESTS_FIRST=true yarn run test:coverage` - All tests should run and generate the appropriate report just like the last time in coverage-js Change-Id: I50744b8977e0683e079af5bdd2865dbcd6ad9066 Reviewed-on: https://gerrit.instructure.com/146098 Tested-by: Jenkins Reviewed-by: Ryan Shaw <ryan@instructure.com> QA-Review: Jeremy Putnam <jeremyp@instructure.com> Product-Review: Clay Diffrient <cdiffrient@instructure.com>
2018-04-06 05:27:42 +08:00
"istanbul-merge": "^1.1.1",
Upgrade Jest Test plan: - build passes flag=none Change-Id: I3855883ee1ec15e3de8076712c399793974108ad Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/333290 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Martin Ochoa <martin.ochoa@instructure.com> QA-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Product-Review: Aaron Shafovaloff <ashafovaloff@instructure.com>
2023-11-21 04:28:13 +08:00
"jest": "^29.7.0",
upgrade some NPM dependencies Change-Id: If2a90959713e292a46c9d5e9c75c89a37f7316b6 Reviewed-on: https://gerrit.instructure.com/205007 Tested-by: Jenkins Reviewed-by: Cameron Matheson <cameron@instructure.com> QA-Review: Ryan Shaw <ryan@instructure.com> Product-Review: Ryan Shaw <ryan@instructure.com>
2019-08-14 13:36:39 +08:00
"jest-canvas-mock": "^2",
upgrade jest to v28 refs DE-1284 Change-Id: I6f91f5d986d51d73a809cba9fd93355a6f8de7a4 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/296476 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Andrea Cirulli <andrea.cirulli@instructure.com> QA-Review: Aaron Ogata <aogata@instructure.com> Product-Review: Aaron Ogata <aogata@instructure.com>
2022-07-19 06:07:53 +08:00
"jest-config": "^28",
Upgrade Jest Test plan: - build passes flag=none Change-Id: I3855883ee1ec15e3de8076712c399793974108ad Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/333290 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Martin Ochoa <martin.ochoa@instructure.com> QA-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Product-Review: Aaron Shafovaloff <ashafovaloff@instructure.com>
2023-11-21 04:28:13 +08:00
"jest-environment-jsdom": "^29.7.0",
add overrides and editing to bulk assignment edit closes LA-847 flag=assignment_bulk_edit test plan: - Assignments and their overrides should be displayed with their dates - Each date input should function and work independently Change-Id: Ia2206bcae8b462535e3bcc99bf024bfaae39bc3e Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/230953 QA-Review: Anju Reddy <areddy@instructure.com> Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Product-Review: Jon Willesen <jonw+gerrit@instructure.com> Reviewed-by: Augusto Callejas <acallejas@instructure.com> Reviewed-by: Ed Schiebel <eschiebel@instructure.com>
2020-03-23 11:42:21 +08:00
"jest-fetch-mock": "^3.0.3",
upgrade some NPM dependencies Change-Id: If2a90959713e292a46c9d5e9c75c89a37f7316b6 Reviewed-on: https://gerrit.instructure.com/205007 Tested-by: Jenkins Reviewed-by: Cameron Matheson <cameron@instructure.com> QA-Review: Ryan Shaw <ryan@instructure.com> Product-Review: Ryan Shaw <ryan@instructure.com>
2019-08-14 13:36:39 +08:00
"jest-junit": "^7",
[npm dependencies] update all our npm dependencies This is just the regular “update all the things” commit. For things in package.json that we just want the latest version of, I changed them to a simple major with a carat. (Eg: “8^” or “4^”), that way you can see easier which things are specifically locked down To a specific version (or range of versions) for a reason. Test plan: * automated specs & build tasks should work Change-Id: Id7a3f853bd0f7537cc0f08d7dba8d6726b836c44 Reviewed-on: https://gerrit.instructure.com/141653 Tested-by: Jenkins Reviewed-by: Brent Burgoyne <bburgoyne@instructure.com> QA-Review: Brent Burgoyne <bburgoyne@instructure.com> Product-Review: Brent Burgoyne <bburgoyne@instructure.com>
2018-02-23 03:58:38 +08:00
"jest-localstorage-mock": "^2",
Extract jest-moxios-utils to its own package closes CORE-2217 Test Plan: - Automated tests pass Change-Id: Icba5c61344e22e8a8e4929b9133c9a2b89a80ef9 Reviewed-on: https://gerrit.instructure.com/174135 Tested-by: Jenkins Reviewed-by: Jon Willesen <jonw+gerrit@instructure.com> QA-Review: Clay Diffrient <cdiffrient@instructure.com> Product-Review: Clay Diffrient <cdiffrient@instructure.com>
2018-12-04 23:19:46 +08:00
"jest-moxios-utils": "^1",
Necessary tweaks I discovered adding the CanvasRce component to a page closes MAT-277 flag=rce_enhancements Factored these changes out of the changes I had to make for MAT-253 where the CanvasRce component was put on a real page and tested. 1. update jest.config.js to mock the tinymce-react Editor component 2. add a missing dependency to package.json 3. tweak tests to use the new mock 4. use safe-dereference operator in places where specs might not have a fully formed ENV test plan: - this is a tough one. It has to pass jenkins, but beyond that it will take the changes for MAT-253 to prove these changes do all we need Change-Id: I5804d1a1f13dbfbc21a3213db92d7afe74e576e6 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/267427 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Gary Mei <gmei@instructure.com> QA-Review: Gary Mei <gmei@instructure.com> Product-Review: Ed Schiebel <eschiebel@instructure.com>
2021-06-22 03:07:58 +08:00
"jsdom-global": "^3.0.2",
[npm dependencies] update all our npm dependencies This is just the regular “update all the things” commit. For things in package.json that we just want the latest version of, I changed them to a simple major with a carat. (Eg: “8^” or “4^”), that way you can see easier which things are specifically locked down To a specific version (or range of versions) for a reason. Test plan: * automated specs & build tasks should work Change-Id: Id7a3f853bd0f7537cc0f08d7dba8d6726b836c44 Reviewed-on: https://gerrit.instructure.com/141653 Tested-by: Jenkins Reviewed-by: Brent Burgoyne <bburgoyne@instructure.com> QA-Review: Brent Burgoyne <bburgoyne@instructure.com> Product-Review: Brent Burgoyne <bburgoyne@instructure.com>
2018-02-23 03:58:38 +08:00
"json-loader": "^0.5.7",
upgrade karma test plan: build passes flag=none Change-Id: I8f55629bc0967b8ffb73fd144164869efe43d064 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/335099 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> QA-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Product-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Reviewed-by: Drake Harper <drake.harper@instructure.com>
2023-12-12 03:58:36 +08:00
"karma": "^6.4.2",
[npm dependencies] update all our npm dependencies This is just the regular “update all the things” commit. For things in package.json that we just want the latest version of, I changed them to a simple major with a carat. (Eg: “8^” or “4^”), that way you can see easier which things are specifically locked down To a specific version (or range of versions) for a reason. Test plan: * automated specs & build tasks should work Change-Id: Id7a3f853bd0f7537cc0f08d7dba8d6726b836c44 Reviewed-on: https://gerrit.instructure.com/141653 Tested-by: Jenkins Reviewed-by: Brent Burgoyne <bburgoyne@instructure.com> QA-Review: Brent Burgoyne <bburgoyne@instructure.com> Product-Review: Brent Burgoyne <bburgoyne@instructure.com>
2018-02-23 03:58:38 +08:00
"karma-chrome-launcher": "^2",
the regular “update all the npm things” commit this updates all the stuff we get from npm that we _can_ upgrade to the newest versions available. test plan: * all the builds should pass Change-Id: Icf1cc3cd02d66e6e1f999ea5f5fc3b5b28775881 Reviewed-on: https://gerrit.instructure.com/167282 Reviewed-by: Steven Burnett <sburnett@instructure.com> Tested-by: Jenkins QA-Review: Ryan Shaw <ryan@instructure.com> Product-Review: Ryan Shaw <ryan@instructure.com>
2018-10-04 07:01:30 +08:00
"karma-coverage-istanbul-reporter": "^2",
[npm dependencies] update all our npm dependencies This is just the regular “update all the things” commit. For things in package.json that we just want the latest version of, I changed them to a simple major with a carat. (Eg: “8^” or “4^”), that way you can see easier which things are specifically locked down To a specific version (or range of versions) for a reason. Test plan: * automated specs & build tasks should work Change-Id: Id7a3f853bd0f7537cc0f08d7dba8d6726b836c44 Reviewed-on: https://gerrit.instructure.com/141653 Tested-by: Jenkins Reviewed-by: Brent Burgoyne <bburgoyne@instructure.com> QA-Review: Brent Burgoyne <bburgoyne@instructure.com> Product-Review: Brent Burgoyne <bburgoyne@instructure.com>
2018-02-23 03:58:38 +08:00
"karma-junit-reporter": "^1",
Update yarn.lock with newest versions of deps closes: CNVS-38384 This is just to keep our tooling up to date Test plan: * automated tests should pass * build tooling should work (meaning webpack builds In prod & dev) Change-Id: I11fbda35827487e59712c762a71540a51258d1db Reviewed-on: https://gerrit.instructure.com/120434 Tested-by: Jenkins Reviewed-by: Simon Williams <simon@instructure.com> Product-Review: Ryan Shaw <ryan@instructure.com> QA-Review: Ryan Shaw <ryan@instructure.com>
2017-07-26 01:29:52 +08:00
"karma-qunit": "~1.2.1",
use selenium grid for karma tests refs DE-1334 Change-Id: I61e78a60498b9fd64ea9d5333504c4db10c8c03f Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/298285 Reviewed-by: Andrea Cirulli <andrea.cirulli@instructure.com> Build-Review: Andrea Cirulli <andrea.cirulli@instructure.com> Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> QA-Review: Aaron Ogata <aogata@instructure.com> Product-Review: Aaron Ogata <aogata@instructure.com>
2022-08-11 02:15:25 +08:00
"karma-selenium-grid-launcher": "^0.3.0",
[npm dependencies] update all our npm dependencies This is just the regular “update all the things” commit. For things in package.json that we just want the latest version of, I changed them to a simple major with a carat. (Eg: “8^” or “4^”), that way you can see easier which things are specifically locked down To a specific version (or range of versions) for a reason. Test plan: * automated specs & build tasks should work Change-Id: Id7a3f853bd0f7537cc0f08d7dba8d6726b836c44 Reviewed-on: https://gerrit.instructure.com/141653 Tested-by: Jenkins Reviewed-by: Brent Burgoyne <bburgoyne@instructure.com> QA-Review: Brent Burgoyne <bburgoyne@instructure.com> Product-Review: Brent Burgoyne <bburgoyne@instructure.com>
2018-02-23 03:58:38 +08:00
"karma-sourcemap-loader": "^0.3",
publish jUnit test result file from karma tests Test plan: * run `yarn test` * there should be xml file in coverage-js/karma-test-results.xml With the spec results that we will use for Jenkins builds Change-Id: Ic68de197d2b52dbccdf58dc2d148aef1f2ca2646 Reviewed-on: https://gerrit.instructure.com/135949 Tested-by: Jenkins Reviewed-by: Robert Lamb <rlamb@instructure.com> Product-Review: Ryan Shaw <ryan@instructure.com> QA-Review: Ryan Shaw <ryan@instructure.com>
2017-12-18 23:21:42 +08:00
"karma-spec-reporter": "^0.0.32",
Update yarn.lock with newest versions of deps closes: CNVS-38384 This is just to keep our tooling up to date Test plan: * automated tests should pass * build tooling should work (meaning webpack builds In prod & dev) Change-Id: I11fbda35827487e59712c762a71540a51258d1db Reviewed-on: https://gerrit.instructure.com/120434 Tested-by: Jenkins Reviewed-by: Simon Williams <simon@instructure.com> Product-Review: Ryan Shaw <ryan@instructure.com> QA-Review: Ryan Shaw <ryan@instructure.com>
2017-07-26 01:29:52 +08:00
"karma-verbose-reporter": "^0.0.6",
(webpack) upgrade to webpack 5 refs FOO-2835 flag = none there are no behavioral changes, only what was necessary to do the upgrade, see inline comments for explanation where it was warranted Change-Id: I737f31a210365f190ddb606e96e8eb84e2359e0d Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/294133 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Aaron Ogata <aogata@instructure.com> Reviewed-by: Charley Kline <ckline@instructure.com> QA-Review: Aaron Ogata <aogata@instructure.com> Product-Review: Aaron Ogata <aogata@instructure.com>
2022-06-17 13:54:48 +08:00
"karma-webpack": "^5",
upgrade some NPM dependencies Change-Id: If2a90959713e292a46c9d5e9c75c89a37f7316b6 Reviewed-on: https://gerrit.instructure.com/205007 Tested-by: Jenkins Reviewed-by: Cameron Matheson <cameron@instructure.com> QA-Review: Ryan Shaw <ryan@instructure.com> Product-Review: Ryan Shaw <ryan@instructure.com>
2019-08-14 13:36:39 +08:00
"lint-staged": "^9",
rework handlebars dependency on brandable_css refs FOO-1116 right now in order to build the javascript, we must run brandable_css first for the specific purpose of injecting into handlebars templates their corresponding stylesheet file with the checksum as reported by brandable_css this patch moves things around such that Rails provides this mapping of "handlebars template" to "CSS variant file checksums" in a global variable (Rails is privy to this information already), webpack then at build time injects only a reference to that mapping into the template, then our runtime brandable-css JS helper will resolve that reference from the mapping and request the correct file based on the current user's variant [1] rails assigns window.BRANDABLE_CSS_HANDLEBARS_INDEX with content like this: [ [ "new_styles_normal_contrast", "new_styles_high_contrast", ... ], { "0c": ["0f4f01ab86", 0, 0, "e3e7211701", 3, ... ], ... } ] the structure of the mapping is explained in brandable_css[1], it is a bit overtuned to reduce the size as much as possible since this is included for ALL pages even though the templates in question may never be rendered (right now it's ~1.5kB and should never grow) [2] webpack asks @canvas/brandable-css to loadStylesheetForJST using the contrived id for that file (frontend_build/i18nLinerHandlebars.js:92) [3] brandable-css/index.js will decode that structure to arrive at the exact URL for the stylesheet for that template for the current user variant with this , we should be able to optimize "rake canvas:compile_assets" to run both brandable_css and webpack in parallel, which will greatly mitigate the performance decrease from moving from node-sass to dart-sass == test plan go to some assignment's syllabus page, edit the file app/stylesheets/jst/courses/Syllabus.scss with something fun like: #syllabus .day_date { background: $fire; } rerun `npx brandable_css`, reload the page and verify it's on fire, optionally change your setting to enable High Contrast mode, reload the syllabus page and verify the color changes (it picks up the other variant stylesheet) [1]: https://github.com/instructure/brandable_css/pull/4/commits/80af6e70af6ad60312187f256c2457d33ca75202 Change-Id: Ie48cc71d4837ee02313b2d45a9ad2944725acad2 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/268615 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: August Thornton <august@instructure.com> QA-Review: August Thornton <august@instructure.com> Product-Review: August Thornton <august@instructure.com>
2021-07-08 08:03:09 +08:00
"loader-utils": "^1",
Enables adding alt text to image uploads It also allows editing other a11y features, like making the image presentational or embedding it as a link. It splits out the Image Options form from the editor tray to avoid copy/pasting too much. The logic and state are still separated between the upload and edit forms, since they don't overlap super well. It also edits the logic around uploading and embedding images to support the extra attributes. A few Jest tests were added to check for appropriate attributes being added. Test Plan: With RCE Enhancements enabled, visit an RCE page Open the image upload modal and choose an image Notice the image attributes form underneath. Add alt text. Adjust the other attributes as desired. Upload the image Open the Raw HTML Editor. Notice that the alt text is added to your image, along with whatever other attributes you changed. Decoration Images are given the `role="presentation"` attribute; Display As "Link" embeds the image as a link. Fixes LS-445 flag = rce_enhancements Change-Id: I462e2c322a3b39fc4fa9f47b675426c581c3a398 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/242736 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Jeremy Stanley <jeremy@instructure.com> QA-Review: Robin Kuss <rkuss@instructure.com> Product-Review: Peyton Craighill <pcraighill@instructure.com>
2020-07-16 05:11:24 +08:00
"merge-stream": "^2",
catch and report on rogue imports fixes FOO-2422 this patch codifies the access rules between modules in the new UI file structure: packages/ can be accessed by everyone ui/shared/ can only be accessed by Canvas packages and features ui/features/ can only be accessed by boot ui/boot/ can only be accessed by entrypoint ui/index.js can only be accessed by Rails additionally, the specifiers used for importing may no longer be arbitrary; generally, every enapsulated folder must use relative specifiers for intra-imports, and bare specifiers for inter-imports ui/features/a/a.js => ui/features/a/b.js [via] ./b.js ui/features/a/a.js => ui/shared/a/a.js [via] @canvas/a/a ui/features/a/a.js => packages/a/a.js [via] a/a the rules are defined in the webpack config file, there are currently 37 violations that we have to address, for now I added a plugin to ignore them (see frontend_build/existingEncapsulationErrors.json) violations are reported with a detailed description of what exactly caused the violation, what is being violated, along with a suggestion on how to address it - see https://github.com/instructure/esmac for the tool that applies the rules - see https://github.com/instructure/webpack-encapsulation-plugin for the webpack implementation of that tool ~ test plan ~ ~~~^ ^~~~ \m/ edit frontend_build/existingEncapsulationErrors.json and remove entries from there, or alternatively just disable the IgnoreErrors plugin to get all the errors displayed, then rerun webpack against the offending source file to view the error report - for example: npx webpack --entry=$PWD/packages/backbone-identity-map/index.js # or, if u chose to disable the plugin npx webpack the messages should be clear and helpful; there are currently 4 scenarios for access violation, and 4 scenarios for specifier mismatche Change-Id: Ibae4245122e2c015ccbd47d73ac8689e0a386d86 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/275200 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Charley Kline <ckline@instructure.com> QA-Review: Charley Kline <ckline@instructure.com> Product-Review: Charley Kline <ckline@instructure.com>
2021-10-02 07:28:20 +08:00
"micromatch": "^4.0.4",
extend JS source files without relying on filepath fixes FOO-1435 flag = none instead of the bundler inferring the source file that an extension is meant for based on filepath, a plugin is now expected to explicitly map each source file to the extension file in its package.json manifest { "canvas": { "source-file-extensions": { "path/to/a.js": "path/to/extension-to-a.js" } } } this allows extensions to continue working even when the path of the source file no longer matches that of the extension inside the plugin == test plan - visit a page that contains an extended module and verify the extension is still applied Change-Id: Ida7d75b87aedc519502c969e6912a335af69abc0 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/256222 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Simon Williams <simon@instructure.com> QA-Review: Simon Williams <simon@instructure.com> Product-Review: Simon Williams <simon@instructure.com>
2021-01-07 01:40:57 +08:00
"mkdirp": "^1.0.4",
Pass correct locale to Planner Sometimes ENV.LOCALE and ENV.MOMENT_LOCALE are different (zh-Hans v zh-cn or mi v mi-nz). We were passing the former to planner, but moment needs the full locale, including language and region identifiers, and formatMessage copes with the full locale just fine, so we really need to pass in the latter or moment eventually blows up. So mi-nz month names would successfully parse, had to both bump our version of moment and tweak the canvas customized mi-nz locale data. to test, you'll have to run yarn to update moment, then build with RAILS_LOAD_ALL_LOCALES=1 yarn build Note on the changes to timezoneSpec.js: - some of the specs were parsing dates like "Mon, Aug 3", which are being interpreted in the current year, when Aut 3 is not a Monday. Resolved this by using MockDate to pretend today is 2/1/2015 - moment does not always interpret the Chinese characters for evening as implying PM. I'm assuming canvas will never need that particular construct and commented out the failing string. - there's one date-time that's getting the date totally wrong. - Fixed grammatically incorrect instances of '8月 3, 2015' to ''8月 3日, 2015' - fix cases where the year is coming after the month and day, which would never really happen fixes ADMIN-1331 test plan: - have a student in course so planner is enabled. - go to /profile/settings and Edit - change the Language to Reo Māori (Aotearoa) and "Update Settings" - go to the planner dashboard - click on + to create a new todo > expect you can create a todo. If you want, you can repeat with any of the languages listed in the ticket just to prove ^that wasn't a fluke. Change-Id: I9ba069ef61529088ab92271d7857998df6bbc409 Reviewed-on: https://gerrit.instructure.com/161206 Tested-by: Jenkins Reviewed-by: Ryan Shaw <ryan@instructure.com> Reviewed-by: Mysti Sadler <mysti@instructure.com> Reviewed-by: Jeremy Stanley <jeremy@instructure.com> QA-Review: Anju Reddy <areddy@instructure.com> Product-Review: Ed Schiebel <eschiebel@instructure.com>
2018-08-18 03:21:04 +08:00
"mockdate": "^2.0.2",
replace webpack with rspack test plan: - run rspack locally (as "webpack" for now) - ensure coverage data for crystalball - ensure build passes with skip-crystalball - ensure source maps for local dev - ensure bundle analysis is available and documented - ensure compile times are at least comparable refs CFA-32 [skip-crystalball] flag=none Change-Id: I8ad916ac7fbe9e3ecee5c690abcd78cdde748ab6 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/339401 Reviewed-by: Isaac Moore <isaac.moore@instructure.com> Build-Review: Isaac Moore <isaac.moore@instructure.com> Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> QA-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Product-Review: Aaron Shafovaloff <ashafovaloff@instructure.com>
2024-02-01 04:19:23 +08:00
"moment-timezone-data-webpack-plugin": "^1.5.1",
[npm dependencies] update all our npm dependencies This is just the regular “update all the things” commit. For things in package.json that we just want the latest version of, I changed them to a simple major with a carat. (Eg: “8^” or “4^”), that way you can see easier which things are specifically locked down To a specific version (or range of versions) for a reason. Test plan: * automated specs & build tasks should work Change-Id: Id7a3f853bd0f7537cc0f08d7dba8d6726b836c44 Reviewed-on: https://gerrit.instructure.com/141653 Tested-by: Jenkins Reviewed-by: Brent Burgoyne <bburgoyne@instructure.com> QA-Review: Brent Burgoyne <bburgoyne@instructure.com> Product-Review: Brent Burgoyne <bburgoyne@instructure.com>
2018-02-23 03:58:38 +08:00
"moxios": "^0.4",
upgrade msw flag=none closes CFA-35 closes LF-1117 Change-Id: I42e65f70ee74a2931a0a4439a4c9c0f22466ef62 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/336892 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Caleb Guanzon <cguanzon@instructure.com> Product-Review: Caleb Guanzon <cguanzon@instructure.com> QA-Review: Aaron Shafovaloff <ashafovaloff@instructure.com>
2024-01-08 09:23:15 +08:00
"msw": "^2.0.12",
the regular “update all the npm things” commit this updates all the stuff we get from npm that we _can_ upgrade to the newest versions available. test plan: * all the builds should pass Change-Id: Icf1cc3cd02d66e6e1f999ea5f5fc3b5b28775881 Reviewed-on: https://gerrit.instructure.com/167282 Reviewed-by: Steven Burnett <sburnett@instructure.com> Tested-by: Jenkins QA-Review: Ryan Shaw <ryan@instructure.com> Product-Review: Ryan Shaw <ryan@instructure.com>
2018-10-04 07:01:30 +08:00
"nyc": "^13",
patch format-message to fix CJS issue Change-Id: Id955360efbd116835f51fe48c53ff8cf221f956c Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/338375 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Michael Hulse <michael.hulse@instructure.com> QA-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Product-Review: Aaron Shafovaloff <ashafovaloff@instructure.com>
2024-01-23 07:00:30 +08:00
"patch-package": "^8.0.0",
"postinstall-postinstall": "^2.1.0",
Revert "Upgrade prettier" This reverts commit 2923619f64252dff64c12411cc663bcfff347e26. Change-Id: I73be26acb7c5288293a8027bf1289b8014988935 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/334698 Reviewed-by: Michael Hulse <michael.hulse@instructure.com> QA-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Product-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com>
2023-12-12 09:27:52 +08:00
"prettier": "^2.8.8",
Upgrade QUnit so we can use new methods Test plan: - All tests pass flag=none Change-Id: I5b361d05fbcd1f186c75d47fd27115dcf8659a74 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/278071 Reviewed-by: Ahmad Amireh <ahmad@instructure.com> QA-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Product-Review: Syed Hussain <shussain@instructure.com> Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com>
2021-11-12 06:04:35 +08:00
"qunitjs": "^1.23.0",
move planner to ui/shared test plan: - smoke test of planner - build passes flag=none Change-Id: I1ccab60a53269adaa4247658696ee080e4e03fae Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/323860 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> QA-Review: Caleb Guanzon <cguanzon@instructure.com> QA-Review: Michael Hulse <michael.hulse@instructure.com> Product-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Reviewed-by: Ed Schiebel <eschiebel@instructure.com>
2023-07-29 01:57:25 +08:00
"react-moment-proptypes": "^1.4.0",
upgrade react from 15.x to 16.x closes: CORE-1874 test plan: Now that the automated selenium & javascript specs pass for this the last thing we need to do is to go manually click around and see if anything breaks. The best thing to do would be to open your browser console and look for errors. Deprecation warnings or propType errors or react warnings are fine but if any actual errors get thrown that is something we want to look into. specific things to look at: * all the gradezilla/gradebook/grading stuff (specifically things that have instUI <NumberInput>s and <Select>s) * look at the submission cell editor * the gb headers (especially make sure keyboard navigation works how it should) * moderated grading * grading perid edit page / enrollment terms * speedgrader * grading standards * gradebook history * theme editor * new discussions/announcements * the new permissions page * the dasboard * student planner * dashcards * global nav trays * help menu * assignment edit page * account user/course search Change-Id: I6a1fe7df9379d9c601eda932bd8cef9c06d10cd2 Reviewed-on: https://gerrit.instructure.com/163913 Reviewed-by: Clay Diffrient <cdiffrient@instructure.com> Tested-by: Jenkins QA-Review: Jeremy Putnam <jeremyp@instructure.com> QA-Review: Tucker McKnight <tmcknight@instructure.com> Product-Review: Clay Diffrient <cdiffrient@instructure.com> Product-Review: Ryan Shaw <ryan@instructure.com>
2018-09-11 12:13:01 +08:00
"react-test-renderer": "^16",
move planner to ui/shared test plan: - smoke test of planner - build passes flag=none Change-Id: I1ccab60a53269adaa4247658696ee080e4e03fae Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/323860 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> QA-Review: Caleb Guanzon <cguanzon@instructure.com> QA-Review: Michael Hulse <michael.hulse@instructure.com> Product-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Reviewed-by: Ed Schiebel <eschiebel@instructure.com>
2023-07-29 01:57:25 +08:00
"redux-devtools-extension": "^2.13.2",
Update redux-logger to 3.0.6 test plan: - automated tests pass Change-Id: Iaf8b223e7c60a43f5b4e10561d5d66643a312992 Reviewed-on: https://gerrit.instructure.com/173817 Tested-by: Jenkins Product-Review: Clay Diffrient <cdiffrient@instructure.com> Reviewed-by: Brent Burgoyne <bburgoyne@instructure.com> QA-Review: Tucker Mcknight <tmcknight@instructure.com>
2018-11-30 09:03:38 +08:00
"redux-logger": "^3.0.6",
make feature flags for Right To Left layout Closes: CORE-1154 There are 2 feature flags here. One a specific user (internal employees, sales people, contractors, etc) can turn on to see where we are and what would still need to be done. And the other is for an account to be able to turn on to let the users in their account that have their language set to an RTL language (eg: Arabic, Farsi or Hebrew) see the interface in RTL This commit is part of a chain of commits. you'll need to apply the ones that follow-on after this to see most of the actual Right To Left features, this commit is mainly just to create the feature flag. Test plan: * go to your user settings page * you should see a feature option for Force RTL Layout” * it should show that it is “in development” * it should should be hidden: eg: only appears for site admins and not For normal users * turn it on (if you have this checked out along with the others that follow beind this commit) * navigate around canvas, most things on most pages should be RTL * you should be able to get an idea of how much more work and what Kind of changes we’d still need to make to get it 100% * now turn off that user feature flag, and go to your account's settings * turn on the "allow users from RTL languages to see RTL layout" account-level feature flag. * nothing should change for you, it should be LTR like normal * set your language to either Arabic, Farsi or Hebrew * now the interface should all be in right to left. (again, you'll need to have the follow-on commits to this to see all of the RTL changes) * without either of the feature flags turned on, absolutely nothing should be different at all anywhere in the interface. Change-Id: Ia78d86fa46d2d289b1913c5d1340546d7f6c3a1f Reviewed-on: https://gerrit.instructure.com/143891 Reviewed-by: Brent Burgoyne <bburgoyne@instructure.com> QA-Review: Jeremy Putnam <jeremyp@instructure.com> Product-Review: Ryan Shaw <ryan@instructure.com> Tested-by: Jenkins
2018-03-17 02:25:14 +08:00
"sass-direction": "^1",
[npm dependencies] update all our npm dependencies This is just the regular “update all the things” commit. For things in package.json that we just want the latest version of, I changed them to a simple major with a carat. (Eg: “8^” or “4^”), that way you can see easier which things are specifically locked down To a specific version (or range of versions) for a reason. Test plan: * automated specs & build tasks should work Change-Id: Id7a3f853bd0f7537cc0f08d7dba8d6726b836c44 Reviewed-on: https://gerrit.instructure.com/141653 Tested-by: Jenkins Reviewed-by: Brent Burgoyne <bburgoyne@instructure.com> QA-Review: Brent Burgoyne <bburgoyne@instructure.com> Product-Review: Brent Burgoyne <bburgoyne@instructure.com>
2018-02-23 03:58:38 +08:00
"script-loader": "^0.7",
upgrade to sinon 9.2.4 Change-Id: Ib416d9e907f37f220318444c9a6e74c1a3459bc3 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/337509 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Michael Hulse <michael.hulse@instructure.com> QA-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Product-Review: Aaron Shafovaloff <ashafovaloff@instructure.com>
2024-01-13 02:27:17 +08:00
"sinon": "^9.2.4",
Build prep and cleanup for InstUI 8 Refs FOO-3190 flag=none Trying to uprev InstUI to version 8 revealed that our front-end build config needs a little attention first. Most of this was stuff that's been "wrong" for a while but this major version upgrade of a major dependency really uncovered where some things needed to be tweaked. Test plan: * This only touches build toolchain stuff, so... * If the automated build passes, this should be good Change-Id: I89bd29a581a8c84b7f82d319a0501a4adf59016e Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/318035 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Aaron Shafovaloff <ashafovaloff@instructure.com> QA-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Product-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Build-Review: Aaron Ogata <aogata@instructure.com>
2023-05-12 09:23:16 +08:00
"stream-browserify": "^3",
Add @instructure/uid dependency to canvas test plan: yarn test:karma builds w/o errors Change-Id: I631dabdf9214e2d44bedaa4f4ff1451fcc0e76b0 Reviewed-on: https://gerrit.instructure.com/206016 Reviewed-by: Carl Kibler <ckibler@instructure.com> Reviewed-by: Ryan Shaw <ryan@instructure.com> QA-Review: Carl Kibler <ckibler@instructure.com> QA-Review: Ryan Shaw <ryan@instructure.com> Product-Review: Ryan Shaw <ryan@instructure.com> Tested-by: Jenkins
2019-08-21 22:55:36 +08:00
"style-loader": "^0.23",
upgrade some NPM dependencies Change-Id: If2a90959713e292a46c9d5e9c75c89a37f7316b6 Reviewed-on: https://gerrit.instructure.com/205007 Tested-by: Jenkins Reviewed-by: Cameron Matheson <cameron@instructure.com> QA-Review: Ryan Shaw <ryan@instructure.com> Product-Review: Ryan Shaw <ryan@instructure.com>
2019-08-14 13:36:39 +08:00
"stylelint": "^10",
replace babel with swc in canvas-lms test plan: - build passes - ensure bundles are not much larger - canvas still works in dev environment - smoke test in Safari - smoke test in Firefox closes CFA-38 flag=none [skip-crystalball] Change-Id: I7879b1e7274b9ce47c3aa1985a6a22e5e3659f25 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/337103 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Isaac Moore <isaac.moore@instructure.com> Build-Review: Isaac Moore <isaac.moore@instructure.com> QA-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Product-Review: Aaron Shafovaloff <ashafovaloff@instructure.com>
2024-01-09 12:16:28 +08:00
"terser-webpack-plugin": "5.3.10",
upgrade some NPM dependencies Change-Id: If2a90959713e292a46c9d5e9c75c89a37f7316b6 Reviewed-on: https://gerrit.instructure.com/205007 Tested-by: Jenkins Reviewed-by: Cameron Matheson <cameron@instructure.com> QA-Review: Ryan Shaw <ryan@instructure.com> Product-Review: Ryan Shaw <ryan@instructure.com>
2019-08-14 13:36:39 +08:00
"through2": "^3",
Bump a11y checker version closes MAT-687 flag=none test plan: - Configure user account language to Vietnamese. - Navigate to RCE instance. - Add content with an a11y issue. - Click a11y checker button. > Verify that the a11y tray uses the specified language. Change-Id: Ie8256781a5f1af744f13009912415acb9363442b Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/286851 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Jake Oeding <jake.oeding@instructure.com> QA-Review: Jake Oeding <jake.oeding@instructure.com> Product-Review: Juan Chavez <juan.chavez@instructure.com>
2022-03-11 13:37:19 +08:00
"timezone-mock": "^1.3.1",
Update tinymce and @tinymce/tinymce-react closes LS-1609 flag=rce_enhancements Had to nohiost tinymce so it remains w/in canvas-rce where RCEWrapper.js can require tinymce's stylesheets, but it still needs to be a dev dep. of canvas-lms because there are specs that import tinuymce. Moved the matchMedia jsdon polyfill into jest-setup where it can be used by everyone. Need it there since the new tinymce calls it. test plan: - specs pass - the RCE still works and looks the same Sorry, I don't know what else to say Change-Id: I8c956664176b7c25995a55e0c6fea4dafad3970f Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/255604 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Nate Armstrong <narmstrong@instructure.com> QA-Review: Nate Armstrong <narmstrong@instructure.com> Product-Review: Ed Schiebel <eschiebel@instructure.com>
2020-12-19 01:36:23 +08:00
"tinymce": "^5",
Upgrade TypeScript Test plan: - All existing tests pass flag=none Change-Id: I2a4babd263f9714a15dfbaac7c5cc952069eca94 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/313551 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Isaac Moore <isaac.moore@instructure.com> Reviewed-by: Cameron Ray <cameron.ray@instructure.com> Product-Review: Cameron Ray <cameron.ray@instructure.com> QA-Review: Aaron Shafovaloff <ashafovaloff@instructure.com>
2023-03-17 11:37:19 +08:00
"ts-node": "^10.9.1",
Upgrade TypeScript flag=none Change-Id: I3e9dec807e073f662707f8c1e2e7673d998d52a4 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/333530 Reviewed-by: Gustavo Bernardes <gustavo.bernardes@instructure.com> QA-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Product-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com>
2023-11-22 22:11:39 +08:00
"typescript": "^5.3.2",
upgrade vitest Change-Id: I1d45a2718944ac7de74bc16edbe0b9b44bc5cfc6 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/338208 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Charley Kline <ckline@instructure.com> QA-Review: Charley Kline <ckline@instructure.com> Product-Review: Charley Kline <ckline@instructure.com>
2024-01-21 23:40:07 +08:00
"vitest": "^1.2.1",
Upgrade canvas-planner & rce to not use ui-presets This gets canvas planner and canvas-rce on babel 7, which is a prerequisite to canvas doing the same. Also, by not depending on the Kitchen sink of ui-presets, it cleans a ton of unused stuff from our node_modules/yarn.lock. It was originally 2 different commits but in order to get the yarn.lock right, we have to do them all as one. This also made it so we needed to have less “resolutions” in our package.json since the newer versions of those things work fine with the newer version of babel So there are 2 test plan areas: 1. Canvas-planner Closes: CORE-2575 Test plan: * smoke test to make sure everything in canvas-planner still works/looks like it used to in the canvas ui * make sure the translation task (yarn check-transifex) still works canvas-rce: upgrade to babel 7 & @instructure/ui-babel-preset 2. canvas-rce Closes: CORE-2576 Test plan: * smoke test the RCE editor * theming should still work/look exactly as before * make sure all the various build tasks (eg yarn test, test:coverage, debug, lint, extract, etc) all still work as before Change-Id: Id896687e3905f4df4627b181cad3f67ffe4417a5 Reviewed-on: https://gerrit.instructure.com/183877 Tested-by: Jenkins Reviewed-by: Jon Willesen <jonw+gerrit@instructure.com> Reviewed-by: Steven Burnett <sburnett@instructure.com> QA-Review: Brent Burgoyne <bburgoyne@instructure.com> Product-Review: Ryan Shaw <ryan@instructure.com>
2019-03-06 02:30:44 +08:00
"waait": "^1",
(webpack) upgrade to webpack 5 refs FOO-2835 flag = none there are no behavioral changes, only what was necessary to do the upgrade, see inline comments for explanation where it was warranted Change-Id: I737f31a210365f190ddb606e96e8eb84e2359e0d Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/294133 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Aaron Ogata <aogata@instructure.com> Reviewed-by: Charley Kline <ckline@instructure.com> QA-Review: Aaron Ogata <aogata@instructure.com> Product-Review: Aaron Ogata <aogata@instructure.com>
2022-06-17 13:54:48 +08:00
"webpack": "^5",
"webpack-bundle-analyzer": "^4.5.0",
Update webpack-cli for webpack:analyze bugfix Fixes FOO-1674 flag = none Update webpack-cli dependency to pull in a bugfix which was preventing the webpack:analyze tool from working. Test plan: * yarn webpack:analyze works again * nothing else broke (major version number changed!) Change-Id: I5f6ee48ea7b24bda9e13e73f44cee8cf23abfc22 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/260189 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Jeff Largent <jeff.largent@instructure.com> QA-Review: Jeff Largent <jeff.largent@instructure.com> Product-Review: Charley Kline <ckline@instructure.com>
2021-03-09 03:33:46 +08:00
"webpack-cli": "^4",
(webpack) upgrade esmac plugin refs FOO-2835 flag = none there's no need for the custom IgnoreErrors plugin anymore since the esmac plugin now has an option for bypassing specific violations ~ test plan ~ webpack build still reports on access control violations Change-Id: I684ce4754f6afbf478daf27c3f6d1b9c4dfc161a Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/294369 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Charley Kline <ckline@instructure.com> QA-Review: Charley Kline <ckline@instructure.com> Product-Review: Charley Kline <ckline@instructure.com>
2022-06-21 20:07:32 +08:00
"webpack-esmac-plugin": "^4.0.0",
(webpack) upgrade to webpack 5 refs FOO-2835 flag = none there are no behavioral changes, only what was necessary to do the upgrade, see inline comments for explanation where it was warranted Change-Id: I737f31a210365f190ddb606e96e8eb84e2359e0d Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/294133 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Aaron Ogata <aogata@instructure.com> Reviewed-by: Charley Kline <ckline@instructure.com> QA-Review: Aaron Ogata <aogata@instructure.com> Product-Review: Aaron Ogata <aogata@instructure.com>
2022-06-17 13:54:48 +08:00
"webpack-manifest-plugin": "^5",
catch and report on rogue imports fixes FOO-2422 this patch codifies the access rules between modules in the new UI file structure: packages/ can be accessed by everyone ui/shared/ can only be accessed by Canvas packages and features ui/features/ can only be accessed by boot ui/boot/ can only be accessed by entrypoint ui/index.js can only be accessed by Rails additionally, the specifiers used for importing may no longer be arbitrary; generally, every enapsulated folder must use relative specifiers for intra-imports, and bare specifiers for inter-imports ui/features/a/a.js => ui/features/a/b.js [via] ./b.js ui/features/a/a.js => ui/shared/a/a.js [via] @canvas/a/a ui/features/a/a.js => packages/a/a.js [via] a/a the rules are defined in the webpack config file, there are currently 37 violations that we have to address, for now I added a plugin to ignore them (see frontend_build/existingEncapsulationErrors.json) violations are reported with a detailed description of what exactly caused the violation, what is being violated, along with a suggestion on how to address it - see https://github.com/instructure/esmac for the tool that applies the rules - see https://github.com/instructure/webpack-encapsulation-plugin for the webpack implementation of that tool ~ test plan ~ ~~~^ ^~~~ \m/ edit frontend_build/existingEncapsulationErrors.json and remove entries from there, or alternatively just disable the IgnoreErrors plugin to get all the errors displayed, then rerun webpack against the offending source file to view the error report - for example: npx webpack --entry=$PWD/packages/backbone-identity-map/index.js # or, if u chose to disable the plugin npx webpack the messages should be clear and helpful; there are currently 4 scenarios for access violation, and 4 scenarios for specifier mismatche Change-Id: Ibae4245122e2c015ccbd47d73ac8689e0a386d86 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/275200 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Charley Kline <ckline@instructure.com> QA-Review: Charley Kline <ckline@instructure.com> Product-Review: Charley Kline <ckline@instructure.com>
2021-10-02 07:28:20 +08:00
"wrap-ansi": "^7.0.0",
upgrade some NPM dependencies Change-Id: If2a90959713e292a46c9d5e9c75c89a37f7316b6 Reviewed-on: https://gerrit.instructure.com/205007 Tested-by: Jenkins Reviewed-by: Cameron Matheson <cameron@instructure.com> QA-Review: Ryan Shaw <ryan@instructure.com> Product-Review: Ryan Shaw <ryan@instructure.com>
2019-08-14 13:36:39 +08:00
"wsrun": "^5",
Point to instructure forks Closes: CCI-351 flag = none Test Plan: - no behavioral changes - build passes Change-Id: I2e6bfa46b56ee2b59b8289fc90ef9c319757fc34 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/235566 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: James Butters <jbutters@instructure.com> Reviewed-by: Jacob Powell <spowell@instructure.com> QA-Review: James Butters <jbutters@instructure.com> QA-Review: Jacob Powell <spowell@instructure.com> Product-Review: James Butters <jbutters@instructure.com>
2020-04-29 05:19:29 +08:00
"xsslint": "instructure/xsslint#babel7",
Bump a11y checker version closes MAT-687 flag=none test plan: - Configure user account language to Vietnamese. - Navigate to RCE instance. - Add content with an a11y issue. - Click a11y checker button. > Verify that the a11y tray uses the specified language. Change-Id: Ie8256781a5f1af744f13009912415acb9363442b Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/286851 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Jake Oeding <jake.oeding@instructure.com> QA-Review: Jake Oeding <jake.oeding@instructure.com> Product-Review: Juan Chavez <juan.chavez@instructure.com>
2022-03-11 13:37:19 +08:00
"yaml-loader": "^0.5"
clean up JS tests and integrate karma - js:generate_runner now generates common files to be used by different test runners - js spec file order now shuffled to better expose dependencies - fakeENV now returns two methods: setup and teardown - stock tinymce 3 files are now wrapped for AMD test plan: - tinymce should work the same - js:test rake task should run tests - js:build task should work as normal (using new location of r.js) - test results should successfully send to firework Change-Id: Ic09647f55dae57130fa0fe3d6a9168d2b67b89a2 Reviewed-on: https://gerrit.instructure.com/29297 QA-Review: Shawn Meredith <shawn@instructure.com> Tested-by: Shawn Meredith <shawn@instructure.com> Tested-by: Aaron Shafovaloff <ashafovaloff@instructure.com> Reviewed-by: Aaron Shafovaloff <ashafovaloff@instructure.com> Product-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> QA-Review: Aaron Shafovaloff <ashafovaloff@instructure.com>
2014-01-24 23:58:37 +08:00
},
make inspect-process an optional dependency Change-Id: If62f0601df401e2407a0a606a75c230d1225b205 Reviewed-on: https://gerrit.instructure.com/183822 Reviewed-by: Simon Williams <simon@instructure.com> QA-Review: Simon Williams <simon@instructure.com> Tested-by: Jenkins Product-Review: Brent Burgoyne <bburgoyne@instructure.com>
2019-03-05 23:51:37 +08:00
"optionalDependencies": {
bump babel to latest v7.x refs DE-1274 Change-Id: I2b3a678761a03b71b97659ec585b3023223329e6 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/296262 Reviewed-by: Andrea Cirulli <andrea.cirulli@instructure.com> QA-Review: Aaron Ogata <aogata@instructure.com> Product-Review: Aaron Ogata <aogata@instructure.com> Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com>
2022-07-16 01:11:46 +08:00
"@storybook/addon-actions": "^6.5.9",
"@storybook/addon-essentials": "^6.5.9",
"@storybook/addon-links": "^6.5.9",
"@storybook/addon-storyshots": "^6.5.9",
move webpack 5 storybook packages to optionalDependencies Change-Id: I496e4e6be461d29c38406d57c9f97311831fc40b Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/298113 QA-Review: Aaron Ogata <aogata@instructure.com> Product-Review: Aaron Ogata <aogata@instructure.com> Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Alex Slaughter <aslaughter@instructure.com>
2022-08-09 10:44:30 +08:00
"@storybook/builder-webpack5": "^6.5.9",
"@storybook/manager-webpack5": "^6.5.9",
Resolve final circular package dependencies Refs CFA-27 flag=none Change-Id: I9787633a7deef3206f1462e8f65936dc51f1af3d Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/335951 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Michael Hulse <michael.hulse@instructure.com> QA-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Product-Review: Aaron Shafovaloff <ashafovaloff@instructure.com>
2023-12-25 02:29:29 +08:00
"@storybook/react": "^6.5.9"
make inspect-process an optional dependency Change-Id: If62f0601df401e2407a0a606a75c230d1225b205 Reviewed-on: https://gerrit.instructure.com/183822 Reviewed-by: Simon Williams <simon@instructure.com> QA-Review: Simon Williams <simon@instructure.com> Tested-by: Jenkins Product-Review: Brent Burgoyne <bburgoyne@instructure.com>
2019-03-05 23:51:37 +08:00
},
return focus to the status bar buttons when the kb shortcut dialog or the a11y checker tray close, return focus to the button that opened it. closes COREFE-108 test plan: - in rce, click on the kb short cutton in the status bar - close the kb shortcut dialog > expect focus to return to the button - repeat for the a11y checker - tab until the show-on-focus kb shortcut button above the RCE appears, click it, then close the dialog > expect focus to return to the button Change-Id: I27ea79930e643d9908a784fbcb89900918d3be01 Reviewed-on: https://gerrit.instructure.com/204283 Tested-by: Jenkins Reviewed-by: Clay Diffrient <cdiffrient@instructure.com> QA-Review: Clay Diffrient <cdiffrient@instructure.com> Product-Review: Ed Schiebel <eschiebel@instructure.com>
2019-08-08 04:19:35 +08:00
"browserslist": [
"extends @instructure/browserslist-config-canvas-lms"
],
upgrade karma everyone was getting build errors when they were npm install'ing. it was because karma 0.10 depended on an out-of-date version of chokiadr that does not compile against node 0.12 I also indicated that canvas is licenced agpl 3 so that you wouldn't always see an npm warning about not having one. also, let karma serve our css files so if any javascript references them in our quit tests, we don't see 404 warnings Change-Id: Iaa0377bc87b8f7ec8726d6cb82c0f8a103134b56 Reviewed-on: https://gerrit.instructure.com/58584 Tested-by: Jenkins Reviewed-by: Mike Nomitch <mnomitch@instructure.com> Reviewed-by: Clay Diffrient <cdiffrient@instructure.com> Product-Review: Ryan Shaw <ryan@instructure.com> QA-Review: Ryan Shaw <ryan@instructure.com>
2015-07-16 12:24:49 +08:00
"repository": "instructure/canvas-lms",
clean up JS tests and integrate karma - js:generate_runner now generates common files to be used by different test runners - js spec file order now shuffled to better expose dependencies - fakeENV now returns two methods: setup and teardown - stock tinymce 3 files are now wrapped for AMD test plan: - tinymce should work the same - js:test rake task should run tests - js:build task should work as normal (using new location of r.js) - test results should successfully send to firework Change-Id: Ic09647f55dae57130fa0fe3d6a9168d2b67b89a2 Reviewed-on: https://gerrit.instructure.com/29297 QA-Review: Shawn Meredith <shawn@instructure.com> Tested-by: Shawn Meredith <shawn@instructure.com> Tested-by: Aaron Shafovaloff <ashafovaloff@instructure.com> Reviewed-by: Aaron Shafovaloff <ashafovaloff@instructure.com> Product-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> QA-Review: Aaron Shafovaloff <ashafovaloff@instructure.com>
2014-01-24 23:58:37 +08:00
"scripts": {
fix JS job sanity around COVERAGE var refs DE-462 Change-Id: Ie5bce0bdf0e7a16eb9424813abd49000d5d819d2 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/257532 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Kyle Rosenbaum <krosenbaum@instructure.com> QA-Review: Aaron Ogata <aogata@instructure.com> Product-Review: Aaron Ogata <aogata@instructure.com>
2021-01-27 23:25:50 +08:00
"test": "yarn test:packages && if [ \"$COVERAGE\" = \"1\" ]; then yarn test:jest:coverage --runInBand; else yarn test:jest --runInBand; fi && if [ \"$COVERAGE\" = \"1\" ]; then yarn test:karma; else yarn test:karma:concurrently; fi",
Add a way to generate better js coverage This should pick up coverage from both karma and jest in Canvas proper. It should also pick up coverage from anything under packages/* closes CORE-1265 Test Plan: - Run `COVERAGE=true yarn test` - Coverage reports (coverage-final.json) should generate in all packages such as (canvas-planner) as well as in coverage-karma and coverage-jest - Run `yarn run test:coverage` - coverage-js folder should be generated. Opening index.html should show the full coverage report - Remove coverage-{js, karma, jest} and packages/canvas-planner/coverage as well as .nyc_output to get back to a clean state - Run `RUN_TESTS_FIRST=true yarn run test:coverage` - All tests should run and generate the appropriate report just like the last time in coverage-js Change-Id: I50744b8977e0683e079af5bdd2865dbcd6ad9066 Reviewed-on: https://gerrit.instructure.com/146098 Tested-by: Jenkins Reviewed-by: Ryan Shaw <ryan@instructure.com> QA-Review: Jeremy Putnam <jeremyp@instructure.com> Product-Review: Clay Diffrient <cdiffrient@instructure.com>
2018-04-06 05:27:42 +08:00
"test:coverage": "script/generate_js_coverage",
speed up JS tests by running them concurrently closes: CORE-865 In order to get accurate coverage reports (ie: so the coverage numbers don’t only reflect a fraction of the total tests), when the COVERAGE environment variable is set, it does not split them out into groups to run concurrently. That way our linters-and-js-master build (which sets that environment variable) will run the same as it always has and our patch-set builds (which run the linters-and-js) will be faster. Test plan: * run ‘yarn test’ * it should be a lot faster than it used to be * look at the linters-and-js build in jenkins for this commit * it should have test reports for all both groups (coffee, js) Of karma tests as well as for the jest tests. * look at the coverage report after this gets merged. It should be the same as it was before Change-Id: I35147cc84df4afae92c1a73c201667d4d44b5518 Reviewed-on: https://gerrit.instructure.com/136373 Reviewed-by: Simon Williams <simon@instructure.com> Reviewed-by: Clay Diffrient <cdiffrient@instructure.com> Reviewed-by: Jeremy Neander <jneander@instructure.com> Tested-by: Jenkins Product-Review: Ryan Shaw <ryan@instructure.com> QA-Review: Ryan Shaw <ryan@instructure.com>
2017-12-22 04:09:17 +08:00
"test:watch": "concurrently --names \"jest,karma\" \"jest --watch .\" \"yarn test:karma:watch\"",
Install Vitest This does not yet change our build process Demo: - yarn run test:vitest:watch ui/features/theme_editor/ Test plan: - build passes Closes CFA-17 flag=none Change-Id: I6eac4684af62525829e36f5dd0c64bb80c638ca3 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/333130 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Martin Ochoa <martin.ochoa@instructure.com> Reviewed-by: Gustavo Bernardes <gustavo.bernardes@instructure.com> QA-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Product-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Build-Review: Andrea Cirulli <andrea.cirulli@instructure.com>
2023-11-17 20:54:42 +08:00
"test:vitest": "vitest run --color",
"test:vitest:watch": "vitest watch --color",
"test:vitest:coverage": "vitest run --color --coverage",
run jest tests concurrently closes USERS-376 fixes USERS-379 fixes USERS-385 test plan: - specs pass Change-Id: I30d4c27a2c628858a207d4c0236345bad49b7bcf Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/228278 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Charley Kline <ckline@instructure.com> QA-Review: Charley Kline <ckline@instructure.com> Product-Review: Charley Kline <ckline@instructure.com>
2020-02-28 05:49:45 +08:00
"test:jest": "jest --color",
Remove SSL legacy flag flag=none Test plan - Specs pass - Rebuild Javascript assets and ensure you can view stuff - Ensure yarn test:jest:coverage starts Change-Id: Icb407270cb83882ae895190e3b39b2488e56e6ba Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/343539 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Eric Saupe <eric.saupe@instructure.com> QA-Review: Eric Saupe <eric.saupe@instructure.com> Build-Review: Aaron Ogata <aogata@instructure.com> Product-Review: Mysti Lilla <mysti@instructure.com>
2024-03-23 05:45:12 +08:00
"test:jest:coverage": "NODE_OPTIONS=\"--max_old_space_size=5120\" jest --color --coverage --testTimeout=5000",
fix audio player and video player sizing closes LA-729 flag=rce_enhancements The original intent for the audio player was to size it so the buttons just fit. This ignored the fact that it's rendered w/in an iframe, so popup menus are clipped. This change sizes the player to leave room for those popups. While the ticket was written against the audio player, the same issues may occur in the video player, either for portrait videos or videos < 400px wide when closed captions are present. The original code for sizing the video player shrank the width to fit thea video's size, which clipped the buttons. This change sets a minimum width for the player and letter-boxes the video. test plan: - in the new rce - add an audio file > expect it to be wide enough to show all the buttons and tall enough for the speed and volume popups - add a vertical video > expect the video sized to fit in the available space in the Computer tab of the Upload Media modal - Submit to upload > expect the player to be wide enough to show all the buttons - click the fullscreen button > expect the video to be the height of the screen and letterboxed - restore to windowed size > expect the video to return to its letterboxed size - click the video, then the Options button - change the video's size > expect the video to remain letterboxed - add a horizontal video > expect the video sized to fit in the available space in the Computer tab of the Upload Media modal - submit to upload > expect the player to be sized to the size of the video - fullscreen > expect the video to be letterboxed in the fullscreen player (if the aspect ration of the video !== that of your monitor, or fill the screen if they match) - for the horizontal video, select Opitons and change the size to be "medium" or "custom" and < 400px wide and add subtitles > expect the video to be letterboxed in a 400px wide iframe. Change-Id: Ib5d08dbd7796985d00f656e38a642ab92939d614 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/238432 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Alex Anderson <raanderson@instructure.com> QA-Review: Robin Kuss <rkuss@instructure.com> Product-Review: Ed Schiebel <eschiebel@instructure.com>
2020-05-26 23:37:35 +08:00
"test:jest:debug": "node --inspect-brk node_modules/.bin/jest --runInBand",
update JS testing docs flag=none this commit also removes the phantomjs docker-compose service which has been broken for years, ever since PhantomJS was removed from karma.conf.js in https://gerrit.instructure.com/c/canvas-lms/+/102169 test plan: - follow the docs to ensure you can run a targeted JS test in docker Change-Id: Ifa1647897a7a9605e097aeaf89e718c167d379fc Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/256179 Reviewed-by: Nate Armstrong <narmstrong@instructure.com> QA-Review: Nate Armstrong <narmstrong@instructure.com> Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Product-Review: Michael Ziwisky <mziwisky@instructure.com>
2021-01-06 16:57:21 +08:00
"test:jest:watch": "jest --color --watch",
use native jest test sequencer for test sharding refs DE-1287 [canvas-builds-refspec=6bbd69725d207fb32daeab11b834d6a2b35ac84c] Change-Id: I73eda09fc9cab01ed87b8487258992f161a6310f Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/296633 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Andrea Cirulli <andrea.cirulli@instructure.com> QA-Review: Aaron Ogata <aogata@instructure.com> Product-Review: Aaron Ogata <aogata@instructure.com>
2022-07-20 23:24:03 +08:00
"test:jest:build": "if [ \"$COVERAGE\" = \"1\" ]; then yarn test:jest:coverage --maxWorkers=3 --shard=$CI_NODE_INDEX/$CI_NODE_TOTAL; else yarn test:jest --maxWorkers=3 --shard=$CI_NODE_INDEX/$CI_NODE_TOTAL; fi",
Give more memory to karma when it's running This should make it so our post-merge build starts working again and reporting new coverage information. closes CORE-1435 Test Plan: - Run `COVERAGE=true yarn run test:karma` - It should not fail because of memory issues Change-Id: I6e103352fa25e130d0ba8072a77c9d81ac11bb85 Reviewed-on: https://gerrit.instructure.com/150666 Tested-by: Jenkins Reviewed-by: Ryan Shaw <ryan@instructure.com> Product-Review: Clay Diffrient <cdiffrient@instructure.com> QA-Review: Clay Diffrient <cdiffrient@instructure.com>
2018-05-18 06:02:10 +08:00
"test:karma": "yarn run test:karma:watch --single-run",
Add linters to new Jenkins This moves eslint, stylelint, and xsslint to be part of our JS build pipeline. It does not account for other linters that are more general like tatl_tael linters and commit messages or non-frontend language specific linters like rubocop. Test Plan: - The linters-and-js build on New Jenkins should run and actually run the linters specified above. closes COREFE-220 flag = none Change-Id: I8f633caf9af025c83bbe68fbd1536276a838c159 Reviewed-on: https://gerrit.instructure.com/206106 Tested-by: Jenkins Reviewed-by: Ed Schiebel <eschiebel@instructure.com> Reviewed-by: Ryan Shaw <ryan@instructure.com> QA-Review: Ryan Shaw <ryan@instructure.com> Product-Review: Ryan Shaw <ryan@instructure.com>
2019-08-22 03:12:19 +08:00
"test:karma:concurrently": "concurrently --names \"coffee,jsa,jsg,jsh\" \"JSPEC_GROUP=coffee yarn test:karma:headless\" \"JSPEC_GROUP=jsa yarn test:karma:headless\" \"JSPEC_GROUP=jsg yarn test:karma:headless\" \"JSPEC_GROUP=jsh yarn test:karma:headless\"",
use selenium grid for karma tests refs DE-1334 Change-Id: I61e78a60498b9fd64ea9d5333504c4db10c8c03f Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/298285 Reviewed-by: Andrea Cirulli <andrea.cirulli@instructure.com> Build-Review: Andrea Cirulli <andrea.cirulli@instructure.com> Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> QA-Review: Aaron Ogata <aogata@instructure.com> Product-Review: Aaron Ogata <aogata@instructure.com>
2022-08-11 02:15:25 +08:00
"test:karma:headless": "yarn run test:karma --browsers ${KARMA_BROWSER:-ChromeHeadlessNoSandbox}",
Give more memory to karma when it's running This should make it so our post-merge build starts working again and reporting new coverage information. closes CORE-1435 Test Plan: - Run `COVERAGE=true yarn run test:karma` - It should not fail because of memory issues Change-Id: I6e103352fa25e130d0ba8072a77c9d81ac11bb85 Reviewed-on: https://gerrit.instructure.com/150666 Tested-by: Jenkins Reviewed-by: Ryan Shaw <ryan@instructure.com> Product-Review: Clay Diffrient <cdiffrient@instructure.com> QA-Review: Clay Diffrient <cdiffrient@instructure.com>
2018-05-18 06:02:10 +08:00
"test:karma:watch": "node --max-old-space-size=4096 ./node_modules/.bin/karma start",
use selenium grid for karma tests refs DE-1334 Change-Id: I61e78a60498b9fd64ea9d5333504c4db10c8c03f Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/298285 Reviewed-by: Andrea Cirulli <andrea.cirulli@instructure.com> Build-Review: Andrea Cirulli <andrea.cirulli@instructure.com> Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> QA-Review: Aaron Ogata <aogata@instructure.com> Product-Review: Aaron Ogata <aogata@instructure.com>
2022-08-11 02:15:25 +08:00
"test:karma:watch:headless": "yarn run test:karma:watch --browsers ${KARMA_BROWSER:-ChromeHeadlessNoSandbox}",
fix JS job sanity around COVERAGE var refs DE-462 Change-Id: Ie5bce0bdf0e7a16eb9424813abd49000d5d819d2 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/257532 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Kyle Rosenbaum <krosenbaum@instructure.com> QA-Review: Aaron Ogata <aogata@instructure.com> Product-Review: Aaron Ogata <aogata@instructure.com>
2021-01-27 23:25:50 +08:00
"test:packages": "if [ \"$COVERAGE\" = \"1\" ]; then yarn workspace-run-serial test:coverage; else yarn workspace-run-serial test; fi",
run canvas-rce tests in parallel refs DE-1207 Change-Id: Ib749db529d6a477663f89cd0c4482bbc93a51ae7 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/293098 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Isaac Moore <isaac.moore@instructure.com> QA-Review: Aaron Ogata <aogata@instructure.com> Product-Review: Aaron Ogata <aogata@instructure.com>
2022-06-02 22:22:55 +08:00
"test:packages:parallel": "if [ \"$COVERAGE\" = \"1\" ]; then yarn workspace-run test:coverage; else yarn workspace-run test; fi",
make npm build scripts more user friendly :) test plan: - run the following commands and assess that they run as expected: - yarn run build - yarn run build:css - yarn run build:css:watch - yarn run build:js - yarn run build:jss:watch Change-Id: I4c0a2a68ce62896364bc2da5e7956002c15f5847 Reviewed-on: https://gerrit.instructure.com/110497 Reviewed-by: Clay Diffrient <cdiffrient@instructure.com> Tested-by: Jenkins Reviewed-by: Ryan Shaw <ryan@instructure.com> QA-Review: Steven Burnett <sburnett@instructure.com> Product-Review: Felix Milea-Ciobanu <fmileaciobanu@instructure.com>
2017-05-03 00:44:54 +08:00
"build": "yarn run build:css && yarn run build:js",
upgrade some NPM dependencies Change-Id: If2a90959713e292a46c9d5e9c75c89a37f7316b6 Reviewed-on: https://gerrit.instructure.com/205007 Tested-by: Jenkins Reviewed-by: Cameron Matheson <cameron@instructure.com> QA-Review: Ryan Shaw <ryan@instructure.com> Product-Review: Ryan Shaw <ryan@instructure.com>
2019-08-14 13:36:39 +08:00
"build:watch": "concurrently --raw \"yarn build:css:watch\" \"yarn build:js:watch\"",
make npm build scripts more user friendly :) test plan: - run the following commands and assess that they run as expected: - yarn run build - yarn run build:css - yarn run build:css:watch - yarn run build:js - yarn run build:jss:watch Change-Id: I4c0a2a68ce62896364bc2da5e7956002c15f5847 Reviewed-on: https://gerrit.instructure.com/110497 Reviewed-by: Clay Diffrient <cdiffrient@instructure.com> Tested-by: Jenkins Reviewed-by: Ryan Shaw <ryan@instructure.com> QA-Review: Steven Burnett <sburnett@instructure.com> Product-Review: Felix Milea-Ciobanu <fmileaciobanu@instructure.com>
2017-05-03 00:44:54 +08:00
"build:css": "brandable_css",
Harvard RCE tweaks - not directly related to the RCE, but now preload the 3 lato-exended font variants likely to be used on the page. this keeps font loading from blocking - the big change is to make it possible to limit the number of RCEs that will fully render on page load. This should address the loading issues for quizzes with many essay questions (the sample quiz from Harvard had 30 + other questions) For now, the necessary property is only being set on the take-quiz page closes: MAT-355 flag=rce_enhancements,flag=rce_limit_init_render_on_page test plan: account flag. - create a legacy quiz with > 5 essay questions. Feel free to have other questions in there too if you like - preview or take the quiz > expect all 6 RCEs to be created on the page - you could use React dev tools or document.querySelectorAll('.rce-wrapper').length === 6 - turn the "RCE Limit number of RCEs initially rendered on th page" account feature flag on - take the quiz again > expect only the first 5 RCEs to be fully rendered - scroll down to the bring the 6th into view > expect it to be fully realized - while scrolled to the bottom, refresh the page > not that the 6th RCE is in view, expect it to be fully realized also Change-Id: Idd76a56c4ea69e45a4f1cc28e3cd8561b40c2403 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/270075 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> QA-Review: Weston Dransfield <wdransfield@instructure.com> Reviewed-by: Jon Scheiding <jon.scheiding@instructure.com> Product-Review: Ed Schiebel <eschiebel@instructure.com>
2021-07-27 23:13:08 +08:00
"build:css:compressed": "SASS_STYLE=compressed brandable_css",
make npm build scripts more user friendly :) test plan: - run the following commands and assess that they run as expected: - yarn run build - yarn run build:css - yarn run build:css:watch - yarn run build:js - yarn run build:jss:watch Change-Id: I4c0a2a68ce62896364bc2da5e7956002c15f5847 Reviewed-on: https://gerrit.instructure.com/110497 Reviewed-by: Clay Diffrient <cdiffrient@instructure.com> Tested-by: Jenkins Reviewed-by: Ryan Shaw <ryan@instructure.com> QA-Review: Steven Burnett <sburnett@instructure.com> Product-Review: Felix Milea-Ciobanu <fmileaciobanu@instructure.com>
2017-05-03 00:44:54 +08:00
"build:css:watch": "brandable_css --watch",
"build:js": "yarn run webpack-development",
"build:js:watch": "yarn run webpack",
move packages into dependencies layer for caching refs DE-216 [change-merged] [build-registry-path=jenkins/canvas-lms/de-216] Test Plan: 1. Ensure that docker-compose build works locally 2. Ensure that packages building is cached when files aren’t changed 3. Packages build correctly when modified Change-Id: I3e775e5d7eb51ba06078314b50bf2f8efb6d7d0b Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/245423 Reviewed-by: James Butters <jbutters@instructure.com> Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> QA-Review: Aaron Ogata <aogata@instructure.com> Product-Review: Aaron Ogata <aogata@instructure.com>
2020-08-19 05:43:49 +08:00
"build:packages": "yarn workspace-run build:canvas",
Initial pace plans import This change brings in the basic pace plans frontend with styled-components and several other smaller libraries replaced with InstUI 7 components. It also adds the 'reselect' library as a direct dependency (which we already had through @instructure/outcomes-ui) and 'tsc-files' for type-checking of staged TS files on commit. There were also some tweaks to typescript and eslint configs, mostly to get both up to speed with the typescript code. Finally, this also adds a `pace_plans` endpoint to `courses_controller` to bootstrap the frontend-- this will get moved to `pace_plans_controller` once it has been merged. It's also worth noting that no frontend tests are included with this change-- the existing tests were written with enzyme and are heavily snapshot-based, so we will be replacing those with @testing-library/react tests in later updates (in keeping with current testing best practices at Instructure). closes LS-2431, LS-2432, LS-2433, LS-2434, LS-2452 flag = pace_plans Test plan: - Set up a course with at least one module and several module items - Turn on the pace_plans feature flag in the account associated with that course - Turn on the "Enable pace plans" setting in course settings - Create a pace plan for the course via the Rails console: c = Course.find<id> pp = c.pace_plans.create! workflow_state: 'active' c.context_module_tags.each_with_index do |t, i| pp.pace_plan_module_items.create! module_item: t, duration: i*2 end - Go to the course as a teacher or admin - Expect to see a "Pace Plans" link in the course navigation - Click it, expect the pace plan you created earlier to load and render - Expect to be able to pick dates, change durations, and toggle checkboxes (although saves will fail, since there is no API yet). - Expect to not see the "Pace Plans" course nav link when the feature flag or course setting is off - Expect /courses/<id>/pace_plans to return a 404 when the feature flag or course setting is off - Expect to not see the "Pace Plans" course nav link as a student - Expect /courses/<id>/pace_plans to display an "Unauthorized" page as a student Change-Id: If4dc5d17f2c6a2109d4b4cb652c9e9ef00d7cc33 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/271650 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Ed Schiebel <eschiebel@instructure.com> QA-Review: Ed Schiebel <eschiebel@instructure.com> Product-Review: Jeff Largent <jeff.largent@instructure.com>
2021-08-18 05:14:24 +08:00
"check:js": "tsc --checkJs -p tsconfig.json",
turn on noImplicitAny for typescript also: remove tsconfig-strict.json also: remove tsc precommit hook test plan: - existing tests pass flag=none Change-Id: Ia2b30d9d77fdb55159de4fe16f3ee1826f43aad5 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/317197 Reviewed-by: Yona Appletree <yona.appletree@instructure.com> Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> QA-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Product-Review: Aaron Shafovaloff <ashafovaloff@instructure.com>
2023-04-28 05:13:41 +08:00
"check:ts": "tsc -p tsconfig.json",
"check:ts:watch": "tsc --watch -p tsconfig.json",
simplify lint scripts in package.json flag=none Change-Id: Ia1c376996a6f8f82ca7db53c93ec38d69cfdab3d Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/336860 Reviewed-by: Michael Hulse <michael.hulse@instructure.com> Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> QA-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Product-Review: Aaron Shafovaloff <ashafovaloff@instructure.com>
2024-01-06 08:56:41 +08:00
"lint:packages": "eslint packages --cache --ext '.js,.jsx,.ts,.tsx'",
fix pre-commit hook with unfixable eslint error test plan: - have a local yarn install - add an unfixable lint error (unused var) to a file in the prettier whitelist - try to commit the file - it should not try to run in docker after the lint error Change-Id: If1fcfc6693be26c6f6fdddb8cfa4c54a73512ebe Reviewed-on: https://gerrit.instructure.com/173469 Reviewed-by: Clay Diffrient <cdiffrient@instructure.com> QA-Review: Clay Diffrient <cdiffrient@instructure.com> Product-Review: Clay Diffrient <cdiffrient@instructure.com> Tested-by: Jenkins
2018-11-28 06:40:21 +08:00
"lint:staged": "lint-staged",
simplify lint scripts in package.json flag=none Change-Id: Ia1c376996a6f8f82ca7db53c93ec38d69cfdab3d Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/336860 Reviewed-by: Michael Hulse <michael.hulse@instructure.com> Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> QA-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Product-Review: Aaron Shafovaloff <ashafovaloff@instructure.com>
2024-01-06 08:56:41 +08:00
"lint:style": "stylelint './app/**/*.{css,scss}' './packages/**/*.{css,scss}'",
Add linters to new Jenkins This moves eslint, stylelint, and xsslint to be part of our JS build pipeline. It does not account for other linters that are more general like tatl_tael linters and commit messages or non-frontend language specific linters like rubocop. Test Plan: - The linters-and-js build on New Jenkins should run and actually run the linters specified above. closes COREFE-220 flag = none Change-Id: I8f633caf9af025c83bbe68fbd1536276a838c159 Reviewed-on: https://gerrit.instructure.com/206106 Tested-by: Jenkins Reviewed-by: Ed Schiebel <eschiebel@instructure.com> Reviewed-by: Ryan Shaw <ryan@instructure.com> QA-Review: Ryan Shaw <ryan@instructure.com> Product-Review: Ryan Shaw <ryan@instructure.com>
2019-08-22 03:12:19 +08:00
"lint:xss": "node ./script/xsslint.js",
simplify lint scripts in package.json flag=none Change-Id: Ia1c376996a6f8f82ca7db53c93ec38d69cfdab3d Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/336860 Reviewed-by: Michael Hulse <michael.hulse@instructure.com> Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> QA-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Product-Review: Aaron Shafovaloff <ashafovaloff@instructure.com>
2024-01-06 08:56:41 +08:00
"lint": "eslint ui --cache --ext '.js,.jsx,.ts,.tsx'",
patch format-message to fix CJS issue Change-Id: Id955360efbd116835f51fe48c53ff8cf221f956c Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/338375 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Michael Hulse <michael.hulse@instructure.com> QA-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Product-Review: Aaron Shafovaloff <ashafovaloff@instructure.com>
2024-01-23 07:00:30 +08:00
"postinstall": "yarn dedupe-yarn; patch-package; test -n \"$DISABLE_POSTINSTALL\" || (yarn build:packages && ./script/install_hooks)",
replace webpack with rspack test plan: - run rspack locally (as "webpack" for now) - ensure coverage data for crystalball - ensure build passes with skip-crystalball - ensure source maps for local dev - ensure bundle analysis is available and documented - ensure compile times are at least comparable refs CFA-32 [skip-crystalball] flag=none Change-Id: I8ad916ac7fbe9e3ecee5c690abcd78cdde748ab6 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/339401 Reviewed-by: Isaac Moore <isaac.moore@instructure.com> Build-Review: Isaac Moore <isaac.moore@instructure.com> Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> QA-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Product-Review: Aaron Shafovaloff <ashafovaloff@instructure.com>
2024-02-01 04:19:23 +08:00
"webpack:analyze": "SKIP_SOURCEMAPS=1 WEBPACK_PEDANTIC=0 rspack --analyze",
"webpack": "gulp rev 1> /dev/null & NODE_ENV=development rspack --watch=true",
"webpack-development": "NODE_ENV=development rspack build",
"webpack-production": "NODE_ENV=production rspack build",
don't swallow stderr during build:packages flag = none stderr output of the individual processes fed to "wsrun" are being swallowed if it's running in --parallel and asked to --collect-logs see: https://github.com/hfour/wsrun/issues/107 see: https://github.com/hfour/wsrun/issues/92 == test plan grab the following image from starlord and verify you see the actual error output from the canvas-rce package: export IMAGE="starlord.inscloudgate.net/jenkins/canvas-lms:63.262363.4-postgres-12-ruby-2.6-failed" && docker pull "$IMAGE" && docker run \ -v "$PWD"/package.json:/usr/src/app/package.json:ro \ --rm -it \ "$IMAGE" \ yarn build:packages Change-Id: I7650e6b9b83bb22faea569eba05a9f73f5e72b4f Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/262410 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Aaron Ogata <aogata@instructure.com> QA-Review: Ahmad Amireh <ahmad@instructure.com> Product-Review: Ahmad Amireh <ahmad@instructure.com>
2021-04-07 23:59:07 +08:00
"workspace-run": "r() { wsrun --fast-exit --exclude-missing --report -c $@; exit $?; } && r",
Bump wsrun to the latest version Test Plan: - All workspaces run their tests on jenkins Change-Id: I66fa941a11cdd6306a27b5a374af88755d593472 Reviewed-on: https://gerrit.instructure.com/188718 Tested-by: Jenkins Reviewed-by: Brent Burgoyne <bburgoyne@instructure.com> QA-Review: Brent Burgoyne <bburgoyne@instructure.com> Product-Review: Brent Burgoyne <bburgoyne@instructure.com>
2019-04-09 02:36:08 +08:00
"workspace-run-serial": "r() { wsrun --fast-exit --exclude-missing --collect-logs --report --serial -c $@; exit $?; } && r",
add npm script that can run specific js specs example usage: `npm run jspec spec/javascripts/jsx/files` refs CNVS-33223 test plan: - current webpack test build should work exactly the same - `npm run jspec` should build + run all specs - `npm run jspec path/to/stuff` should build + run only specified specs - should work with both directories and individual files - `jspec-watch` should watch + build a path, but not run specs Change-Id: I788dd38a6c69a4c36a1300fcecf43678bc7f5327 Reviewed-on: https://gerrit.instructure.com/94625 Tested-by: Jenkins Reviewed-by: Steven Burnett <sburnett@instructure.com> Product-Review: Felix Milea-Ciobanu <fmileaciobanu@instructure.com> QA-Review: Felix Milea-Ciobanu <fmileaciobanu@instructure.com>
2016-11-08 05:13:53 +08:00
"jspec": "./spec/jspec.sh",
spec: add aXe unit testing capability this patch updates the a11y helper, adds a new spec script to run, and adds aXe testing to discussion views test plan: - run the spec files edited in this patch normally with yarn run jspec-watch path/to/spec - tests should all pass as expected - run the spec files edited in this patch with the new command yarn run a11y-report path/to/spec - you should get aXe errors on existing a11y violations Change-Id: Ib3db892046e115bedb363752d1e56226eef893af Reviewed-on: https://gerrit.instructure.com/87962 Reviewed-by: Jonathan Featherstone <jfeatherstone@instructure.com> Reviewed-by: Steven Burnett <sburnett@instructure.com> Reviewed-by: Clay Diffrient <cdiffrient@instructure.com> Tested-by: Jenkins Product-Review: Matt Berns <mberns@instructure.com> QA-Review: Matt Berns <mberns@instructure.com>
2016-08-17 05:30:29 +08:00
"jspec-watch": "./spec/jspec.sh --watch",
script to upgrade without adding dupes to yarn.lock because yarn is silly and frequently adds duplicate entries for things into yarn.lock when it could satisfy everything the app needs with one version; when you make any changes to package.json, run this script: `yarn upgrade-and-dedupe` to make sure that yarn.lock doesn't add needless duplicates of things. if yarn ever fixes this issue: https://github.com/yarnpkg/yarn/issues/579 then this can go away. test plan: 1. check this out 2. run `yarn upgrade-and-dedupe` 3. push the change that commit makes 4. it should pass jenkins and not introduce any errors Change-Id: I8c268cc4c7c6ac4474221ce65129a6ef8b261813 Reviewed-on: https://gerrit.instructure.com/142447 Tested-by: Jenkins Reviewed-by: Clay Diffrient <cdiffrient@instructure.com> Product-Review: Ryan Shaw <ryan@instructure.com> QA-Review: Ryan Shaw <ryan@instructure.com>
2018-03-03 02:20:00 +08:00
"a11y-report": "./spec/jspec.sh --a11y",
A script to just update instUI Closes: CORE-1709 This is what our Jenkins job to pull in every instui RC commit will use Test plan: * run `yarn upgrade-instructure-ui` * it should make a commit that has new entries in yarn.lock for all the instUI packages that uses the latest rc version on the npm registry * it should not affect anything else besides yarn.lock Change-Id: I78cce6e801015819c4e4b27e26ede352deceebb9 Reviewed-on: https://gerrit.instructure.com/160435 Tested-by: Jenkins Reviewed-by: Brent Burgoyne <bburgoyne@instructure.com> Product-Review: Ryan Shaw <ryan@instructure.com> QA-Review: Ryan Shaw <ryan@instructure.com>
2018-08-11 00:22:49 +08:00
"upgrade-and-dedupe": "rm -rf yarn.lock node_modules && yes 1 | yarn install --flat --production --ignore-scripts && git checkout package.json && yarn install && git add yarn.lock",
update build to load es modules from subpackages closes LA-995 flag=none 1. unify the instui ui-babel-preset options across sub-packages 2. include "@instructure" as part of each sub-package name 3. unify the commonjs and es module directory structure 4. use index.js to export anything needed to be imported from outside the package. This removes any dependency on the package's internal directory structure and makes importing independent of commonjs vs es module simple 5. move canvas-rce's main entry from async.js to index.js (I'm 98% sure index.js was an artifact of the old rce) test plan: - canvas-lms builds locally and in docker. (Jenkins builds the docker image, so I presume if it passes jenkins, the docker build wasn't broken) - sniff test the result, esp. student planner and the new rce. - yarn build:watch from canvas-rce, canvas-planner, and canvas-media packages should work, and yarn build:watch from canvas-lms should pick-up any changes. (I've verified this by finding a console.log statement and changing the message then use devtools to see it's in the new source after refreshing the browser) Change-Id: I5f242d06ad655597cd416057d4b740d4bd86003b Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/238603 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Alex Anderson <raanderson@instructure.com> QA-Review: Robin Kuss <rkuss@instructure.com> Product-Review: Ed Schiebel <eschiebel@instructure.com>
2020-05-28 06:04:02 +08:00
"upgrade-instructure-ui": "script/upgrade-instructure-ui",
Fix root unable to run npx deduplicate-yarn refs MAT-241 flag=none Test Plan: - docker-compose run --rm -u 0 web bash - verify "yarn dedupe-yarn" succeeds Change-Id: I517a420724aa548e294920da8ed93464cb744077 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/276051 Reviewed-by: August Thornton <august@instructure.com> Product-Review: August Thornton <august@instructure.com> QA-Review: August Thornton <august@instructure.com> Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com>
2021-10-16 00:46:44 +08:00
"dedupe-yarn": "yarn yarn-deduplicate",
Introduce Storybook to Canvas + i18N Canvas Inbox fixes VICE-947 This story contains work to move Canvas Inbox and Storybook to `app/jsx` inside our Monolith. Storybook should now be enabled for all of `app/jsx` and works with our existing I18n code after updating webpack to load translations correctly. Test Plan 1. Install node modules with `yarn` 2. At Canvas-LMS root, run `yarn storybook` 3. Storybook should open, test that Canvas Inbox components work as expected Change-Id: Iccd2b103164a2da4e37b5746f4d9d2b5faf5f29d Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/253024 QA-Review: Davis Hyer <dhyer@instructure.com> Product-Review: Davis Hyer <dhyer@instructure.com> Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Davis Hyer <dhyer@instructure.com>
2020-11-18 03:27:40 +08:00
"clean": "yarn workspace-run-serial clean",
Storybook config fixes closes MAT-65 flag=none - The update to package.json corrects a typo in the command line, line, plus adds a directory needed to load brandable_css - The instui babel presets in the new .babelrc.json file are needed if you want an RCE in storybook - The change to ENV in preview.js is needed if you want an RCE in storybook test plan: - storybook builds and everything still works - components are rendered using the Lato font family Change-Id: I04c45e4dc6bd853c3513ff689d63f6388d874ec1 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/263291 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Jeffrey Johnson <jeffrey.johnson@instructure.com> QA-Review: Jeffrey Johnson <jeffrey.johnson@instructure.com> Product-Review: Jeffrey Johnson <jeffrey.johnson@instructure.com>
2021-04-21 05:46:42 +08:00
"storybook": "start-storybook -p 6006 --no-dll --static-dir ./public/javascripts,./public",
Add storyshots to storybook refs OUT-4237 flag=none Test-plan: > yarn install > yarn storybook - Look through outcomes stories in storybook quickly, verify everything loads > yarn test-storybook - Verify everything passes, if something doesn't pass, verify that that corresponding story is also broken in storybook > echo $? # should return 0 and jest results should say 0 failures - Change one of the stories so that it doesn't render, For example: undo the changes made to ManagementHeader.stories.js in tis PS > yarn test-storybook - Verify that it fails > echo $? # should return 1 and jest results should say 1+ failure(s) Change-Id: I492f50d861dccdfdf4a958fd007da44041f9dd49 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/258297 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Jeffrey Johnson <jeffrey.johnson@instructure.com> Reviewed-by: Michael Brewer-Davis <mbd@instructure.com> QA-Review: Pablo Gomez <pablo.gomez@instructure.com> Product-Review: Brian Watson <bwatson@instructure.com>
2021-02-06 07:39:54 +08:00
"test-storybook": "yarn jest --roots .storybook --testMatch **/storybook.test.js"
make it so it works with yarn 1.3.2 (frd) closes: CORE-675 test plan: * while running yarn 0.27, * run `yarn` * it should work and there should only be one jquery in node_modules * brew upgrade yarn (or whatever else you do to upgrade yarn to 1.3.2) * run `yarn` * it should not log any warning about unpacking jquery to the same location as something else * it should work and not make any changes to yarn.lock or node_modules * load the calendar page, there should not be any errors Change-Id: I08a1b8ceddf31cae59720270f870516ad213b87d Reviewed-on: https://gerrit.instructure.com/133548 Tested-by: Jenkins Reviewed-by: Clay Diffrient <cdiffrient@instructure.com> Product-Review: Ryan Shaw <ryan@instructure.com> QA-Review: Ryan Shaw <ryan@instructure.com>
2017-11-22 07:09:15 +08:00
},
"resolutions": {
deduplicate yarn.lock refs DE-397 De-duplicating yarn.lock is necessary for some future InstUI upgrade work. In order to do this, we need to patch karma-webpack to avoid watching too many files within our JS job. We also need to pin babel-plugin-dynamic-import-node to the latest to work around a breaking change that causes “request of a dependency is an expression”. Both of these version pins are work arounds and will be addressed by our efforts to upgrade webpack to v5. Test Plan: 1. Ensure that “yarn dedupe-yarn” does not produce any file changes. 2. Ensure that the “JS (Karma)” job does not produce any warnings like “request of a dependency is an expression” 3. Ensure that the “JS (Karma)” job does not produce any warnings like “System limit for number of file watchers reached” 4. Ensure that Canvas front-end builds & behaves properly Change-Id: I94d77bd775bc12f9f96ac44640c862ff3e3dee79 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/256674 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Ahmad Amireh <ahmad@instructure.com> QA-Review: Ahmad Amireh <ahmad@instructure.com> Product-Review: Ahmad Amireh <ahmad@instructure.com>
2021-01-14 05:14:23 +08:00
"graphael": "https://github.com/instructure/graphael.git",
upgrade & dedupe node packages fixes FOO-2037 the result of removing yarn.lock and reinstalling packages according to the latest version within their specified range Change-Id: I1d2851d5a1a9fc6caeddc388492622ffd4f59379 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/255460 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Product-Review: Charley Kline <ckline@instructure.com> QA-Review: Charley Kline <ckline@instructure.com> Reviewed-by: Charley Kline <ckline@instructure.com>
2021-05-26 01:22:32 +08:00
"@apollo/react-testing": "3.0.1",
"@apollo/react-common": "3.0.1",
"@apollo/react-components": "3.0.1",
"@apollo/react-hoc": "3.0.1",
"@apollo/react-hooks": "3.0.1",
add resolution to storybook ts plugin flag = none Test Plan: - Existing tests pass - Story book runs correctly -- yarn storybook By upgrading to typescript 5, we broke storybook. TS 5 dropped certain methods that the storybook TS plugin relied on. https://gerrit.instructure.com/c/canvas-lms/+/313551 more information on this issue can be found in this GitHub storybook thread https: //github.com/storybookjs/storybook/issues/21642 Change-Id: If7f6c68b41e3e2fb35f183a825af2dff0aaa9ac1 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/317575 QA-Review: Drake Harper <drake.harper@instructure.com> Reviewed-by: Omar Soto-Fortuño <omar.soto@instructure.com> Product-Review: Omar Soto-Fortuño <omar.soto@instructure.com> Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com>
2023-05-06 06:29:29 +08:00
"@apollo/react-ssr": "3.0.1",
upgrade 'media-capture-new' to rc.38 flag=speedgrader_studio_media_capture test plan: - tests pass Change-Id: I655570e0066cdbd10ddd6aacf43fdad2280fb789 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/343300 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Spencer Olson <solson@instructure.com> QA-Review: Derek Williams <derek.williams@instructure.com> Product-Review: Cameron Ray <cameron.ray@instructure.com>
2024-03-20 22:19:20 +08:00
"@storybook/react-docgen-typescript-plugin": "1.0.6--canary.9.cd77847.0",
"@instructure/emotion": "8.51.0",
"@instructure/ui-a11y-content": "8.51.0",
"@instructure/ui-alerts": "8.51.0",
"@instructure/ui-buttons": "8.51.0",
"@instructure/ui-color-utils": "8.51.0",
"@instructure/ui-dom-utils": "8.51.0",
"@instructure/ui-drilldown": "8.51.0",
"@instructure/ui-grid": "8.51.0",
"@instructure/ui-icons": "8.51.0",
"@instructure/ui-menu": "8.51.0",
"@instructure/ui-responsive": "8.51.0",
"@instructure/ui-simple-select": "8.51.0",
"@instructure/ui-spinner": "8.51.0",
"@instructure/ui-text": "8.51.0",
"@instructure/ui-text-input": "8.51.0",
"@instructure/ui-truncate-text": "8.51.0",
"@instructure/ui-view": "8.51.0",
"@instructure/uid": "8.51.0"
AMD Conversion "Trivial" JavaScript / CoffeeScript changes -------------------------------------------------- For the most part, all javascript was simply wrapped in `require` or `define`. The dependencies were found with a script that matched regexes in the files, it errs on the side of listing too many dependencies, so its worth double checking each file's dependencies (over time, anyway). i18n API changes -------------------------------------------------- No longer have to do I18n.scoped calls, just list i18n as a dependency with the scope and it's imported already scoped require ['i18n!some_scope'], (I18n) -> I18n.t 'im_scoped', 'I'm scoped!' JS bundling now done with r.js, not Jammit -------------------------------------------------- We don't use jammit to bundle JS anymore. Simply list dependencies for your JS modules in the file and RequireJS handles the rest. To optimize the JavaScript, first make sure you have node.js 0.4.12+ installed and then run: $ rake js:build The app defaults to the optimized build in production. You can use non-optimized in production by putting ?debug_assets=true in the url just like before. You can also test the optimized JavaScript in development with ?optimized_js=true. Significant changes -------------------------------------------------- These files have "real" changes to them (unlike the JavaScript that is simply wrapped in require and define). Worth taking a really close look at: - app/helpers/application_helper.rb - app/views/layouts/application.html.erb - config/assets.yml - config/build.js - lib/handlebars/handlebars.rb - lib/i18n_extraction/js_extractor.rb - lib/tasks/canvas.rake - lib/tasks/i18n.rake - lib/tasks/js.rake Change-Id: I4bc5ecb1231f331aaded0fef2bcc1f3a9fe482a7 Reviewed-on: https://gerrit.instructure.com/6986 Tested-by: Hudson <hudson@instructure.com> Reviewed-by: Ryan Florence <ryanf@instructure.com>
2011-11-11 00:31:45 +08:00
}
maintain precision of grades in grade input fixes GRADE-1098 test plan: 1. Create an Assignment a. with Display Grade as Percentage b. worth 9.5 points 2. Open New Gradebook 3. Grade a student on this assignment twice a. once with 55 (interpreted as percentage) b. again with 55% (explicit percentage) 4. Verify grade is 55% 5. Verify score is 5.225 Change-Id: Ie48ec7d5b787e864bfd3379e8dc6a4dbebebc2e5 Reviewed-on: https://gerrit.instructure.com/148848 Tested-by: Jenkins Reviewed-by: Derek Bender <djbender@instructure.com> Reviewed-by: Shahbaz Javeed <sjaveed@instructure.com> QA-Review: Shahbaz Javeed <sjaveed@instructure.com> Product-Review: Matt Goodwin <mattg@instructure.com>
2018-05-02 04:54:56 +08:00
}