[Template] Build test package failing in nightly runs

[jerryshia]

Template nightly test runs are failing with:

Error message:
configurationClient.spec.ts(5,37): error TS1479: The current file is a CommonJS module whose imports will produce 'require' calls; however, the referenced file is an ECMAScript module and cannot be imported with 'require'. Consider writing a dynamic 'import("../../src/index.js")' call instead.
To convert this file to an ECMAScript module, change its file extension to '.mts', or add the field "type": "module" to '/mnt/vss/_work/1/s/sdk/template/template/test/public/package.json'.
Error: Failed calling tsc -p .. Exit code: 2

##[error]Bash exited with code '2'.

For more details check here:
https://dev.azure.com/azure-sdk/internal/_build/results?buildId=3831833&view=results

[jeremymeng]

This only happens in min/max testing. Looks an known issue in vitest. We may need to upgrade the vitest dependency version since it is passing in normal runs.

"tsc -p ."

../../../../../common/temp/node_modules/.pnpm/@types[email protected]/node_modules/@types/chai/index.d.ts(1,1): error TS6200: Definitions of the following identifiers conflict with those in another file: Message, ObjectProperty, ChaiPlugin, AssertionArgs, Operator, OperatorComparable, AssertionError, chai
../../../../../common/temp/node_modules/.pnpm/@vitest[email protected]/node_modules/@vitest/expect/dist/chai.d.cts(16,1): error TS6200: Definitions of the following identifiers conflict with those in another file: Message, ObjectProperty, ChaiPlugin, AssertionArgs, Operator, OperatorComparable, AssertionError, chai
../../../../../common/temp/node_modules/.pnpm/vite-node@1.6.0_@types[email protected]/node_modules/vite-node/dist/index-O2IrwHKf.d.ts(87,14): error TS2304: Cannot find name 'WebSocket'.
../../../../../common/temp/node_modules/.pnpm/vite@5.2.12_@types[email protected]/node_modules/vite/types/customEvent.d.ts(27,14): error TS2304: Cannot find name 'WebSocket'.
../../../../../common/temp/node_modules/.pnpm/vite@5.2.12_@types[email protected]/node_modules/vite/types/importGlob.d.ts(38,11): error TS2304: Cannot find name 'Worker'.
../../../../../common/temp/node_modules/.pnpm/vitest@1.6.0_@types+node@18.19.33_@vitest[email protected]/node_modules/vitest/index.d.cts(1,15): error TS1479: The current file is a CommonJS module whose imports will produce 'require' calls; however, the referenced file is an ECMAScript module and cannot be imported with 'require'. Consider writing a dynamic 'import("./dist/index.js")' call instead.
configurationClient.spec.ts(5,37): error TS1479: The current file is a CommonJS module whose imports will produce 'require' calls; however, the referenced file is an ECMAScript module and cannot be imported with 'require'. Consider writing a dynamic 'import("../../src/index.js")' call instead.
To convert this file to an ECMAScript module, change its file extension to '.mts', or add the field "type": "module" to '/mnt/vss/_work/1/s/sdk/template/template/test/public/package.json'.

[xirzec]

@mpodwysocki maybe time to bump some minimum versions?

[jeremymeng]

The problem is actually because dependency-testing does not support newer testing via vitest yet. What it does is creating a package under test/public directory with the updated dependency versions, and build that package (tsc -p .), then run a command for integration test

azure-sdk-for-js/eng/tools/dependency-testing/templates/package.json

Line 12 in 02c1c78

"integration-test:node": "mocha --require tsx --require source-map-support/register --reporter mocha-multi-reporter.js --reporter-option output=test-results.xml --timeout 350000 --full-trace \"dist-esm/**/{,!(browser)/**/}*.spec.js\" --exit",

[jeremymeng]

pipeline has been green recently.