Qwik Router Spec #228
thejackshelton
started this conversation in
Proposals For Qwik
Qwik Router Spec
#228
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
What is it about?
spec
basically this is the feature list of qwik-city, which ones could be done by nitro instead?
[...catchall]and(hidden)folders for naminglayoutfiles that provide:onDocumentcallbacks for providing<head>dataindexfiles that are the route leaves and can also contain request callbacksmdxfiles that are transformedplugin@[name].tswhich sees all requests before ssr starts)<Link>componentsrouteLoader$: exported by layouts and indexes, loads data for that route before SSR startsaction$: used to handle forms, either as a POST or as XHR requestserver$: used to run server functions via XHR requestsTLDR: Almost exactly like previous Qwik Router / City
BUT using other packages and tooling instead of "re-inventing the wheel".
NEW:
api report json with all the endpoints exported -> optimizer helps figure out the scope capture and params -> Qwik Router finds the endpoints and vars -> updates API report -> Ex: (Developers (consumers) go Ah! I'm not backwards compatible with previous version)
Qwik Router only does read of manifest and writes API report ^
Best way forward, start doing environment api
use vite-envs branch -> grab latest from build/v2 -> start working towards vite environment API, with all the above, pretty much no API changes.
h3 handles runtime adapters for everything, but Qwik Router also has express, fastify, connect, polka adapters, so we need to make sure these still work.
https://qwik.dev/docs/deployments/node/#installation
Beta Was this translation helpful? Give feedback.
All reactions