SPA mode for routing, a static index.html that is served by the infra provider directly without hitting handler as a catch-all route
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 11.2k
- Forks
- 899
- Avg merge
- 2d 24m
- Merged PRs (30d)
- 40
Description
Describe the feature
I am trying to implement a SPA mode for Solid Start. We need a way where we can say this set of routes (accounting for sub routes to be handled by specific handler) should be handled by a static index.html that the infra provider should serve without hitting the handler.
Eg.
/api/** - Handled by API route
/** - serve index.html statically
Additional information
- Would you be willing to help implement this feature?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named in the issue. Start by tracing Nitro's routing and deployment-provider integration for catch-all routes, then determine how /api/** can remain handler-backed while /** is served as a static index.html. Done means the behavior is supported for the relevant infrastructure provider paths without invoking the handler for the SPA fallback.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend, infrastructure, web-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100