Referencing a variable that does not exist can cause an entire fastify exception about point-of-view HOT 9 CLOSED

@mcollina ok. I just created the PR33.
Due to lack of time now it's without tests but I'll add them in a few days.
As always comments and suggestions are welcome :-) ... thanks for now. Bye

from point-of-view.

@smartiniOnGitHub Thank you very much.

from point-of-view.

I think fastify is doing the correct thing. If your application throw it is better to crash, otherwise you are going to leak memory.

What we can do is to catch and send that to the error handler... the user will see a 500. Would this be bettere?

from point-of-view.

So how do I catch this exception, it seems to be in the form of Plug-ins, in the plug-in callback? or where?

from point-of-view.

very likely we would have to add it in this library.

Would you mind sending a PR?

from point-of-view.

Hi all, I just started an implementation for this (I have the same problem even when an EJS include file is missing and I need to have it fixed), I hope to push something for a PR soon ...

from point-of-view.

To speedup development cycles in some projects I use nodemon ... if I'd add it in dev dependencies here and add a custom npm command to have an hot-reloadable dev server ?
@mcollina What do you think ?

from point-of-view.

The best way to develop this is via unit tests, not with a “hot-reloadable dev server”, I’m kind of -1. There is no need to add this to package.json either as you can use it from a global installation.

from point-of-view.

@mcollina This could be closed now (just merged) ... thanks a lot.

from point-of-view.