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 🙏

© 2024 – Pkg Stats / Ryan Hefner

testcafe-serverless-cli

v0.0.5

Published

Deploy lambdas and resources: ```sh npx testcafe-serverless-cli init --accessKeyId=XXXXXXXXXXXX --secretAccessKey=XXXXXXXXXXXX ```

Downloads

10

Readme

testcafe-serverless-cli

Deploy lambdas and resources:

npx testcafe-serverless-cli init --accessKeyId=XXXXXXXXXXXX --secretAccessKey=XXXXXXXXXXXX

Run testcafe tests:

npx testcafe-serverless-cli run --accessKeyId=XXXXXXXXXXXX --secretAccessKey=XXXXXXXXXXXX --testcafeDir=/path/to/test-cafe-project --concurrency=1

You can pass the following options to the npx testcafe-serverless-cli run [options] function.

Parameter | Type | Description | Default ----------------- | ------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------- skipJsErrors | Boolean | Defines whether to continue running a test after a JavaScript error occurs on a page (true), or consider such a test failed (false). | false skipUncaughtErrors | Boolean | Defines whether to continue running a test after an uncaught error or unhandled promise rejection occurs on the server (true), or consider such a test failed (false). | false selectorTimeout | Number | Specifies the time (in milliseconds) within which selectors make attempts to obtain a node to be returned. See Selector Timeout. | 10000 assertionTimeout | Number | Specifies the time (in milliseconds) within which TestCafe makes attempts to successfully execute an assertion if a selector property or a client function was passed as an actual value. See Smart Assertion Query Mechanism. | 3000 pageLoadTimeout | Number | Specifies the time (in milliseconds) TestCafe waits for the window.load event to fire after the DOMContentLoaded event. After the timeout passes or the window.load event is raised (whichever happens first), TestCafe starts the test. You can set this timeout to 0 to skip waiting for window.load. | 3000 speed | Number | Specifies the test execution speed. A number between 1 (fastest) and 0.01 (slowest). If an individual action's speed is also specified, the action speed setting overrides the test speed. | 1 stopOnFirstFail | Boolean | Defines whether to stop a test run if a test fails. You do not need to wait for all the tests to finish to focus on the first error. | false