No error logs or debug/verbosity mode

[hashworks]

As far as I see, kutt offers no way to log any errors. It won't show any by default and there is no debug/verbosity mode – and if there is one it isn't documented.

For example, I had a working instance and suddenly I'm getting 500 errors on link creation. Opening old links, login, listing old links etc. works fine, only the link creation fails. However, there is no error output whatsoever besides the {"error":"An error occurred."} json output.

Basically I have to guess what's wrong, I think it's absolutely required that there is some kind of error logging.

[poeti8]

You can see the errors in Node.js console. So I guess what you mean is to send more info of what happened inside API response as well?

[hashworks]

There are no errors in my node console – at least not for that specific 500 error.

[vmwsree]

I ms tuck . . i mablet to create link.. not able to delete or update.. it shows error occurred.. no way to know whats going on

[kengher]

try running npm run dev to see if more error details show up.

[hashworks]

This is something that should be configurable over a configuration file, parameter or environment variable.

[ksingh7]

a parameter in .env to control debuging is much needed.