-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Disclose render mode #11724
Milestone
Comments
Possibly related: It'd be useful to see a tree of routes with the rendering method listed for each, to review for performance opportunities, likely as part of build output. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the problem
The performance characteristics of SPA vs SSR apps is very different. While many frameworks only support one or the other, SvelteKit can run in different modes and supports both. It quite hard to compare SvelteKit to an SSR-only framework or SPA-only framework because our numbers are grouped together despite these being totally different deployment modes. Being able to report on this would help us generate better reports at https://cwvtech.report/ to understand where users are succeeding at creating fast sites and where we can better guide them.
HTTPArchive/cwv-tech-report#32 (comment)
Describe the proposed solution
One possibility would be to generate something like:
And then mark feature usage for stuff like
ssr|prerendered|spa|mpa
andenhanced-img
:https://www.w3.org/TR/user-timing/#dfn-mark_feature_usage
This could be controlled by an option similar to Svelte's
discloseVersion
option.Alternatives considered
No response
Importance
nice to have
Additional Information
No response
The text was updated successfully, but these errors were encountered: