SolidStart, the Solid app framework
Repo solidjs/solid-start, read from GitHub 11 min ago. solidjs has not joined Take My Repo.
seroval and seroval-plugins to ^1.8.0.@solidjs/start out of server pre-bundling, so that server functions no longer fail with "invalid server function" in dev with plugins that pre-bundle server dependencies, such as the Cloudflare Vite plugin.fetch never rejected: with Nitro, the error hook and the errorHandler never ran for it, and SolidStart's own dev server never showed its error overlay. An h3 HTTPError not marked unhandled, or a status thrown as a number, is answered as before. A server that calls the handler's fetch itself now gets a rejected promise for such an error and answers it; headers set for the error response with event.res.errHeaders are not part of that answer.HEAD request when a route file exports both a page and a GET that returns nothing, such as a [...404].tsx. The server threw "did not return a response" and answered 500 instead of rendering the page as it does for GET.Blob instead of a File named blob, an empty type stays empty instead of application/octet-stream, and a file keeps its exact name and its lastModified. The server still reads uploads from clients that send only the part index.Blob instead of a File named blob, an empty type stays empty instead of application/octet-stream, and a file keeps its exact name and its lastModified. The server still reads uploads from clients that send only the part index.FormData that is the only argument. A call like upload(file, { tags }), or one with files in arrays, objects, maps, sets or form data, sends them as parts of multipart form data next to the serialized arguments, and the server function gets them as File values. Calls without files are sent as before.serverFunctions.skewProtection. When it is on, a page loaded before a deploy can no longer call the new server's functions with an outdated client. The server answers such a call with 409 instead of running the function, and the page reloads once to load the new version. Each build gets a random ID, or pass { buildId } (such as a commit hash) when several machines build the same deploy. Only applies to production builds, and is off by default.upload(file, { tags }), or one with files in arrays, objects, maps, sets or form data, sends them as parts of multipart form data next to the serialized arguments, and the server function gets them as File values. Calls without files are sent as before.seroval and seroval-plugins to 1.7.0.OPTIONS handler are now matched as API routes.@sentry/solidstart) resolved to their Node build in the browser. The dev overlay's @jridgewell/trace-mapping is now pre-bundled, as the "browser" condition makes it import a UMD build."use server" function was compiled: its body shipped in the client bundle, and the build failed with Attempt to import 'server-only' in a client module once one of them imported server-only code such as @solidjs/start/http. The ids of lazily loaded route components matched no client manifest entry either, so their CSS was missing from the server-rendered HTML. Relative patterns in the serverFunctions.filter option now resolve against Vite's root too.