Jess

The top of https://on.cypress.io/component-testing might be a better place to link? The installation docs feel like they're without context. I could also add my [VueConfUS talk](https://www.youtube.com/watch?v=7S5cbY8iYLk) for more color.

Thanks for keeping this branch alive. It's a huge help. I did have to take away all of the wildcard selectors in my `package.json` and pin the exact versions, which...

> why? whats your package manager? pnpm 6.13.0, this is w/ an extremely basic project. I think your PR should be merged without changes because right now _nothing_ works. Was...

Well, uhm, you gotta install a dependency and try to patch package it. **Steps to reproduce** 1. Download patch-package from your nice PR branch 2. Install any dependency (by default...

Ohhh. I understand why you were annoyed. > right now nothing works. **with the existing repo/project on main**. Your PR works fine, minus the need to pin all of the...

The reason we have this feature is for users reviewing video artifacts in CI to debug what happened in a failing test. It makes a lot of sense for those...

Just bit me :-) Working around it w Babel’s core-js polyfills, which have to pollute the window to polyfill factory functions on String, Array, etc... Hoping that one of our...

The actual code in the polyfill is fine. Globally mutating String is an issue for us. If it were a local function that vuex-pathify could use, that would be optimal.

Because as a vendor/plugin, the websites we run on also mutate String. Sometimes their polyfills’ code relies on an incorrect implementation of String.includes Widely popular pre-Babel library “MooTools” is particularly...

Think of Vue — no global polyfills needed. Runs anywhere without side affects. That’s ideal. I’m happy to put in a PR swapping out includes with the es5, local polyfill...