More explanations about the composer.json given as example

[fabarea]

On the README.md file, a composer.json file is given as example. Though, I am not sure to understand well the reason why to add lw/typo3-installers as requirement and the composer.lightwerk.com repository in the composer file. Doesn't it work without as demoed on http://composer.lightwerk.com/? What would be the benefit?

[AndreasA]

Actually with typo3 6.2 I do not think one should use the lightwerk composer.json at all for an extension. That only works good for the lightwerk typo3-ter downloads but the extension itself should use "type": "typo3-cms-extension" and no require at all.
That will use the "composer/installers" (which should be loaded first without any additional require) and also install to the typo3conf/ext directory.
Furthermore, that way typo3 recognizes the extension as a typo3 extension and uses the directoryname as extension key as before and not vendorname.extkey which would create problems if you somewhere try to access the directory name as extension key.

Furthermore, for composer one should add a replace with only the extension key, that way if I were to define a extension as requirement somewhere composer would accept it.