-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using ssr: false
throws on mount: Cannot create proxy with a non-object as target or handler
#20210
Labels
Comments
I have the same issue upgrading from 3.3.3 to 3.4.0 |
stafyniaksacha
changed the title
Using
Using Apr 11, 2023
ssr: false
in routeRules
throws on mount: Cannot create proxy with a non-object as target or handler
ssr: false
throws on mount: Cannot create proxy with a non-object as target or handler
8 tasks
m0ksem
added a commit
to epicmaxco/vuestic-ui
that referenced
this issue
Apr 11, 2023
m0ksem
added a commit
to epicmaxco/vuestic-ui
that referenced
this issue
Apr 12, 2023
Me to, same error ! |
I had the same error and had to downgrade it And only downgrading it didn't work, I had to delete the lock file and node_modules |
meadowsys
added a commit
to meadowsys/wiwipaccer
that referenced
this issue
Apr 13, 2023
critical bug: nuxt/nuxt#20210
Wondering what the procedure is, when will you publish a patch for this? |
It's planned for today: #20246. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Environment
RootDir: /home/projects/nuxt-starter-5g3aev
Nuxt project info:
Reproduction
https://stackblitz.com/edit/nuxt-starter-5g3aev?file=nuxt.config.ts
Describe the bug
Disabling SSR, (ex: through route rules, or in global config) result in blank page.
Same happen with
experimental.renderJsonPayloads
andexperimental.respectNoSSRHeader
Additional context
No response
Logs
Error while mounting app: TypeError: Cannot create proxy with a non-object as target or handler at createNuxtApp (nuxt.js:98:1) at initApp (entry.js:39:18) at entry.js:57:3
The text was updated successfully, but these errors were encountered: