CLI overhaul brainstorming

[jkelleyrtp]

We'd like to overhaul the CLI to be more productive and more helpful!

Here are the notes from the brainstorming session we had in Feb 7 office hours.

CLI Tooling Brainstorming

---

• TUI or GUI
  • orrr built-in to window
  • basically desktop
• Missing features
• Features for v0.1
  • Logging (both general and structured per component)
  • Reload button
  • Make naming consistent with cargo
    • cargo run - dx run
    • cargo init - dx init
    • cargo new - dx new
    • cargo watch?
  • dx serve --platform is automatic
  • dx config
  • Performance metrics (frequent-rerenders, long renders, long async tasks)
  • Interactive configuration
  • Built-in guides
  • Cargo.toml linting
  • Config flags based on the project
  • More templates
    • Setting up directories and cfg-flags for you
  • Profiles?
    • Auto
  • wasm-opt (and other optimizations)
  • assets (and opt-levels)
  • Big reload button
  • talisman (gopher equivalent)
  • Plugin manager
    • Plugins
    • Tailwind plugin
    • SCSS/SASS plugin
    • Scoped CSS
    • Minify/obfuscate
    • Installing plugins from git
  • Installer/updater
  • dx migrate (0.4 -0.5 or any version)
  • reverse proxy/tunnel/ssh share your running app to other people
    • in theory works other renderers
  • Refactors (IDE integration)
    • convert rsx into a component
    • showing reactivity captures
    • hover lens for previewing components
    • Hover lens for running/serving project
    • Logs populated into lenses (like code ninja)
  • Storybook
  • Fix fmt with 0.5
    • Loops/for/match
• Longer-term features
  • server_fn profile (and postman-like testing)
  • Deploy
  • Infrastructure-as-code stuff
  • Finding #[component]
  • Mocking #[component]
  • Testing (sweet integration?)
  • Component screenshots
  • using the CLI in CI for CI/CD/testing/snapshots/metrics/etc
  • Walking through the app for you and running into edge cases
  • open-api spec generation