-
-
Notifications
You must be signed in to change notification settings - Fork 33.7k
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
SSR Async Component Functional = TypeError: Cannot read property 'Ctor' of undefined #7784
Closed
luisatmaniak opened this issue
Mar 10, 2018
· 0 comments
· Fixed by annict/annict#1034, annict/annict#1035, owncloud/web#46, OSM-Browser/osm-browser#56 or OSM-Browser/osm-browser#58
Closed
SSR Async Component Functional = TypeError: Cannot read property 'Ctor' of undefined #7784
luisatmaniak opened this issue
Mar 10, 2018
· 0 comments
· Fixed by annict/annict#1034, annict/annict#1035, owncloud/web#46, OSM-Browser/osm-browser#56 or OSM-Browser/osm-browser#58
Comments
yyx990803
added a commit
that referenced
this issue
Mar 13, 2018
This was referenced Mar 14, 2018
6 tasks
f2009
pushed a commit
to f2009/vue
that referenced
this issue
Jan 25, 2019
aJean
pushed a commit
to aJean/vue
that referenced
this issue
Aug 19, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version
2.5.14
Reproduction link
luisatmaniak/vue-hackernews-2.0@142d1d7
Steps to reproduce
On the server, when rendering a component asynchronously that is also functional, errors are thrown on the console. In this particular repo (vue hacker news 2.0) it fails the first time, but for some reason, it works for a subsequent request. The same thing works just fine if it's done in the browser (non-ssr).
What is expected?
No errors thrown, correct HTML produced on the server.
What is actually happening?
An error is thrown on the console, HTML not produced at all.
The text was updated successfully, but these errors were encountered: