No implicit any tsconfig cause issue with webpack config factory

Describe the Bug

I’m using a factory to generate my webpack browser & server configuration. My application tsconfig is in full strict mode. When running the builder for the browser, it seems that type annotations are removed before typescript compilation, causing errors related to implicit any types.

Minimal Reproduction

import { Configuration } from 'webpack';

export type ConfigFactory = ( baseConfig: Configuration, ngBuildConfig: any, ngBuildTarget: any ) => Configuration;

const factory: ConfigFactory = ( baseConfig, ngBuildConfig, ngBuildTarget ) => {
    // ...
}
export default factory;

Build fails with following message:

An unhandled exception occurred: ⨯ Unable to compile TypeScript:
configs/build/webpack.browser.config.ts:15:18 - error TS7006: Parameter 'baseConfig' implicitly has an 'any' type.

15 const factory = (baseConfig, ngBuildConfig, ngBuildTarget) => {
                    ~~~~~~~~~~
configs/build/webpack.browser.config.ts:15:30 - error TS7006: Parameter 'ngBuildConfig' implicitly has an 'any' type.

15 const factory = (baseConfig, ngBuildConfig, ngBuildTarget) => {
                                ~~~~~~~~~~~~~
configs/build/webpack.browser.config.ts:15:45 - error TS7006: Parameter 'ngBuildTarget' implicitly has an 'any' type.

15 const factory = (baseConfig, ngBuildConfig, ngBuildTarget) => {
                                               ~~~~~~~~~~~~~

See "/tmp/ng-lUATx4/angular-errors.log" for further details.

Expected Behavior

Build should work.

Screenshots

If applicable, add screenshots to help explain your problem.

Environment

Libs
- @angular/core version: 12.0.5
- @angular-devkit/build-angular version: 12.2.4
- @angular-builders/custom-webpack version: 12.1.1

For Tooling issues:
- Node version: 16.7.0
- Platform:  Fedora Linux x64

Others:

Additional Context

Seemms related to #749.

I’ve managed to fix the issue localy by editing https://github.com/just-jeb/angular-builders/blob/66b21aa50d31ae06ff4a3467851f068680f70cc9/packages/custom-webpack/src/utils.ts#L9-L17 and adding transpileOnly:

    require('ts-node').register({
      project: tsConfig,
      compilerOptions: {
        module: 'CommonJS',
        transpileOnly: true,
        types: [
          'node', // NOTE: `node` is added because users scripts can also use pure node's packages as webpack or others
        ],
      },
    });

Funny thing is that somehow, the server build is not impacted by this, but use the exact same factory signature.

[just-jeb]

Cool then, I’m graduating to stable release. Thanks for your insights that allowed to pinpoint the root cause quickly and of course for your contribution! @all-contributors please add @GerkinDev for code.

[just-jeb]

Thank you for your contribution, could we please confirm that the issue is solved for you in 12.1.2-beta.0?