Alex Liu

I'm guessing this issue might be related to #13350. Would you like to try the following method? It may help solve the error you encountered. ```vue const asyncData = useAsyncData('blog',...

I apologize, but I suspect this issue might be related to other components in your project. The method provided above is merely a workaround and does not truly solve the...

How about using a number like XMLHttpRequest.readyState ? I'm not sure if it's going to be like a magic number. https://developer.mozilla.org/en-US/docs/Web/API/XMLHttpRequest/readyState

If it is an external link, `to.value` is a string, so I only judge whether `to.value` is a string, if yes, skip it, if not, execute `router.resolve(to.value)` .

> **re: extra spaces in `` and ``** > > Yes, please! Every time I see this I want to send a PR but have been avoiding the distraction >...

> I wonder if these changes will have a significant impact after text compression. GZIP/brotli should cover a lot of that already. > > Would be interesting to see benchmarks...

> Yes, for both. Ideally, the `head` module would allow providing options to be used with the `renderSSRHead` function. > > I think if you want to tackle this, you...

@manniL I have tried to compare the differences before and after this PR using the Nuxt Movies project. From the Response Headers provided by Chrome DevTools, I found Before Content-Length:...

Thank you for bringing this to my attention. I resolved the conflict caused by #19144.

I'm unsure which option is better between using `name` or `path` for dynamic route, Even though they resolve to the same page components, their paths may still differ. While `name`...