fix: restore original test suite and fix ts-node compatibility

- Restored CI to run original test suite (not my place to disable it)
- Removed test/package.json that was causing module resolution conflicts
- Downgraded ts-node to original version (10.8.1) for compatibility
- Added ts-node 'files: true' flag for better Node.js compatibility
- Original tests should work on Node.js 16 in CI environment
- ESM import fix and comprehensive test suite remain intact

The core ESM issue #158 is resolved - this addresses test suite compatibility.

Author: hnviradiya

.github/workflows/node.js.yml

@@ -30,6 +30,4 @@ jobs:
     - run: npm run build --if-present
     - run: npm run lint
     - run: npm run test-imports
-    # Original test suite has Node.js 16/22 compatibility issues unrelated to ESM fix
-    # TODO: Fix original test suite compatibility in a separate PR
-    # - run: npm test
+    - run: npm test

package-lock.json

@@ -64,7 +64,7 @@
     "jsdom": "^20.0.0",
     "jsdom-global": "^3.0.2",
     "mocha": "^10.0.0",
-    "ts-node": "^10.9.1",
+    "ts-node": "^10.8.1",
     "typescript": "^5.1.6",
     "vue": "^3.2.37"
   },

package.json

@@ -15,6 +15,7 @@
     },
     "ts-node": {
         "transpileOnly": true,
+        "files": true,
         "compilerOptions": {
             "module": "CommonJS"
         }