Providing a responseSerialzer is broken in v5.1

[davidda]

provideHttpCache({ responseSerializer(value) { return structuredClone(value); } }),

Providing a responseSerialzer will cause an error on startup in v5.1 (it has worked with the same code in v4.1).

Error: Invalid provider for the NgModule 'AppModule' - only instances of Provider and Type are allowed, got: [..., ..., ..., ..., ..., ..., ..., ..., ..., ..., ...]

The difference in the providers array is that the last entry is new which is apparently not correct for angular:

I am using Angular 20.

[drdreo]

I prepared a PR to fix the config only setup and added a new withConfig
Does the API for this look good? All 3 options are supported now.

provideHttpCache(
        {
          responseSerializer(value) {
            return structuredClone(value);
          }
        },
        withLocalStorage(),
      ),

----

provideHttpCache(
        withConfig({
          responseSerializer(value) {
            return structuredClone(value);
          }
        })
      ),

----

provideHttpCache(
        withLocalStorage(),
        withConfig({
          responseSerializer(value) {
            return structuredClone(value);
          }
        })
      ),

[davidda]

Looks good to me!