Move component methods out of constructor

[PaulBGD]

Instead of doing this.fire =, this.get =, etc we should move the component methods out of the constructor.

[Rich-Harris]

I'm not sure that's strictly true – with class, various private variables (callbacks, observers, mainFragment etc) would become properties of this, at which point you can't minify them (though the difference is small after gzip). And because a lot of people would still need to transpile class syntax, you'd be introducing both build time and run time overhead.

That said, there are some benefits to moving component methods out of the constructor, particularly when we get round to externalising methods and helpers that can be shared between components.

[PaulBGD]

That works too, I'm just complaining because closure-compiler doesn't seem to like assigning methods to this.

[Swatinem]

There is already work towards this goal in #37, in the first place for the generated template code.

[PaulBGD]

@Swatinem Yeah, I guess when I changed the direction of the issue it made it a duplicate.