Replies: 4 comments 6 replies
-
|
Traffic analytics. It's the perfect place. I don't have it fully implemented yet, but I'm using it to ping a webhook with some anonymous data that I can use to watch usage patterns in the app. Since the rest of the request chain isn't dependent on the promise resolving I can send it and move on. Which pages are getting the most use? Which are getting the least? What time of day? Rate of new feature adoption? I'm thinking toward using that data to steer decisions, maybe allow A/B testing, and maybe using a hash of the userID to identify (anonymously) how the top users are using the application. I can also see possibilities for rate limiting and IP blacklisting if working with a cache. This is all a work in progress though. I'm just playing with it at this point. This is also for an internal application that won't see huge traffic volumes, at least not any time soon. |
Beta Was this translation helpful? Give feedback.
-
|
Sounds nice! |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
I'll jump in onto this thread, mostly because I want to hear from y'all if I'm doing something wrong! 😅 For my work-in-progress personal site, I use To use these locals on the client, I currently have a one-line I would really love to either move my hooks implementation to |
Beta Was this translation helpful? Give feedback.
-
|
Excellent! |
Beta Was this translation helpful? Give feedback.
-
|
Kind of looking in the same direction, but not sure why you must use |
Beta Was this translation helpful? Give feedback.
-
|
@binajmen Coding this "locals pass-through" is a bit boilerplate, and I wish it was automatic, but I'm not sure how many apps need this. One of my demo apps would be fine with it. But I'd think larger apps would still need to pass more data through, other than Even if sveltekit could automatically merge or pass /* hooks.js */
export const handle = async ({ event, resolve }) => {
event.locals.sensitive = JSON.parse(event.cookies.get('tokens') ?? null)
event.locals.non_sensitive = JSON.parse(event.cookies.get('user') ?? null)
const response = await resolve(event)
return response
}/* pretend this is magically happening behind the scenes, without a +layout.server.js file */
export const load = ({ locals }) => {
return {
/* we're now dangerously passing access tokens to the client-side */
...locals
}
} |
Beta Was this translation helpful? Give feedback.
-
|
I've got several hooks in sequence - request / performance logging, get access / id tokens from cookies, get user claims (from id token), etc. |
Beta Was this translation helpful? Give feedback.
-
|
I haven't used sequence yet, but I've seen it around! |
Beta Was this translation helpful? Give feedback.
-
|
Do you have public content you could share? As a SK newcomer, I'm struggling without proper tutorials/examples. It seems hooks will respond to my needs, but I'm not sure what is the impact mentioned by @Coretteket. Do you have also the same boilerplate-y issue? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I currently use this function in hooks.js to read browser cookies and set
event.locals.I'd love to learn how you're using
handle()to do rad shit.👇
Beta Was this translation helpful? Give feedback.
All reactions