Skip to main content

Customisation of NPM Dependencies

Feature RequestRuntimes

Summary:

Allow users to customise or override the NPM dependencies within the Checkly runtime environment.

Description:

Currently, users are restricted to a set list of packages and versions in the Checkly runtime, which may not cover all the specific use cases or compatibility issues they encounter. As a Checkly user, I need to be able to dynamically use packages in my own runtime. I process dependency updates in projects regularly to use the latest versions for new features and security updates.

Posted by Alex Noyes ·
Status: Completed3 comments

Log in to comment and vote

Comments3

  • María de Antón changed status to Completed
    •

    Oct 24, 2025

    Pinned

    The time has come! You can absolutely customize and tell us which NPM, PNPM or Yarn dependencies you need to run your Playwright Checks, as you know better than us, which are the right ones to use!

    As such, Playwright Check Suites support both public and private dependencies. Public dependencies work as such, out of the box, and private ones require secure credentials configuration. Learn more about custom dependencies.

    → Here’s how to create your first Playwright Check Suite today!


    On top of this, you also get full playwright compatibility: Projects, multiple-browsers, fake media devices, storageState, custom dependencies, you name it.


    If you have any questions, please, do ask! As the PM behind these new checks, I’m here for it!

    Happy monitoring!

  • Kristian Munkvold

    •

    Nov 25, 2024

    Huge +1 on this one

  • coryreid

    •

    Jul 18, 2024

    +1 for this request - even if this was limited to just private locations, I’d love the ability to use the Checkly agent as a base image and build a custom container with any additional tooling/NPM packages to support specific context around our checks.