@quasar/testing-unit-vitest v1.2.3 depending on critically vulnerable version of happy-dom

[mr-gurke]

Hi,

I wanted to say thanks for providing this package, first.

Today our pipeline crashed, because of the problem outlined in the title. Will there be a fast fix for this?

All the best!

[IlCallo]

Seems like happy-dom dropped Node 18 support in May
Version 19 explicitly removes CJS support, noting that Node 18 isn't supported anymore

This means we need to release a new major version to fix this
Meanwhile, we're not so far away from Vitest 4, so I'd prefer to wait until that's released as stable before releasing a new major version

As a fast fix you can use overrides option to force the happy-dom version to v20 and see if everything works fine

I don't consider the problem to be as security critical as it could seem, because we use happy-dom to run unit tests, which are fully in control of the dev and run locally
In our case happy-dom is used in a "safe environment", unless the dev itself injects something nasty in its own tests

[mr-gurke]

Thanks for the reply! Overrides solves the problem for me perfectly.

[IlCallo]

I started working on Vitest 4 support, modernizing the AE codebase in the meantime
You can keep track of the progress here: #409

I still need to get the build process right