npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@jspsych/new-plugin

v0.3.1

Published

CLI tool to create new jsPsych plugins

Readme

@jspsych/new-plugin

This package allows you to start building a plugin in any directory by simply running npx @jspsych/new-plugin from the command line.

You will be prompted to enter a name for your plugin, a description, the name of the author, an optional link to the author's GitHub profile, the preferred language (TypeScript or JavaScript) for your plugin, and an optional link to a README.md file for your plugin. Your template package containing boilerplate code will then be automatically generated in your current working directory.

[!NOTE] If you are running this command in the jspsych-contrib repository, you will not be prompted to enter a README.md link. It will be generated automatically, and your template package will also be automatically generated under the ./packages folder.

In the generated package, you will find a ./docs folder containing a markdown file for you to fill in technical information about your plugin, e.g. additional parameters it takes in and the data it generates. You will also find an ./examples folder where you can write simple scripts to demonstrate the functionality your plugin provides. The file that contains your actual plugin code should be the index.js file under the ./src folder. Lastly, we also provide a package.json for you to list metadata about your plugin so that it can be easily published to a registry like npm, a README.md and a CITATION.cff file. If you plan to publish your plugin, we highly recommend filling out the CITATION.cff file as it allows your plugin's users to easily cite your plugin.