jsPsych package updates
- Dominant language
- Python
- Stars
- 12
- Forks
- 21
- Avg merge
- 5d 19h
- Merged PRs (30d)
- 5
Description
## TL;DR
jsPsych packages have updated, and we should decide when we want to update our versions.
## Summary
We're loading several [jsPsych packages](https://lookit.readthedocs.io/en/master/researchers-jspsych-intro.html#jspsych-packages) that have been updated. Some things to consider:
- Communicating updates to researchers, since we currently have no way for researchers to control the specific versions used in their studies.
- The jsPsych core version here needs to match the version used in CHS-jsPsych, so we will need to update these in parallel.
- Establishing a package update workflow for patch vs minor vs major updates.
- Is there a way to configure dependabot updates for these packages? (They're loaded via a script tag and not listed in any dependency files, so they aren't picked up by dependabot).
Contributor guide
Research direction
Review the jsPsych package references loaded through script tags and compare them with the versions used by CHS-jsPsych. Determine the current package-update workflow and dependency-file configuration, then document a concrete approach for version updates, researcher communication, and Dependabot support.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- developer-experience, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100