Support Angular 13

[DavidDudson]

Is your feature request related to a problem? Please describe.

Due to this plugin depending on an old @angular version, it fails to work with angular 13. I believe this is due to a typescript version change. causing the legacy @ngtools/webpack plugin to no longer work

/webpack/src/ivy/plugin.js is an ES module file as it is a .js file whose nearest parent package.json contains "type": "module" which defines all .js files in that package scope as ES modules.
Instead rename index.js to end in .cjs, change the requiring code to use import(), or remove "type": "module" from ../package.json

Describe the solution you'd like

A new major version of @angular-builders/jest and @angular-builders/custom-webpack both supporting angular 13

Additional context
There is a workaround. Adding:

  "resolutions": {
    "@angular/compiler": "13.0.0",
    "@angular/cli": "13.0.0",
    "@angular-devkit/build-angular": "~13.0.0"
    }

to package json and this works fine.

[abadakhshan]

@DavidDudson

You could find a solution here #1050

[just-jeb]

This PR will resolve it. You're not supposed to use Angular Builders 12 with Angular 13 (see the docs). I expect the PR to be merged in the next few days, please be patient 😄

[DavidDudson]

angular-builders-jest is also a dep of ours, they just released a prerelease version (11.X) which seems to work perfectly for us!

Thanks for the quick PR <3

[just-jeb]

You're welcome to check out the preview version 13.0.0-beta.0 (under the next tag).

[gabynevada]

@just-jeb I get the following error when trying ng build using the beta

Error: Cannot find module 'webpack-sources'

After installing webpack-sources package everything works as expected, including the new angular cache.

Thanks!

[just-jeb]

@gabynevada Hey, I suspect it's a broken lock file. Try to remove it and regenerate again (remove the webpack-sources from direct dependencies before regeneration).

[DavidDudson]

@just-jeb that beta version works perfectly. I think this is close to record timing that all our dependencies have been working (even if they are still all pre-release) after an angular upgrade, thank you very much! It means we can thoroughly test our applications while waiting for full releases.

[gabynevada]

@just-jeb Perfect! That was the issue.

Thanks! All working great

[just-jeb]

@DavidDudson doing my best 😄 The stable release won't take long, I'm working on integrating a new builder, then a few minor doc updates and we're good to go.
Unless you discover any issues of course.

[just-jeb]

Aaaand v13 is officially out.