This is an open repository of jsPsych plugins and extensions developed by members of the jsPsych community. If you've written a jsPsych plugin or extension that you think others might be interested in using, this is the place to share it!

Plugins and extensions in the main jsPsych repository are maintained by the core jsPsych team. The team takes responsibility for fixing bugs and updating plugins to take advantage of new features in jsPsych.

Plugins and extensions in this jspsych-contrib repository are contributed by community members. They are not extensively tested or verified by the core jsPsych team, and there is no guarantee that anyone will be available to fix bugs, push updates, or answer questions about these plugins/extensions. However we would encourage contributors to respond to issues/questions and to maintain their code.

Contributions to jspsych-contrib that are broadly useful, well-documented, and well-tested may be added to the main jsPsych repository, with the contributor's permission.

Contributions to this repository must:

• Be functional -- they must work in at least some particular circumstance.
• Include the complete code for the plugin or extension.
• Include a readme.md file following our template.
• Include a package.json file.

Optionally, contributions can include:

• A /docs directory with documentation matching the template for docs on jspsych.org
• An /examples directory with a working .html demo.
• A test suite following the testing framework in our -ts templates.

To submit a contribution, open a pull request that contains a directory for your plugin/extension inside the /packages directory. In the pull request comments, please make it clear how we can verify that the contribution is functional. This could be accomplished with a link to a demonstration experiment, the inclusion of an example file and/or testing files, or through some other means. We try to review pull requests quickly and add new contributions as soon as the minimal standards are met.

There are two plugin template directories inside the /packages directory that you can use as a reference when creating a directory for your plugin contribution. Both templates are compatible with jsPsych v7+.

Regardless of which template you use, you can get started by creating a copy of the template folder in /packages and renaming it according to your plugin/extension name. You may also want to read the jsPsych documentation on plugin development to understand how to work with the index.tsfile (in plugin-template-ts) and index.js file (in plugin-template). In your plugin/extension folder, be sure that you also:

• Edit the package.json file
• Add a readme.md file to your plugin/extension directory, based on the readme template

This template uses TypeScript source files that are complied into JavaScript using Node.js and npm. This is the format used for plugins in the main jsPsych repo. To use this template, you should edit the src/index.ts file, keeping the overall structure but changing the details as appropriate (plugin name, parameters, trial method, etc.). You can then use the npm run build command to compile your index.ts code into JavaScript files, which will appear in a /dist directory. This format also allows you to add a Jest test file (optional), which you can create based on the src/index.spec.ts template file.

In the rollup.config.mjs file, replace "jsPsychPluginName" with your plugin name. You do not need to edit the other config files in this template directory.

For more details, including setup instructions and detailed explanations of files, please see the jsPsych documentation page: Configuring the jsPsych development environment. You can also read the plugin development documentation and look at the plugin/extension folders in the main jsPsych repository /packages directory for more examples.

This template allows you to put your plugin's JavaScript code directly into a JavaScript template file, rather than using TypeScript and Node.js/npm. To use this template, you should keep the overall structure of the index.js file, but change the details as appropriate for your plugin (plugin name, parameters, etc.). The JavaScript code that runs the trial goes inside the trial method for the plugin class. More information about working with the index.js file can be found in the plugin development documentation.

We would like to encourage you to contribute plugins and extensions that are compatible with the latest jsPsych version. At the same time, we realize that there may be jsPsych users who have created very useful plugins/extensions with jsPsych v6 that they would like to share with the community, but don't have the time/resources to convert into the jsPsych v7+ Node package format. Therefore we welcome contributions that are compatible with v6 as well as v7+.

If you'd like to contribute a jsPsych v6 plugin, please do the following:

• Use the plugin-template directory as a reference
• Delete everything inside of the index.js template file and replace it with your v6-compatible plugin code
• In the package.json file, change the "jspsych" version field in "devDependencies" to "6.3.1"

And remember to follow the other steps for contributing:

• Edit the package.json file with the information about your plugin
• Add a readme.md file for your plugin, based on the readme template. This must state the jsPsych version that your plugin is compatible with.
• Optional: add a /docs directory with a markdown documentation file, and/or /examples directory with an HTML example file