It appears that error.js is still allowing status 500 errors to leak their actual error out to the user interface, despite the middleware being in place to catch this the same way it should catch a 404.
Not exactly sure why this is, because as far as I can tell we are using the recommended method.
It appears that
error.jsis still allowing status 500 errors to leak their actual error out to the user interface, despite the middleware being in place to catch this the same way it should catch a 404.Not exactly sure why this is, because as far as I can tell we are using the recommended method.
@keawade Any thoughts?