Skip to main content

Runtime support for pdf-parse and csv-parse

Validating PDF and CSV files are a big part of our test suite. Would really appreciate these two being added as it’s needed for us to use Browser Checks.

Although we did notice that pdf2json was included in the runtime already, but trying to replace pdf-parse with it proved to be too much of an effort. We also tried the same using fs to replace csv-parse, but the parse packages already do the heavy lifting.

> npx checkly test --list
Validating project resources... ✅

Bundling project resources... ❌

    Error: Encountered an error parsing check files for <filePathRedacted>.

    The following NPM dependencies were used, but aren't supported in the runtimes.
    For more information, see https://www.checklyhq.com/docs/runtimes/.
        <filePathRedacted> imports unsupported dependencies:
                pdf-parse
                csv-parse
Status: Completed9 comments

Log in to comment and vote

Comments9

  • Michelle Liebheit

    •

    Mar 31

    Hi Matthew, I just wanted to let you know that we have included csv-parse and pdf-parse in our newest runtime 2026.04. Thank you for your request and happy monitoring!

  • Hervé Labas

    Team•

    Jan 12

    Hi Matthew!
    Have you tried using Playwright Check Suites to that end? They allow custom dependencies and would be able to run your tests as is.

    Let us know how that goes!

    • Matthew Capdeville

      •

      Jan 12

      Hey Hervé, yes that’s actually how we’re currently using Checkly through our existing Playwright tests. Our plan was to start using Browser Checks, but these two dependencies are blocking us from doing so.

      • Hervé Labas

        Team•

        Jan 12

        I see. Out of curiosity, what was the motivation behind moving from a Playwright Check Suite to Browser Checks? Since Playwright Check Suites are new and more capable overall, I’d love to understand the context behind that! 🙏

        • Matthew Capdeville

          •

          Jan 12

          For our situation we needed checks that we’re both cost efficient and highly available. After reading the documentation, Browser Checks seemed to fit that role. For example we could run a login Browser Check every 1 minute that gives us quick results vs our login Playwright Suite Check that runs all the login tests every 30 minutes. Hope that explained it well enough and if there is a suggestion on how to do it differently, we’re open to it!

          • Hervé Labas

            Team•

            Jan 13

            OK yeah that makes a lot of sense, thanks for sharing!