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
I was about to create a bug report for this, but well, had already 2 reports for other topics and both appeared to be a misconfiguration on my side, so I did not want to annoy contributors with false flags.
The thing is, I am currently trying to perform a migration to nuxt bridge, and some of my callbacks defined in the hooks section, stopped tripping. In my case it is actually the other way round: I have just a couple tripping, the rest is not.
So my scenario is to start a server and request a page from a default template. In this case I only get console messages for listen when server starts and ready when app initializes. No hook related to rendering is triggered and I have no idea why. For the same code base (excluding of course changes made for nuxt bridge migration) in nuxt 2 at least render:routeDone was working.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello community,
I was about to create a bug report for this, but well, had already 2 reports for other topics and both appeared to be a misconfiguration on my side, so I did not want to annoy contributors with false flags.
The thing is, I am currently trying to perform a migration to nuxt bridge, and some of my callbacks defined in the hooks section, stopped tripping. In my case it is actually the other way round: I have just a couple tripping, the rest is not.
My example nuxt.config.js would look like that
I cut off everything, that might be irrelevant.
So my scenario is to start a server and request a page from a default template. In this case I only get console messages for
listen
when server starts andready
when app initializes. No hook related to rendering is triggered and I have no idea why. For the same code base (excluding of course changes made for nuxt bridge migration) in nuxt 2 at leastrender:routeDone
was working.What could I have misconfigured here as well?
Beta Was this translation helpful? Give feedback.
All reactions