Qwik City lazy-loaded route chunks exposed without authorization guards
Qwik City utilizes file-based routing where route components are lazy-loaded via dynamic imports. This process generates separate entry chunks that the browser fetches via the client-side loader when a user navigates to a specific path. Currently, the framework lacks a built-in declarative mechanism to restrict access to these generated chunks based on user
qwik