Skip to content

Option to disable router #13445

@benmccann

Description

@benmccann

Describe the problem

I noticed while writing #13444 that you can't super easily build an MPA with SvelteKit today. One use case I have for this is a site where I have only a single page and so the router is unnecessary overhead. When I mentioned the option in another thread, @theetrain @khromov and @paoloricciuti expressed that it would be useful/cool option to have

Describe the proposed solution

A router option

I think disabling the router would also disable functionality associated with the router such as the before and after navigate callbacks. This is much simpler than creating a separate MPA implementation that provides those. That could always be done down the road if there is demand, but I don't think as many people are going to want those and it doesn't need to block the feature.

Alternatives considered

Note that we already have 'csr` for client-side rendering so we should avoid using that acronym for client-side routing

Importance

nice to have

Additional Information

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions