failure due to multiple versions of transitive dependencies from npm and workspace

[jeremymeng]

Our tests pull in multiple versions of @azure/core-lro and we are using the following config to ensure they are not optimized into one single chunk in browser bundle.

import viteConfig from "../../../vitest.browser.shared.config.ts";

import { defineConfig, mergeConfig } from "vitest/config";

export default mergeConfig(
  viteConfig,
  defineConfig({
    test: {
      globalSetup: ["test/global-setup.ts"],
    },
    optimizeDeps: {
      exclude: ["@azure/core-lro"],
      include: [
        // v2
        "@azure/arm-authorization > @azure/core-lro",
        "@azure/arm-compute > @azure/core-lro",
        "@azure/arm-resources > @azure/core-lro",
        "@azure/keyvault-keys > @azure/core-lro",
        // v3
        "@azure/arm-batch > @azure/core-lro",
        "@azure/arm-keyvault > @azure/core-lro",
      ],
    },
  }),
);

However, vitest throws an error during the test probing phase before any tests are executed. It seems to be related to how vite cache modules. In this case even though the import of deserializeState is from @azure/core-lro v3, because the cached version is v2 which doesn't have that export and it tries to check imports from the cached version thus failed.

Any workaround?

[vitest]  RUN  v4.1.0 C:/git/jsmain/sdk/batch/batch-rest
[vitest]
[vitest] No test files found, exiting with code 1
[vitest]
[vitest]
[vitest]  chromium
[vitest]
[vitest] include: dist-test/**/*.spec.js
[vitest] exclude:  dist-test/**/node/*.spec.js, dist-test/snippets.spec.js, dist-test/integration/**/*.spec.js, dist-test/stress/**/*.js
[vitest]
[vitest] JUNIT report written to C:/git/jsmain/sdk/batch/batch-rest/test-results.browser.xml
[vitest]
[vitest] ⎯⎯⎯⎯⎯⎯ Unhandled Error ⎯⎯⎯⎯⎯⎯⎯
[vitest] SyntaxError: [vite] The requested module '@azure/core-lro' does not provide an export named 'deserializeState'
[vitest]  ❯ analyzeImportedModDifference ../../../node_modules/.pnpm/vite@7.3.1_@types+node@20.19.37_tsx@4.21.0_yaml@2.8.3/node_modules/vite/dist/node/module-runner.js:459:36
[vitest]  ❯ ServerModuleRunner.processImport ../../../node_modules/.pnpm/vite@7.3.1_@types+node@20.19.37_tsx@4.21.0_yaml@2.8.3/node_modules/vite/dist/node/module-runner.js:1028:54
[vitest]  ❯ ServerModuleRunner.cachedRequest ../../../node_modules/.pnpm/vite@7.3.1_@types+node@20.19.37_tsx@4.21.0_yaml@2.8.3/node_modules/vite/dist/node/module-runner.js:1051:33

[hi-ogawa]

The unhandled error looks like a server side runtime error, so it doesn't match with your problem statement. Would be nice to have a fuller picture of config or reproduction to understand the issue. For example, is it possible that global-setup.ts pulls in your azure package and that's hitting the issue?

[jeremymeng]

For example, is it possible that global-setup.ts pulls in your azure package and that's hitting the issue?

@hi-ogawa yes you are right! it's the global-setup.ts that pulls in @azure/arm-batch which should have used v3 of @azure/core-lro (linked workspace version) but was getting v2 from cache.

[jeremymeng]

I was thinking about making a simplified repro project, but here's the steps using our mono repo

1. git clone https://github.com/Azure/azure-sdk-for-js
2. git checkout fcf086e7ab8293d98418e0e1c102255acdc1b4e9
3. pnpm install
4. pushd sdk/batch/batch-rest
5. npx turbo build --token 1
6. npm run test:browser

maybe it's an issue in vite?