Support for Cypress 15.0.0

[CamilleDrapier]

Since Cypress 15.0.0 was released a short while ago, it would be great if @quasar/quasar-app-extension-testing-e2e-cypress would allow using it.

I have run a few test with cypress 15.0.0, and it seems to be generally working, but maybe there is more than just adding the 15.0.0 version to the allowed peer dependencies:

-     "cypress": "^12.2.0 || ^13.2.0 || ^14.0.0",
+     "cypress": "^12.2.0 || ^13.2.0 || ^14.0.0 || ^15.0.0",

[IlCallo]

I'm afraid there will be something more to do
I'll try to do the upgrade in the following weeks

If possible, I'll release a minor version allowing Cypress 15 usage
Then I'll release a major version which drops all previous Cypress versions, containing breaking changes and Node versions bumps

[FelixNumworks]

Hi :)
Do you have a schedule for when this could be fixed @IlCallo ? Thank you !

[IlCallo]

As predicted, upgrading to Cypress 15 is way harder than expected, mainly due to the second error that @FelixNumworks reported here

As Felix noted, that error comes from Cypress 15 itself using tsx and Vite 6 and 7 not handling it correctly for sass package, which is ironic since using tsx was the solution for many other TS+Cypress problems

It would work fine for Vite 6 if we were using legacy api for Sass compiler in Vite, but that's deprecated in Vite 6 and removed in Vite 7
Quasar switched to the modern-compiler (now the default) quite some time ago already.

I also just noticed that Cypress v15 component testing won't work at all if quasar dev hasn't been run first
I don't remember hitting this problem before, but it's extremely rare to run the Cypress component test command with UI without having worked on the project running quasar dev anyway

That said, that's a blocker for Cypress 15 support, no matter the Vite and app-vite version
The workaround is already clear and there are PRs to fix it on Vite side, but up until now they didn't take action

Right now I have everything ready for a minor release to support Cypress 15, aside that issue over which we don't have control.

I'll freeze the development on this feature for now, since it's not possible to have Cypress 15 working with app-vite out of the box, and wait until something happens on Cypress, Vite or TSX side

You can find my work on this PR

Relevant resources:

• Cypress 15 component testing fails with sass error cypress-io/cypress#32362
• fix(css): workaround tsx esModule interop of sass-embedded import vitejs/vite#19182
• __esModule interop is applied to .cjs files privatenumber/tsx#627