New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hard to distinguish warnings and errors #3778
Comments
You might try |
I'm seeing this as output from |
Yes, as the author of |
Look at this, psa does already seem to be the default for spago 😳: $ spago --help
…
-P,--no-psa Don't build with `psa`, but use `purs`
… But it doesn't seem to be used 🤔 |
Maybe it needs to be globally installed? |
I think it needs to be on your PATH. |
Ah yes, either spago and purescript-psa are both installed locally or both globally, but the global spago doesn't pick up a local purescript-psa. Should maybe be implemented. Tools like webpack use the local version if they find one iirc. |
For anyone reading this, if you need to use spago with psa, simply install both globally. They will work together automatically. |
At the moment it's really hard to visually distinguish warnings from errors:
It would be cool if the difference was more prominent. E.g. through using different colors and adding ASCII art for sectioning the output.
Maybe something like this (pseudocode for coloring):
What do you think?
The text was updated successfully, but these errors were encountered: