search

wasp-lang / wasp

The fastest way to develop full-stack web apps with React & Node.js.
https://wasp-lang.dev
MIT License
12.79k stars 1.14k forks source link

Better show Wasp development information: CLI Powerline or browser dev tooling or Wasp Studio #250

Open Martinsos opened 3 years ago

Martinsos commented 3 years ago

Coming from #207.

Idea is to provide some kind of nice progress indicator in Wasp CLI. Idea: at the bottom of the screen, there could be a "readonly" line that shows special "wasp status" -> it would be showing current status of the wasp start. So while we are printing stuff, that line would always be there. While packages are installing, it could be showing smth like [1/2] Installing web-app and server .... Then, once that is done, it could show something like All good - wasp is running in dev mode!, and if at some point server crashes or smth like that, it could be showing Server broken - fix it. It could also be showing stuff like schema is out of sync with db - run 'wasp db migrate-dev' to sync it.

There is cool package on npm that might server as inspiration https://www.npmjs.com/package/ora . This is however something we should be doing in Haskell!

turbodami commented 3 years ago

Cool one!

Martinsos commented 10 months ago

A spin on this: When developing wasp app, in your browser's tab, you would see a small something that would be showing the status of wasp start -> are there any warnings or errors. It could be a small circle, that is green if all ok, orange if warnings, red if errors. Maybe you could move it around if it is bothering you. It could start spinning when wasp start is compiling. This would help with the fact that Wasp might print a warning in the CLI, but you won't see it! Or maybe this could even be shown in your editor? But that would be editor dependent.

Martinsos commented 1 month ago

Alternative is to not have a CLI powerline, but instead make all this part of Wasp Studio (client/server/db logs, warnings and errors, ...).