Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

onResponseError element-plus el-notification bug

See original GitHub issue

Environment

Operating System: Linux
Node Version: v16.14.2
Nuxt Version: 3.0.0-rc.4
Package Manager: npm@7.17.0
Builder: vite
User Config: css, build
Runtime Modules: -
Build Modules: -

Reproduction

https://stackblitz.com/edit/github-38hauf?file=composables/useApi.ts

Describe the bug

Hello, in the header I get a null user but if i comment ElNotification which is in onResponseError of useApi.ts i get my user in the header. I don’t understand why. (sorry for my English)

Additional context

dependency element-plus 2.2.6

Logs

No response

Issue Analytics

State:
Created a year ago
Comments:7 (4 by maintainers)

Top GitHub Comments

2reactions

arnauddoubcommented, Jul 6, 2022

If people are interested, with this code I can have the notifications and the user in async in the layout stackblitz

0reactions

danielroecommented, Jul 4, 2022

This is a common SSR gotcha. The issue is that on SSR, Vue renders the HTML from top to bottom, outside to inside. And if you only fetch the user as you are rendering the ‘inner’ part of the page, it doesn’t rerender the layout at the top of the page. (On client-side it’s fine as can be reactive.) So if you have a common piece you rely on for rendering your page, make sure to fetch it in the layout, a plugin, or a middleware - somewhere outside of the rendering process.