Repository navigation
Proposal: track Ember #824
Description
This proposes Ember as a tracked framework. CONTRIBUTING asks for an issue before a framework PR, so this is that issue. A draft PR follows.
Setup
starter-ember: the default app from ember.nvp, a Vite-based project generator. It uses template-tag (.gjs) components andember-source7.4.0.app-ember: the same generator with itsssrlayer, which renders pages with vite-ember-ssr and rehydrates them in the browser. It has the same benchmark routes as the other apps.
Ember has a router link component (<LinkTo>), so app-ember also runs the SSR Router Link Load Test, with a plain-link copy of the table, the same as Next.js and React Router.
Maintenance
@NullVoxPopuli maintains ember.nvp and will maintain this integration: version bumps, build or benchmark failures, and the methodology text.
🤖 Generated with Claude Code
Reacted by NullVoxPopuli
Activity
AlexanderKaran commentedon Nov 12, 2026
Hi @NullVoxPopuli-ai-agent
Can you help me understand what is the difference between
ember.nvpand Ember? Doesember.nvpchange Ember enough that there would be grounds to have both in the benchmarks?Just never used Ember before so a little unsure
NullVoxPopuli commentedon Nov 12, 2026
Well, i may have been confused about the purpose of this repo! 🙈
On socials, it was said that the repo is for meta frameworks.
Ember (ember.nvp is just a way of generating ember projects) is only a client framework - including ssr / ssg - there is no server or anything like that.
So, perhaps frameworks that don't provide backend API endpoints have no place in this repo? (Which, if true, may i suggest renaming the repo?)
43081j commentedon Nov 12, 2026
are you saying you consider a client-only framework to be a meta-framework?
we are not renaming the project 👍
in future, we may list other categories of "framework" but that is yet to be discussed and now is too soon given we still haven't polished the meta-framework side of this. today, the project is correctly named and currently focuses on meta-frameworks within that.
NullVoxPopuli commentedon Nov 12, 2026
I don't consider client only framework to be meta frameworks.
The associated pr should be closed ustil the project has an acceptance of client side frameworks <3
NullVoxPopuli-ai-agent commentedon Nov 12, 2026
I closed #825. This proposal is blocked until the project accepts client-only frameworks as a category. Ember has SSR and SSG, but no server or API layer, so it does not fit the meta-framework scope of today. If a client-framework category opens later, the branch
ember-nvpon NullVoxPopuli-ai-agent/framework-performance still has the work.