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

playwright.testing.template

v1.0.9

Published

A boilerplate template for a Playwright test framework to API and E2E test an application.

Downloads

14

Readme

Playwright test framework boilerplate

A boilerplate template for a Playwright test framework to API and E2E test an application.

Get Started

Coming soon tm

API Tests

Coming soon tm

UI Tests

Coming soon tm

Issues

Coming soon tm

  • The package.json in our package has a dependency version, should we change this to use latest?
    • fine to do that as can be justified by needing latest browser support via PW
  • The target project's package.json will not contain our script entries. Should we modify the target's package.json so it does? Seems intruisive.
    • Could just have the instructions in the readme.
    • A: As long as they are custom scripts as they won't override standard scripts that a user might need. In addition find to override as that provides a better experience if there are breaking changes that need updating in the script
  • Need to test what happens when you update the package within a project, does it override existing files? How to approach this if it does.
    • A: Might be better to leave files that shouldn't be modified in the node folder.
  • Have to test and make sure this will still run in a pipeline, concern is that the browsers might not be installed as part of Playwright
    • Pending