Jess

Closing the loop on this... I released the global polyfill and modifying String.includes started throwing errors on one of our major partner sites: `Cannot redefine non-configurable property 'includes'` I had...

👋🏻 I highly suggest using Cypress Component Testing. I'm the maintainer and I'm happy to help you out. Right now we have framework-specific bindings, but writing a wrapper for vanilla...

There was an open issue in the Istanbul plugin that was recently fixed for this... can you give this a try @lucaspeterson22 https://github.com/iFaxity/vite-plugin-istanbul/issues/13?

OK I understand the two approaches and the problem you're trying to solve by unifying the icon library configurations across the three tools we have. I'm trying to understand the...

@TheJaredWilcurt and I spoke on the Cypress Discord. Essentially, this is because he can't strip `v-data*` out, which is generated. The third party solution https://github.com/meinaart/cypress-plugin-snapshots is able to solve his...

The latest binary has the issue where if your current nvm version is < node 12, and you fix it, you can't re-open it -- it just bounces once in...

@pimlie I can't use the Cmty issue reporter because the Version field is required and there have been no versions released :-( 

Yeah. It does include the typo. I’ll clear the modules and retry On Sun, Mar 8, 2020 at 9:09 AM Pim wrote: > Unfortunately I have no idea where this...

If we're going with ts-jest, it should not fail. You can write TS code that won't compile and it'll pass unit tests. ts-jest doesn't use the typescript compiler. This was...

I think the dream is that we listen to the user's existing settings and use the ts-jest or babel-jest settings they have. If TS users want their stuff to fail...