Modularity and visibility question: Why exposing everything is the default behavior? Can it be changed with config?

[Chaciej]

When building a SvelteKit app, all routes becomes visible to the client, even if they're not in use (not available within the current network of pages context). Why is this the default behavior? It seems counterintuitive and could potentially lead to side effects. It's not only about security either, this was particularly troublesome for a puzzle game project I was working on, where finding clues about the next route name is crucial. In contrast, Next.js 13 doesn't seem to have this issue as it loads code progressively.

I know similar question has been asked before: #10072

Modularity question (connected to the previous): Is it possible to build only parts of an application in SvelteKit?
What I have in mind is building a selected fragment from all of my route files, like one nested block separately (if not possible in SK we can discuss potential solutions besides finding another framework)

In my current case I would prefer having many smaller projects nested within bigger one (for example these would be accessed from another domain). While one could argue to simply add a separate app for these, that's not always the most practical solution as server memory and management time are finite resource.

I really enjoy working with SvelteKit as simple and intuitive as it is, but I've run into issues that make me reconsider their viability for certain projects. I think there's room for improvement, and I'm interested in the community's thoughts on this.

Cheers!