Renaming "Qwik City" into "Qwik Router" in V2

[shairez]

What's the motivation for this proposal?

Problems you are trying to solve:

• "Qwik City" as a name requires extra explanation
• A meta framework on top of Qwik (which is already very different than any other framework) adds another layer of confusion when learning about it

Goals you are trying to achieve:

• Simplicity in both learning and explaining about Qwik

Any other context or information you want to share:

---

Proposed Solution / Feature

What do you propose?

In V2, the plan is to have the only "breaking changes" be the packages renaming.

Qwik will become @qwik.dev/core
and Qwik City will become @qwik.dev/router

99% of the stuff inside of "Qwik City" is routing related - even SSG, loaders and actions and server functions (which are RPCs "routed" to the right place on the server)

So in the end of the day, renaming this package with no breaking API changes (everything will stay backwards compatible with Qwik City) we think will make things easier for Qwik developers.

[PatrickJS]

Yes let’s change it

[steffanek]

Totally agree!!