CLI

[brillout]

Note

This includes brainstorming ideas (long-term vision). A lot is out-of-scope for the MVP: we can only implement the MVP-relevant parts.

I suggest that running $ framework does the following:

• Ensure The background process that runs the localhost dashboard (e.g. localhost:4200) is running
• Runs background jobs
• Prints the list of commands (just convenience commands like framework run [prompt], framework logs, ... — not important since the UI already implements all features)
• Prints the CLI version
  • [Only if trivial to implement] Show whether the version is up-to-date (by using $ npm info).
    • Should be async (show static info first, then await npm server and show "up-to-date" label)
    • The CLI regularly auto-updates itself
    • Also show (✅ auto-update enabled).