Avoid clashing global types between Cypress and Jest

Hello. Thank you for this library. Describe the bug I use cypress-fail-fast in a project with common cypress config for other projects. It has jest test for custom cypress commands. After install cypress-fail-fast I have typescript error “Property ‘toEqual’ does not exist on type ‘Assertion’. Did you mean ‘equal’? ts(2551) index. d. ts (206, 9): ‘equal’ is declared here.” If delete /// <reference types="cypress" /> in the plugin. d. ts and index. d. ts errors disappears. So I suggest delete these two lines from cypress-fail-fast. I tried it and it is ok.

[javierbrea]

Hi, @javierbrea! Thank you for detail explanation. Your suggestion about purpose of my repository exactly right. Created tsconfig for jest tests helped me, but if you will have more information about this issue, for example, why another plugin did not this typescript error, write in this issue.

You’re welcome @aleksey-ilin 😃

Well, other plugins may not produce this conflict due to multiple reasons:

• Other plugins may don’t have dependency with Cypress types. This one does because it is extending Cypress’ TestConfigOverrides interface in order to provide custom options to specs, and in the Node.js side it needs to extend Cypress plugin options.
• Other plugins may don’t even have TypeScript types. For example, the other plugin you are using: cypress-image-snapshot
• You may be using other plugins, but you don’t import them from your Jest tests. This one neither produces a conflict if you don’t import it in your Jest tests, and you have TypeScript configured properly.

And, finally, I don’t know if other plugins define the dependency with Cypress, which produces the conflict. But, as mentioned in my previous comment, it is a real dependency, so, I think that it shouldn’t be removed to “fix” a conflict between Jest and Cypress. That conflict is not a problem of this plugin, and removing the dependency here would be only a workaround.

[aleksey-ilin]

Hi, @javierbrea! Thank you for detail explanation. Your suggestion about purpose of my repository exactly right. Created tsconfig for jest tests helped me, but if you will have more information about this issue, for example, why another plugin did not this typescript error, write in this issue.