[Bug]: latest zone.js v0.13.2 is causing import error about jest-preset-angular

[alan-agius4]

Looks like jest-preset-angular is using deep imports, instead of consuming the “public” entry-points

IE

jest-preset-angular/setup-jest.mjs

Line 1 in 65a848a

import 'zone.js/fesm2015/zone-testing-bundle.min.js';

Instead of something like;

import 'zone.js/testing';

That being said, it’s a bit unclear how the zone-testing-bundle should be consumed.

I think as an interim for v0.13.x we could re-allow deep imports and remove them in v0.14.x.

//cc @JiaLiPassion.

[alan-agius4]

zone.js version 0.13.3 has been just released which should get around this issue.

Deep imports will eventually no longer be allowed from zone.js version 0.14.0.

The proper way to use zone testing is the following:

import "zone.js";
import "zone.js/testing";

[timothee-dhenain-zenika]

It's still an issue with the latest version of Angular (17.0.2), all of our tests are broken as well after upgrading. This is our following package.json:

"dependencies": {
    "@angular/animations": "~17.0.2",
    "@angular/common": "~17.0.2",
    "@angular/compiler": "~17.0.2",
    "@angular/core": "~17.0.2",
    "@angular/forms": "~17.0.2",
    "@angular/localize": "~17.0.2",
    "@angular/platform-browser": "~17.0.2",
    "@angular/platform-browser-dynamic": "~17.0.2",
    "@angular/router": "~17.0.2",
    "@angular/service-worker": "~17.0.2",
    "@ngrx/effects": "~16.3.0",
    "@ngrx/store": "~16.3.0",
    "rxjs": "~7.8.1",
    "tslib": "~2.6.1",
    "zone.js": "~0.14.2"
  },
  "devDependencies": {
    "@angular-builders/jest": "~16.0.0",
    "@angular-devkit/build-angular": "~17.0.0",
    "@angular-eslint/builder": "~17.0.1",
    "@angular-eslint/eslint-plugin": "~17.0.1",
    "@angular-eslint/eslint-plugin-template": "~17.0.1",
    "@angular-eslint/schematics": "~17.0.1",
    "@angular-eslint/template-parser": "~17.0.1",
    "@angular/cli": "~17.0.0",
    "@angular/compiler-cli": "~17.0.2",
    "@types/jest": "~29.5.3",
    "jest": "~29.6.2",
    "jest-canvas-mock": "~2.5.2",
    "jest-preset-angular": "~13.1.3",
    "typescript": "~5.2.2",
  }

And our angular.json configuration:

"test": {
        "builder": "@angular-builders/jest:run",
        "options": {
          "tsConfig": "tsconfig.spec.json",
          "configPath": "jest.config.js",
          "assets": ["src/favicon.ico", "src/assets"],
          "styles": ["src/styles.scss"],
          "scripts": []
        }
      },

FAIL src/app/shared/components/features/search/components/search-companies/components/search-companies-by-id/pipe/search-companies-by-id-placeholder.pipe.spec.ts
● Test suite failed to run

Cannot find module 'zone.js/bundles/zone-testing-bundle.umd' from 'node_modules/@angular-builders/jest/node_modules/jest-preset-angular/setup-jest.js'

Require stack:
  node_modules/@angular-builders/jest/node_modules/jest-preset-angular/setup-jest.js
  node_modules/@angular-builders/jest/dist/jest-config/setup.js

[Tallyb]

#2162

[ghiscoding]

indeed the temp fix seems to work now, but I guess it's probably better to keep this issue open until a proper fix is implemented. Thanks for the info and quick turnaround about the Angular upstream :)

[alexus85]

updating to the latest version (13.1.4) seem to have solved the issue for me.

[karoldydo]

Update package "@angular-builders/jest": "^17.0.0" solve the problem.

[ocombe]

I have the same error, everything was working fine last night, and now all of my tests are broken https://github.com/teambit/envs-health-status/actions/runs/6153094762/job/16696392467

[ocombe]

zone.js/bundles/zone-testing-bundle.umd has been renamed zone.js/bundles/zone-testing.umd in the last package

[Sebastian-G]

Also occurs for new angular builders:

       "test": {
          "builder": "@angular-builders/jest:run",
          "options": {
            "tsConfig": "tsconfig.spec.json",
            "polyfills": ["zone.js", "zone.js/testing"]
          }
        }

fixed by enforcing zone.js version 0.13.1

[SmailHammour]

Since Angular v17 will require Zone.js version 0.14.x or later, this is still an issue?