Error: Exit code 1 [2024-10-26T18:01:49.463Z] INFO Mesh Compose Found default config file e2e/js-config/mesh.config.js (node:9907) Warning: To load an ES module, set "type": "module" in the package.json or use the .mjs extension. (Use `node --trace-warnings ...` to show where the warning was created) [2024-10-26T18:01:49.474Z] ERROR e2e/js-config/mesh.config.js:1 import { defineConfig } from '@graphql-mesh/compose-cli'; ^^^^^^ SyntaxError: Cannot use import statement outside a module at internalCompileFunction (node:internal/vm:76:18) at wrapSafe (node:internal/modules/cjs/loader:1283:20) at Module._compile (node:internal/modules/cjs/loader:1328:27) at Module._extensions..js (node:internal/modules/cjs/loader:1422:10) at Module.load (node:internal/modules/cjs/loader:1203:32) at Module._load (node:internal/modules/cjs/loader:1019:12) at ModuleWrap.<anonymous> (node:internal/modules/esm/translators:203:29) at ModuleJob.run (node:internal/modules/esm/module_job:195:25) at async ModuleLoader.import (node:internal/modules/esm/loader:337:24) at async run (file://node_modules/@graphql-mesh/compose-cli/esm/run.js:51:32) ❯ ChildProcess.<anonymous> internal/e2e/src/tenv.ts:915:11 Module Error: Exit code 1 seems to be an ES Module but shipped in a CommonJS package. You might want to create an issue to the package "Error: Exit code 1" asking them to ship the file in .mjs extension or add "type": "module" in their package.json. As a temporary workaround you can try to inline the package by updating your config: // vitest.config.js export default { test: { server: { deps: { inline: [ "Error: Exit code 1" ] } } } }

AssertionError: expected 1 to be 2 // Object.is equality - Expected + Received - 2 + 1 ❯ e2e/opentelemetry/opentelemetry.e2e.ts:318:30