CLI interface

[mikabytes]

For this version, the CLI interface should handle this (at a minimum)

• Initiate a new Tiden project
• Create stream
• Create nano
• Create namespace
• Create elements components
• Moving/Removing of all above to be done in Rename/remove CLI commands #36

[mikabytes]

It would be pretty awesome if nanos, connects, and Element demos could automatically figure out what props are available on an Element. This way a lot of code could be auto-generated when creating things. I find a lot of my time is actually spent on just setting up the basic boilerplate.

The most simple and obvious way would be to enforce components to declare what props they are using. This comes with some cons though:

• we're limiting the use of alternative mechanisms of creating Components (Tiden might ship with HotHaunted support out-of-box, but it should be possible to use whatever you want, otherwise we turn into yet another framework).
• Actual use and declared use will definitely go out of sync from time to time. This is annoying, especially when teammates make changes and then CLI/UI is found to be broken weeks later.

An alternate idea might be to use Element demos as the de-facto truth. We have the ability to check what props are actually being set on the element. So the tool could sniff what the demos do and replicate that. This also encourages users to write complete demos, which I think is an excellent bonus.