Ndont think i can do that dynamically without making it annoying to me (like having to call
createLogger(request) to access it)
HOk, not entirely sure since it is
next-on-pageswell it is just a function
Ni could maybe initialize the logger with an export let
Nthen reassign in the middleware?
HThat could work?
NI'll try that
None worker shouldnt be reused across requests right?
UA worker can and will be reused
HIt can be, though it is generally tied to a single browser call
UYou should never use global scope for request level data (really in any serverless env)
N
Hoh wait
HYeah, that
Njust tryna add some per-request id to my logs
Uyou can use something like async local storage that you run per request that contains the request id
Nlogs are sent from the server
Nand are unfortunately not async
Nunless im misunderstanding
UYou can still use ALS
Nas in the import from async_hooks ?
Uhttps://nodejs.org/api/async_context.html
Log with ID is actually the example on the docs for async local storage
Log with ID is actually the example on the docs for async local storage
Nthought that was node
Ucloudflare supports node apis ALS being one of them
Nnice
Nill try that then
Nthanks
Nim assuming something like this
NNnever used als
Ndont think it works unfortunately
Nyeah als.getStore() returns undefined. probably because the middleware doesnt actually run the code, just can alter response/request
Nyeah unfortunately cant find a way to do it. ill use middleware to log requests overall though
Nplease tell me node:async_hooks work on pages
Nit works in dev mode, with turbopack
Nbut i use webpack for prod
Nand that does
⨯ Error: Cannot find module 'node:async_hooks'Nalready done
Nin my config
JALS is heavily depended on in next.js and next-on-pages
N
Nsoo why am i having issues importing it lmaoo
Jwhat is it for?
Nwell my next-on-pages prooject
Ni use it for logging
Ni removed the ignore plugin and it works in webpack dev i think?
Nyeah
Nbut it fails to build
NNwhat am i missing
