Is it necessary to redundantly specify components ?

[pushqrdx]

Well, Svelte so far is pretty darn smooth (from me reading the docs) but somethings are plain weird. I mean why would it be necessary to redundantly do this

<!-- App.html -->
<h1>Hello {{$name}}!</h1>
<Greeting/>

<script>
  import Greeting from './Greeting.html';
  export default {
    components: { Greeting } //WHY THIS.
  };
</script>

Isn't the import and the element tag fair enough reasons for the compiler to assume that it's a currently used component ?...

[Conduitry]

There's already some discussion about how to make this more succinct in #1038.

Svelte compiles each component separately (and then they get bundled together later), so it can't actually tell whether a given import is intended as a component. And, similarly if you used a component without importing it, the bundler would not know where the component is supposed to come from.

[pushqrdx]

Well, It can tell by Convention, Let's say we have a <Greeting/> Tag. If we already are importing Greeting, the compiler, by convention, should assume that it's a component.

[arxpoetica]

Closing this issue in favor of continuing the discussion on duplicate ticket #1038. @pushqrdx my convenient answer ;) is to offport such "magic" to a bundler like Rollup or WebPack, but let's take the discussion over to the already-open ticket. :)