TypeError: Cannot read properties of undefined (reading 'start')
ujjwalsoni1707 opened this issue · comments
Need help in debugging the issue.
When running "dev-tool run test:vitest", I am facing the following error in cosmosdb js sdk.
> "dev-tool run test:vitest"
[test-info] ===TEST_MODE="undefined"===
[test-proxy] Image tag obtained from the powershell script => 1.0.0-dev.20250221.1
[test-proxy] Test proxy executable already exists at C:\Users\soniujjwal\AppData\Local\azsdk-dev-tool\Cache\1.0.0-dev.20250221.1\Azure.Sdk.Tools.TestProxy.exe, not downloading it.
[vitest] Testing types with tsc and vue-tsc is an experimental feature.
[vitest] Breaking changes might not follow SemVer, please pin Vitest's version when using it.
[vitest]
[vitest] RUN v3.0.9 C:/Users/soniujjwal/Documents/workRepo/azure-sdk-for-js/sdk/cosmosdb/cosmos
[vitest]
[vitest]
[vitest] ⎯⎯⎯⎯ Unhandled Rejection ⎯⎯⎯⎯⎯
[vitest] TypeError: Cannot read properties of undefined (reading 'start')
[vitest] ❯ Object.CallExpression ../../../common/temp/node_modules/.pnpm/vitest@3.0.9_@types+debug@4.1.12_@types+node@18.19.80_@vitest+browser@3.0.9_msw@2.7.3_@types+_obow6jd3n23uckwufupy6j4r2e/node_modules/vitest/dist/chunks/typechecker.BlF3eHsb.js:431:130
[vitest] ❯ c ../../../common/temp/node_modules/.pnpm/vitest@3.0.9_@types+debug@4.1.12_@types+node@18.19.80_@vitest+browser@3.0.9_msw@2.7.3_@types+_obow6jd3n23uckwufupy6j4r2e/node_modules/vitest/dist/chunks/typechecker.BlF3eHsb.js:87:41
[vitest] ❯ Object.skipThrough ../../../common/temp/node_modules/.pnpm/vitest@3.0.9_@types+debug@4.1.12_@types+node@18.19.80_@vitest+browser@3.0.9_msw@2.7.3_@types+_obow6jd3n23uckwufupy6j4r2e/node_modules/vitest/dist/chunks/typechecker.BlF3eHsb.js:92:37
[vitest] ❯ c ../../../common/temp/node_modules/.pnpm/vitest@3.0.9_@types+debug@4.1.12_@types+node@18.19.80_@vitest+browser@3.0.9_msw@2.7.3_@types+_obow6jd3n23uckwufupy6j4r2e/node_modules/vitest/dist/chunks/typechecker.BlF3eHsb.js:86:22
[vitest] ❯ base.ReturnStatement.base.YieldExpression.base.AwaitExpression ../../../common/temp/node_modules/.pnpm/vitest@3.0.9_@types+debug@4.1.12_@types+node@18.19.80_@vitest+browser@3.0.9_msw@2.7.3_@types+_obow6jd3n23uckwufupy6j4r2e/node_modules/vitest/dist/chunks/typechecker.BlF3eHsb.js:140:24
[vitest] ❯ c ../../../common/temp/node_modules/.pnpm/vitest@3.0.9_@types+debug@4.1.12_@types+node@18.19.80_@vitest+browser@3.0.9_msw@2.7.3_@types+_obow6jd3n23uckwufupy6j4r2e/node_modules/vitest/dist/chunks/typechecker.BlF3eHsb.js:86:22
[vitest] ❯ Object.skipThrough ../../../common/temp/node_modules/.pnpm/vitest@3.0.9_@types+debug@4.1.12_@types+node@18.19.80_@vitest+browser@3.0.9_msw@2.7.3_@types+_obow6jd3n23uckwufupy6j4r2e/node_modules/vitest/dist/chunks/typechecker.BlF3eHsb.js:92:37
[vitest] ❯ c ../../../common/temp/node_modules/.pnpm/vitest@3.0.9_@types+debug@4.1.12_@types+node@18.19.80_@vitest+browser@3.0.9_msw@2.7.3_@types+_obow6jd3n23uckwufupy6j4r2e/node_modules/vitest/dist/chunks/typechecker.BlF3eHsb.js:86:22
[vitest] ❯ base.ExpressionStatement.base.ParenthesizedExpression.base.ChainExpression ../../../common/temp/node_modules/.pnpm/vitest@3.0.9_@types+debug@4.1.12_@types+node@18.19.80_@vitest+browser@3.0.9_msw@2.7.3_@types+_obow6jd3n23uckwufupy6j4r2e/node_modules/vitest/dist/chunks/typechecker.BlF3eHsb.js:110:35
[vitest] ❯ c ../../../common/temp/node_modules/.pnpm/vitest@3.0.9_@types+debug@4.1.12_@types+node@18.19.80_@vitest+browser@3.0.9_msw@2.7.3_@types+_obow6jd3n23uckwufupy6j4r2e/node_modules/vitest/dist/chunks/typechecker.BlF3eHsb.js:86:22
[vitest]
[vitest]
[vitest]
[vitest]
[vitest] vitest exited with code 1
Trace: [Internal Error]
at <anonymous> (c:\Users\soniujjwal\Documents\workRepo\azure-sdk-for-js\common\tools\dev-tool\src\index.ts:13:11)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
Error: Failed calling dev-tool run test:vitest. Exit code: 255`
@ujjwalsoni1707 do you have a branch that we can investigate?
I assume this is related to ESM/vitest migration? /cc @mpodwysocki
@jeremymeng yes I am engaging with the team right now.