You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
Discussed in #185
Active PR:
QwikDev/qwik#7008
Originally posted by shairez October 20, 2024
What's the motivation for this proposal?
Problems you are trying to solve:
Goals you are trying to achieve:
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.
The text was updated successfully, but these errors were encountered: