Pranav 9de8c27368 feat: Use vitest instead of jest, run all the specs anywhere in app/ folder in the CI (#9722) ... Due to the pattern `**/specs/*.spec.js` defined in CircleCI, none of the frontend spec in the folders such as `specs/<domain-name>/getters.spec.js` were not executed in Circle CI. This PR fixes the issue, along with the following changes: - Use vitest instead of jest - Remove jest dependancies - Update tests to work with vitest --------- Co-authored-by: Muhsin Keloth <muhsinkeramam@gmail.com>		2024-07-10 08:32:16 -07:00
..
dashboard	feat: Use vitest instead of jest, run all the specs anywhere in app/ folder in the CI (#9722)	2024-07-10 08:32:16 -07:00
packs	feat: Adds the ability to disable the "new message notification" popup (#9594)	2024-06-11 08:14:58 +05:30
portal	feat: Use vitest instead of jest, run all the specs anywhere in app/ folder in the CI (#9722)	2024-07-10 08:32:16 -07:00
sdk	feat: Use vitest instead of jest, run all the specs anywhere in app/ folder in the CI (#9722)	2024-07-10 08:32:16 -07:00
shared	feat: Use vitest instead of jest, run all the specs anywhere in app/ folder in the CI (#9722)	2024-07-10 08:32:16 -07:00
superadmin_pages	refactor: handling keyboard shortcuts (#9242)	2024-04-26 15:41:02 +05:30
survey	chore(i18n): Update the latest translations (#9340)	2024-05-02 08:18:17 -07:00
v3	feat: Use vitest instead of jest, run all the specs anywhere in app/ folder in the CI (#9722)	2024-07-10 08:32:16 -07:00
widget	feat: Use vitest instead of jest, run all the specs anywhere in app/ folder in the CI (#9722)	2024-07-10 08:32:16 -07:00