solidstart-request-events

To access request event data in SolidStart, use the getRequestEvent function to retrieve the current server context, including details like the request URL and headers within your server-side routes.

Share type-safe data in SolidStart by defining custom properties on event.locals within your middleware. This allows you to pass typed context, like authenticated user objects, securely to downstream server functions.

Yes, you can access the underlying H3 event object directly in SolidStart by utilizing the nativeEvent function, which facilitates advanced scenarios like direct response manipulation and low-level request metadata logging.

Implement server-side authentication in SolidStart by intercepting requests in middleware to check the Authorization header, store the validated user object in event.locals, and access it later in your server route to fetch user-specific data.

Yes, SolidStart supports setting custom response headers from server functions. You can retrieve the server context using getRequestEvent and manipulate the response headers directly for advanced control over your HTTP responses.

Use nativeEvent instead of getRequestEvent when you require direct access to the underlying Vinxi or H3 event object for advanced scenarios that go beyond basic server context retrieval, such as low-level response manipulation.