unit tests in jest fail with with latest build

[h4de5]

Hello, since yesterday evening our unit tests fail with the following message:

Test suite failed to run

    Jest encountered an unexpected token

    Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax.

    Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration.

    By default "node_modules" folder is ignored by transformers.

    Here's what you can do:
     • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it.
     • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript
     • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config.
     • If you need a custom transformation specify a "transform" option in your config.
     • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option.

    You'll find more details and examples of these config options in the docs:
    https://jestjs.io/docs/configuration
    For information about custom transformations, see:
    https://jestjs.io/docs/code-transformation

    Details:

    /azp/agent/_work/2/s/projects/test-wdk/node_modules/ngx-dropzone/fesm2020/ngx-dropzone.mjs:1
    ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){import * as i0 from '@angular/core';
                                                                                      ^^^^^^

    SyntaxError: Cannot use import statement outside a module

      at Runtime.createScriptFromCode (../../../../node_modules/jest-runtime/build/index.js:1728:14)

my guess it has something to do with this commit - https://github.com/peterfreeman/ngx-dropzone/commit/475e1969a97a6e07919f57458277627d67d5e0d8

I can't say if our test setup is somehow wrong or if this happends to everyone.

[h4de5]

also happens with a fresh nx workspace when using angular 12.

[peterfreeman]

Please try again using Angular 13 or switch to Ivy manually.

[wdanda]

FYI - version 3.0.0 doesn't seem to have this issue. Any other way around without forcing us to upgrade to Angular 13?

[felix-vaucourt]

Would also be interested if they is any workaround for people using Nx with Angular 12.x and ngx-dropzone: 3.1.0?

Jest encountered an unexpected token

    Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax.

    Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration.

    By default "node_modules" folder is ignored by transformers.

    Here's what you can do:
     • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it.
     • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config.
     • If you need a custom transformation specify a "transform" option in your config.
     • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option.

    You'll find more details and examples of these config options in the docs:
    https://jestjs.io/docs/configuration
    For information about custom transformations, see:
    https://jestjs.io/docs/code-transformation

/node_modules/ngx-dropzone/ngx-dropzone.d.ts:5
    export * from './public_api';
    ^^^^^^

    SyntaxError: Unexpected token 'export'