Why isn't "export default" recommended in Angular? : <p>According to the <a href="https://www.typescriptlang.org/docs/handbook/modules.html" rel="noreferrer">Typescript documentation (section "Guidance for structuring modules")</a>:</p>

<blockquote>
  <p><em>If you’re only exporting a single class or function, use export
  default</em></p>
  
  <p>Just as “exporting near the top-level” reduces friction on your
  module’s consumers, so does introducing a default export. If a
  module’s primary purpose is to house one specific export, then you
  should consider exporting it as a default export. This makes both
  importing and actually using the import a little easier.</p>
</blockquote>

<p>Example:</p>

<pre><code>export default class SomeType {
  constructor() { ... }
}
</code></pre>

<p>In the <a href="https://angular.io/guide/architecture#components" rel="noreferrer">Angular documentation for components</a> (for example) one sees this:</p>

<pre><code>export class HeroListComponent implements OnInit {
  heroes: Hero[];
  selectedHero: Hero;

  constructor(private service: HeroService) { }

  ngOnInit() {
    this.heroes = this.service.getHeroes();
  }

  selectHero(hero: Hero) { this.selectedHero = hero; }
}
</code></pre>

<p>Generally, a component's or module's primary purpose is to house one specific export. So, is there a reason why Angular does not use or recommend using <code>export default</code>?</p>
