I'm using Transloco with SSR, and I’ve noticed a couple of behaviors that I’m not sure are expected. I’d appreciate any clarification.

1. Why is my custom loader triggered multiple times during SSR on the same page and only if there is directive present?
   When rendering a single page with SSR, I see multiple console.log('loaded') entries from my TranslocoLoader. Here's a simplified version of the loader:

   import { ConfigBaseService } from './config-base.service';
   import { Injectable } from '@angular/core';
   import { TranslocoLoader } from '@jsverse/transloco';
   import { HttpClient } from '@angular/common/http';
   
   @Injectable({ 
     providedIn: 'root' 
   })
   export class SpiderlyTranslocoLoader implements TranslocoLoader {
     constructor(
       private http: HttpClient,
       private config: ConfigBaseService,
     ) {}
   
     getTranslation(lang: string) {
       console.log('loaded')
       return this.http.get(`${this.config.frontendUrl}/assets/i18n/${lang}.json`);
     }
   
   }

   I would expect it to load once per language, but I’m seeing it multiple times just for one SSR render.

   Config:

   provideTransloco({
     config: {
       availableLangs: [
         'en', 'en.generated',
       ],
       defaultLang: 'en',
       fallbackLang: 'en.generated',
       failedRetries: 0,
       missingHandler: {
         useFallbackTranslation: true,
         logMissingKey: false,
       },
       reRenderOnLangChange: true,
     },
     loader: SpiderlyTranslocoLoader
   }),

2. Why does the loader get triggered only when a directive is present in the HTML template?
   If I remove the directive from the component templates, the loader doesn’t log anything and I can't get translations via TranslocoService. I assume this is due to some lazy loading of translations, but I'd like to confirm if this is how it’s supposed to behave.

   With just putting this line of code inside app.component.html the language gets loaded:

   <ng-container *transloco="let t"></ng-container>