review comment

README.md

@@ -103,5 +103,8 @@ if the version is not updated, delete node_modules folder and reinstall
 
 The idea is you can publish the new version using `release` job on CI. 
 
-# for playwright
+## for playwright
 please read doc/PLAYWRIGHT.md
+
+## for vitest 
+please read doc/VITEST.md

package.json

@@ -19,7 +19,7 @@
     "@playwright/test": "^1.30.1",
     "@types/jest": "^29.5.1",
     "@types/luxon": "^3.3.0",
-    "@types/node": "^20.3.3",
+    "@types/node": "^20.11.16",
     "@types/uuid": "^9.0.2",
     "jest": "^29.5.0",
     "jest-environment-jsdom": "^29.5.0",

src/vitest/common.ts

@@ -55,10 +55,6 @@ export const getCommonMetadata = (
   };
 };
 
-const ENDPOINT_FROM_TYPE = {
-  vitest: process.env.VITEST_TESTDATA_API_URL ?? UNKNOWN_VALUE, // your api endpoint eg. http://your_domain/vitest
-};
-
 const LOG_FILE = 'devfeedback.log';
 
 const sendData = async (endpoint: string, data: CommonMetadata): Promise<boolean> => {
@@ -71,7 +67,7 @@ const sendData = async (endpoint: string, data: CommonMetadata): Promise<boolean
 };
 
 export const sendTestData = async (testData: VitestTestData) => {
-  const endpoint = ENDPOINT_FROM_TYPE[testData.type];
+  const endpoint = process.env.VITEST_TESTDATA_API_URL ?? UNKNOWN_VALUE; // your api endpoint eg. http://your_domain/vitest
 
   console.log(`Your test time was ${testData.timeTaken.toFixed(2)}ms.`);