Nick McCurdy

I've had success with using Karma for that sort of thing in the past, but maybe a more modern alternative like Cypress or Playwright would be easier to set up...

I'm aware, but maybe we could write an abstraction layer that could rust tests in something like Vitest and something like Cypress.

Should this be closed? I noticed the original issue (#587) is.

We assume users use JSDOM, which [doesn't implement most CSS layout features](https://github.com/jsdom/jsdom#unimplemented-parts-of-the-web-platform), so I'm not sure how useful it would be for a test to depend on what is scrollable/visible....

Does cypress-testing-library handle events using dom-testing-library or is it assumed that users will use Cypress commands directly?

In that case, I guess it comes down to if this is worth the effort to support without Cypress. If you have a test like this it's entirely possible that...

You could mock whatever your code uses to detect scroll position. Or if that logic is in its own function you can replace the entire thing with a mock.

Single and double quotes are supported in the JS/ES spec. This doesn't have anything to do with Vue, Create Vue, Vite, ESLint, or Prettier.

I know this article is for Circle and we’re already using Travis, but I really like how reusable GitHub Actions is and I think it would help for automating tasks...

@lipis You have access to the Chrome extension in the Web Store, right? Would you mind adding these [credentials](https://github.com/DrewML/chrome-webstore-upload/blob/master/How%20to%20generate%20Google%20API%20keys.md) to our [secrets](https://github.com/prettier/prettier-chrome-extension/settings/secrets) like [this](https://github.com/marketplace/actions/chrome-addon-action) so we can try automating it?