You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Maybe one could use the async hooks to introduce a useLogger method (similar to useEvent of #1546). This would allow to bound the logging output to the correct function invocation (see BrianRosamilia/azure-function-log-intercept#4 for background).
Logs
No response
The text was updated successfully, but these errors were encountered:
Environment
Linux
v16.16.0
3.0.0-rc.5
[email protected]
vite
alias
,nitro
,ssr
,meta
,css
,tailwindcss
,modules
,watch
,runtimeConfig
,serverHandlers
,storybook
,hooks
,vite
@nuxtjs/[email protected]
,@pinia/[email protected]
,./modules/storybook
,-runtime-compiler-module
-
Reproduction
Just have a function with
console.log("something")
.Describe the bug
Azure requires that logs are attached to a function run via
context.log
(instead of sayconsole.log
), see https://docs.microsoft.com/en-us/azure/azure-functions/functions-reference-node?tabs=v2-v3-v4-export%2Cv2-v3-v4-done%2Cv2%2Cv2-log-custom-telemetry%2Cv2-accessing-request-and-response%2Cwindows-setting-the-node-version#write-trace-output-to-logs.But as far as I can see there is no wrapper to provide framework independent logging nor a way to get the azure context from within nitro/nuxt.
Additional context
Maybe one could use the async hooks to introduce a
useLogger
method (similar touseEvent
of #1546). This would allow to bound the logging output to the correct function invocation (see BrianRosamilia/azure-function-log-intercept#4 for background).Logs
No response
The text was updated successfully, but these errors were encountered: