Open bowles-tyler-b opened 5 months ago
Have you found a solution to this problem?
Any plans or idea if/when this will be addressed?
I'm fully stuck because of this problem. Any idea of workaround, without downgrading angular to 17 ?
You could use skipLibCheck
as a workaround.
You could use
skipLibCheck
as a workaround.
Yes, I mentioned that in the original post. This is what we're doing for now, but it does of course reduce type safety.
Thank you ! I hadn't seen it. You've just saved my evening.
Yo can use npm i --legacy-peer-deps true
Command
other
Is this a regression?
The previous version in which this bug was not present was
17.3
Description
We have a custom builder for our angular project that has worked smoothly since Angular 8. We recently upgraded from Angular 15 to Angular 18 and tsc now throws errors when attempting to compile the builder. The errors thrown suggest changing the "moduleResolution" setting in tsconfig.builders.json, but each setting results in different downstream module resolution problems in the @angular-devkit/build-angular package.
Example error:
The full set of errors is pasted below.
I've attempted to change tsconfig.builders.json to use
But each of these yields a different set of errors.
Minimal Reproduction
Minimal reproduction repository: https://github.com/bowles-tyler-b/Angular8-failed-tsc-builder
After running "npm install", run the command "npm run compile" to reproduce the errors
Exception or Error
Your Environment
Anything else relevant?
Adding skipLibCheck to the ts compiler options will suppress the error; this is a workaround now, but reduces type safety in the custom builder.