fix(tests): separate type import for Windows ESM compatibility

Split mixed import to use 'import type' for MockChargingStation type.
Windows Node.js ESM module resolution strictly enforces that type-only
exports cannot be imported as values in mixed import statements.

diff --git a/tests/charging-station/ocpp/2.0/OCPP20TestUtils.ts b/tests/charging-station/ocpp/2.0/OCPP20TestUtils.ts
index 87a728535cc459d89493bf445ee581497fd43dae..5a3b8f4d6aa5ae9551c9fcdd7b17d7e9bf4be687 100644 (file)
--- a/tests/charging-station/ocpp/2.0/OCPP20TestUtils.ts
+++ b/tests/charging-station/ocpp/2.0/OCPP20TestUtils.ts
@@ -17,6 +17,7 @@ import type {
   OCPP20IdTokenType,
   OCPP20TransactionContext,
 } from '../../../../src/types/ocpp/2.0/Transaction.js'
+import type { MockChargingStation } from '../../ChargingStationTestUtils.js'
 
 import {
   ConnectorStatusEnum,
@@ -27,7 +28,7 @@ import {
 import { OCPP20IdTokenEnumType } from '../../../../src/types/ocpp/2.0/Transaction.js'
 import { Constants } from '../../../../src/utils/index.js'
 import { TEST_CHARGING_STATION_BASE_NAME } from '../../ChargingStationTestConstants.js'
-import { createMockChargingStation, MockChargingStation } from '../../ChargingStationTestUtils.js'
+import { createMockChargingStation } from '../../ChargingStationTestUtils.js'
 
 // ============================================================================
 // Testable Interfaces