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

dceky

v1.0.26

Published

Cypress toolkit for Harvard DCE

Readme

dceky

A Cypress-based testing framework by Harvard DCE

Getting Started

It's easy to use ky as your testing framework. To get started, follow these steps:

1. Install and Configure Cypress

Install Cypress: npm i --save-dev cypress

Configure Cypress:

  1. Use npx cypress open
  2. Choose "E2E"
  3. On the configuration page, simply click "Continue"
  4. When you get to the browser chooser, close Cypress

From this point onward, you won't run cypress directly

2. Install and Set Up Ky

Install ky: npm i --save-dev dceky

Set up ky: npm run ky:setup

You'll have a bunch of changes to commit and push. Do that now.

Using Ky

Start Ky Tests: npm run ky:start

To start running ky tests, use npm run ky:start and follow instructions.

You'll be automatically guided through a launch process where you'll choose whether tests will run visibly or headless, which profile(s) you'll use, and which browser(s) you'll use. You can also set these through environment variables or arguments. See the examples below:

// Arguments:
npm run ky:start --headless --browser=Chrome,Safari --profile=Stage
// Example environment:
HEADLESS=true
BROWSER=Chrome,Safari
PROFILE=Stage

Setup Ky: npm run ky:setup

Whenever you update the version of ky or make changes to supporting project-specific commands or other non-test files, you should run ky:setup.

This will regenerate configuration files, typescript declarations, and other ky resources that keep your project working smoothly.

Setup and Start Ky Tests: npm run ky:dev

QA people and CI systems should start tests using npm run ky:start because that ensures that no files, dependencies, or files will be changed on run.

But, developers should run tests using npm run ky:dev because each time the tests are run, ky is automatically set up again, ensuring that ky files are up-to-date and running smoothly.