Should this module be split from the riot core?

[GianlucaGuarini]

I am still not sure whether this module should still be included in the main riot repo or just installable via npm riot-cli. I would like to know your opinion on this topic

cc @tipiirai @cognitom @aMarCruz @rsbondi

[cognitom]

Both is reasonable for me. Basically I have no preference about it, but I like the idea riot-cli. It looks cleaner.

[aMarCruz]

Sorry @GianlucaGuarini , having very busy days, but I'm back :)
I think this is part of the compiler, and should be with him.

[GianlucaGuarini]

@aMarCruz welcome back.. I am happy to receive your feedback again!
My idea was to rely on the riot-compiler but I would avoid that riot and riot-compiler load these dependencies.
Let's use them just in this repo

[aMarCruz]

ok, why not integrate riot-cli in riot-compiler ? I'm not sure, but I think is the standard way in npm packages.

[GianlucaGuarini]

@aMarCruz this would mean that anytime someone will install the riot-compiler in a project he/she will load and install dependencies to compile the tags via command line even if he/she doesn't need it. I would prefer to split them also to get a cleaner unit test (target tags and expected fixtures), but that's more my opinion. I would like to know also what @tipiirai thinks about this

[tipiirai]

I think anything goes as long as users can compile riot tags after the npm install riot command.