Updating from 6.0.6 to 6.0.7 breaks Jest United test

[Philldomd]

Hi i have some issue updating office-addin-debugging and office-addin-dev-certs to version 6.0.7.

When running my CI pipeline i get jest errors like the one below.

Details:

    /home/runner/work/jitsi-outlook/jitsi-outlook/node_modules/@azure/logger/dist/browser/index.js:3
    import { createLoggerContext } from "@typespec/ts-http-runtime/internal/logger";
    ^^^^^^

    SyntaxError: Cannot use import statement outside a module

      10 |
      11 | import { Config } from "../src/models/Config";
    > 12 | import { OfficeMockObject } from "office-addin-mock";
         | ^
      13 | import { setLocationTest, setDataTest, addMeeting } from "../src/utils/OfficeCallHandler";
      14 | const { setLocation } = setLocationTest;
      15 | const { setData } = setDataTest;

      at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1314:40)
      at Object.<anonymous> (node_modules/@azure/monitor-opentelemetry/src/shared/logging/logger.ts:5:1)
      at Object.<anonymous> (node_modules/@azure/monitor-opentelemetry/src/shared/logging/index.ts:4:1)
      at Object.<anonymous> (node_modules/@azure/monitor-opentelemetry/src/shared/envConfig.ts:12:1)
      at Object.<anonymous> (node_modules/@azure/monitor-opentelemetry/src/shared/config.ts:18:1)
      at Object.<anonymous> (node_modules/@azure/monitor-opentelemetry/src/index.ts:9:1)
      at Object.<anonymous> (node_modules/office-addin-usage-data/node_modules/applicationinsights/src/main.ts:4:1)
      at Object.<anonymous> (node_modules/office-addin-usage-data/node_modules/applicationinsights/src/shim/telemetryClient.ts:25:1)
      at Object.<anonymous> (node_modules/office-addin-usage-data/node_modules/applicationinsights/src/index.ts:2:1)
      at Object.<anonymous> (node_modules/office-addin-usage-data/src/usageData.ts:4:1)
      at Object.<anonymous> (node_modules/office-addin-usage-data/src/main.ts:6:1)
      at Object.<anonymous> (node_modules/office-addin-manifest/src/addInTypes.ts:4:1)
      at Object.<anonymous> (node_modules/office-addin-manifest/src/main.ts:4:1)
      at Object.<anonymous> (node_modules/office-addin-mock/src/officeMockObject.ts:1:1)
      at Object.<anonymous> (node_modules/office-addin-mock/src/main.ts:4:1)
      at Object.require (__tests__/OfficeCallHandler.test.ts:12:1)

I have tried changing it to require and tested adding transformsIgnorePatterns for azure and typespec. But the microsoft package got an error that I could not work around.

How should I setup jest to work with the latest version?

Thanks in advance!

[Philldomd]

Hi,
I got it to work using:
transformIgnorePatterns: [],

in my jest.config.js

But that does not seem like the correct solution. The test compile time also increased. I have tried just Ignoring some modules, eg @Azure @typespec and this removes some errors. But i can not ignore @microsoft modules and got export error instead.

Any suggestions?

[millerds]

The library update included this new dependency which apparently uses ESM and jest is not configured to handle that. I think you are on the right track and just need to refine the pattern you are using. Have you tried the specific packages (and not the broad namespace of the packages)? Something like this (which target the offending packages) maybe:

transformIgnorePatterns: [ "node_modules/(?!(@azure/logger|@typespec/ts-http-runtime)/)"]

[Philldomd]

Tried with that ignore pattern but it does not work, added the rest of the faulty files but still got an error.

transformIgnorePatterns: ["node_modules/(?!@azure/logger|@azure/core-rest-pipeline|@azure/core-util|@azure/abort-controller|@azure/core-tracing|@azure/core-client|@azure/opentelemetry-instrumentation-azure-sdk|@typespec/ts-http-runtime)"]

C:\FKApps\repo\fk-ssh\jitsi-outlook\node_modules@microsoft\app-manifest\node_modules\strip-bom\index.js:1
export default function stripBom(string) {
^^^^^^

SyntaxError: Unexpected token 'export'

adding @microsoft in any form does not change the above error. How do we use jest testing on the latest version correctly?