fix: import @testing-library/jest-dom matchers in their own setup s…

…cript

Technically we could just add the import to `setupFilesAfterEnv`, but then they'd not get picked
up by TypeScript since we wouldn't actually be "importing" them in a TS file.

variants/frontend-stimulus-typescript/jest.config.ts

@@ -9,7 +9,7 @@ const config: Config.InitialOptions = {
 
   testPathIgnorePatterns: ['config/'],
   setupFilesAfterEnv: [
-    '@testing-library/jest-dom/extend-expect',
+    './app/frontend/test/setupJestDomMatchers.ts',
     './app/frontend/test/setupExpectEachTestHasAssertions.ts'
   ],
 

variants/frontend-stimulus-typescript/template.rb

@@ -29,5 +29,6 @@
 remove_file "app/frontend/stimulus/controllers/add_class_controller.js", force: true
 copy_file "app/frontend/stimulus/controllers/add_class_controller.ts"
 
+rename_js_file_to_ts "app/frontend/test/setupJestDomMatchers"
 rename_js_file_to_ts "app/frontend/test/setupExpectEachTestHasAssertions"
 rename_js_file_to_ts "app/frontend/test/stimulus/controllers/add_class_controller.test"

variants/frontend-stimulus/app/frontend/test/setupJestDomMatchers.js

@@ -0,0 +1,2 @@
+// this makes the jest-dom matchers available on `expect`
+import '@testing-library/jest-dom';

variants/frontend-stimulus/jest.config.js

@@ -9,7 +9,7 @@ const config = {
 
   testPathIgnorePatterns: ['config/'],
   setupFilesAfterEnv: [
-    '@testing-library/jest-dom/extend-expect',
+    './app/frontend/test/setupJestDomMatchers.js',
     './app/frontend/test/setupExpectEachTestHasAssertions.js'
   ]
 };