Skip to content

[Nitro/SolidStart] use Nitro's SDK as a dependency of SolidStart SDK #17993

@logaretm

Description

@logaretm

Similar to what we are doing for Nuxt's SDK, we would like to hand over all the server-side instrumentation to the Nitro SDK, so the solidstart SDK should be only doing solid specifics.

This will have the added benefits of Database, Server-side Cache, and Storage APIs but they don't seem relevant in that ecosystem.

I'm not sure yet how much Vinxi stuff comes into play here, but for the most part it seems the same stuff we do in Nuxt's today.

Metadata

Metadata

Assignees

No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions