Works fine enough on 33.1.0 here, as far as client-side-rendered SPAs go on PM tbh.
---
Off-topic:
But this caught my eye:
Moonchild wrote: ↑2024-04-21, 15:21
The site makes over 200 individual requests to the server for its home page [...]
It is stupid, yes. And it is due to an issue (design flaw, imo) with Nuxt, which we ran into as well in the past:
https://github.com/nuxt/nuxt/issues/14584 (and a few more of similar type).
For some reason, they decided that to bundle the final client files, each visual component would go into its own JS file, and then *all* get preloaded 1-by-1 in the SPA's HTML template. And thus any entrypoint gets to download every single bit of the website all at once, instead of doing the sane thing, ie building a dependency graph of entrypoints and components, extracting common components, then loading these as-needed from there on JS-driven imports or similar.
The end result being this hundreds-of-js-files-and-images-etc mess. Dead-giveaway being those 100+ /_nuxt/[hash].js files.
To add insult to injury, it also insists on preloading all files in a certain class of applications assets (details are irrelevant), so you get many extra image files preloaded needlessly on top of it.
And there's only very limited solutions for either of these issues atm... In our case, forcing it to bundle per-page instead of per-component (in a really hacky way:
https://github.com/nuxt/nuxt/issues/145 ... 1837436340) got us from 400+ JS files to... 16.
Still more than we'd like, but yeah. My guess is they have PTSD from early JS days where a single 8MB app.js file was also a bit stupid of an approach. But I wonder what is the point of all these dynamic import specs if they never get used in practice... sigh...