-
-
Notifications
You must be signed in to change notification settings - Fork 345
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
New hook onLog()
#1438
Labels
Comments
Closed
Sweet!! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Enabling:
express-vike
). (The current recommendation usespageContext.errorWhileRendering
.)Other condiserations:
interceptLogs
would be neat for easily track errors in an exhaustive fashion (also for manipulating logs coming from other tools). With fine grain control over what is intercepted:interceptLogs: boolean | { client?: boolean, server?: boolean } | { logs: { client: boolean, server: boolean }, errors: { client: boolean, server: boolean } }
.See also:
Instead of having three different hooks (
onLog()
/onClientLog()
/onServerLog()
), a consideration is to have+onLog.js
/+onLog.server.js
/+onLog.client.js
. (The suffixes would automatically change the env of the + file.)The text was updated successfully, but these errors were encountered: