Daniel Roe
Daniel Roe
I can't reproduce this. Would you provide a reproduction? For example, the link to that CSB. :pray:
This appears to be reproducible in a non-Nuxt setup and is probably an issue with the vue `` component + SSR. Would you open an issue in https://github.com/vuejs/core? https://stackblitz.com/edit/github-ncyrhd
This is Vue core behaviour, rather than Nuxt's, and is deliberate. It assumes that a component can reference itself by means of its own file name. See https://vuejs.org/api/sfc-script-setup.html#recursive-components
Reopening to see if there is a way we can or should work around this.
Reopening to see if there is a way we can or should work around this.
Sure 👍 I am also working on resolving https://github.com/nuxt/nuxt.js/issues/14573, which may touch some of these files too, but I think this is safe to merge and we can iterate.
@mmis1000 Yes, it is, and https://github.com/nuxt/nuxt.js/issues/14573 exists to track it. I don't believe it's affected by this PR; please let me know if you think otherwise.
This PR deliberately doesn't make it reactive. So it should only change the suspense structure if there is _already_ a rerender happening.
You're right, it does cause an unnecessary rerender. We may pend this PR as I have local work-in-progress that doesn't cause it, and it makes sense to resolve nuxt/nuxt.js#14573 at...
Ahh. The issue is that etags/size/mime/encoding is calculated when the nitro build happens, and you are modifying the files _afterwards_.