JeB
> maybe a custom test suite in shell-script with tsc? Yeah, e2e test are probably the way to go. We already have custom shell scripts for e2e tests, for example...
Just to make it clear: is it a bug or an enhancement? We have examples with both `csj` and `esm` which are working for `custom-webpack` and `custom-esbuild` builders.
Closing until it's unblocked
From a quick glance I can't see anything in the builder's flow that can impact the cache. I think the sheer fact that you're using this plugin and the way...
I wonder if that's an issue with the builder or [jest-preset-angular](https://github.com/thymikee/jest-preset-angular). Could you try to reproduce it with clean `jest-preset-angular` setup (without the `@angular-builders`) in order to confirm it is...
WIP, probably will release in the coming week.
You're welcome to try out `v18` beta under `@next` tag.
Not sure how I can help here honestly. The error seems to be coming from TS, but it complains about non-existent module. I'd try to isolate it: try to run...
Hi, I am assuming you tried it without the custom webpack config and it worked? We're gonna need a repo with minimal reproduction in order to address this issue.
Most likely you have some issue with dependencies (also known as dependency hell). You can check it by `yarn why` command (or its NPM alternative). Try to delete the lock...