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

@muuktest/amikoo-playwright

v2.1.3

Published

Playwright DOM failure capture library. Automatically captures DOM state and screenshots when tests fail.

Readme

@muuktest/amikoo-playwright

Automatically captures DOM state and screenshots when Playwright tests fail. Configures the Amikoo MCP server and updates the Playwright fixture so test errors can be analyzed by the Amikoo Repair Agent.

The Amikoo Repair Agent auto-heals 70-80% of all broken test cases, saving days worth of time over the course of a month.

Installation

npm install @muuktest/amikoo-playwright && npx @muuktest/amikoo-playwright init

The init command sets up the MCP configuration.

How to configure the Agent in VS Code

Prerequisite: You need an access token to exercise the Amikoo Repair Agent. If you do not have such a token, please submit a request: https://muuktest.com/amikoo-playwright-mcp#section-8

  1. Open VisualStudio (VS) Code.
  2. Open your Playwright project folder.
  3. Open the Chat Agent panel. This can be done via the menu selecting View > Chat or using the shortcut Control⌃ + Command⌘ + I (Mac) or Ctrl + Alt + I (Windows/Linux).
  4. Click the Agent dropdown and select the amikoo-playwright-agent option.
  5. Copilot now will use the Amikoo MCP server to repair the test cases. Refer to "How to run" for the next steps.

Note: The first time you exercise the agent, VS Code will ask you for your Access token. Enter your previously requested token. If you do not have an access token, please submit a request: https://muuktest.com/amikoo-playwright-mcp#section-8

Agent setup

Learn More

See the MCP server documentation for details on the agent and available tools.

How to Run

Repairing a Failing Test

  1. Run your failing Playwright test as usual.
    • When the test fails, Amikoo automatically captures the necessary context data inside the test-results directory.
  2. Open the Agent panel in VS Code.
  3. Ask the amikoo-playwright-agent to fix the failing test.

The agent will:

  • Analyze the captured error context.
  • Identify the relevant files in your project.
  • Propose and apply fixes to your test or related code using amikoo-mcp.
  • Re-run the test to verify the issue has been resolved.

Important Notes

  • The agent repairs one test at a time.
  • If multiple errors exist, the agent resolves them one by one, re-running the test after each fix.
  • The process ends automatically once the test passes.

Support

For support, contact [email protected].