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 believe that changing this.$nuxt to this.<%= globals.nuxt %> (as it is in other places within that file) should fix the problem.
It's strange that it gets past the condition, though. Maybe webpack resolve this.$nuxt to true when it's being built, thus exposing this.$nuxt.fetchPayload?
The text was updated successfully, but these errors were encountered:
Thanks for your contribution to Nuxt.js!
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
If you would like this issue to remain open:
Verify that you can still reproduce the issue in the latest version of nuxt-edge
Comment the steps to reproduce it
Issues that are labeled as pending will not be automatically marked as stale.
Versions
Reproduction
I'm getting an error under circumstances it's hard to reproduce, but I'm pretty sure I see the the cause of the problem.
If I set
globalName
in nuxt.config.js to a custom name, I get an error (cannot get propertyfetchPayload
of undefined).The error is caused by the 2 lines that reference
this.$nuxt
: https://github.com/nuxt/nuxt.js/blob/dev/packages/vue-app/template/components/nuxt-link.client.js#L114-L115I believe that changing
this.$nuxt
tothis.<%= globals.nuxt %>
(as it is in other places within that file) should fix the problem.It's strange that it gets past the condition, though. Maybe webpack resolve
this.$nuxt
totrue
when it's being built, thus exposingthis.$nuxt.fetchPayload
?The text was updated successfully, but these errors were encountered: