# solidjs/solid-start · RepoSense Release & Migration Intelligence

> Preserve file and blob metadata in server function payloads. Update dependencies normally. Migration: None.

## Metadata
- **Repository URL**: https://github.com/solidjs/solid-start
- **Primary Package**: `@solidjs/start` (NPM)
- **Categories**: `FRAMEWORK`, `BACKEND`
- **Latest Version**: `@solidjs/start@2.2.1`
- **Semantic Status**: `COMPATIBLE`
- **Bundle Size Impact (unavailable)**: `Size Unavailable`
- **Atom Ingestion Feed**: https://github.com/solidjs/solid-start/releases.atom

## The Human Context (Plain-English Pitch)
SolidStart is the official application framework for SolidJS, providing server-side rendering, routing, and server functions out of the box. It simplifies building reactive, high-performance web applications by bridging client and server code seamlessly. This release fixes metadata transmission issues when sending files and blobs to server functions.

## Stage 1 Executive Summary ([Core Change] + [Required Action] + [Migration Effort])
Preserve file and blob metadata in server function payloads. Update dependencies normally. Migration: None.

## Breaking Changes & Required Actions
- Preserves original file names and `lastModified` properties during server function uploads.
- Ensures blobs arrive as a `Blob` instance instead of a generic `File` named `blob`.
- Retains empty MIME types on uploaded payloads instead of falling back to `application/octet-stream`.

## Migration Snippet
```ts
npm i @solidjs/start@2.2.1
```

## Ecosystem Compatibility Matrix & Graph Warnings
- **TypeScript >=5.0** [`COMPATIBLE`]: Fully compatible with existing TypeScript configurations and type definitions.
- **Vite ^5.0** [`COMPATIBLE`]: Maintains seamless integration with standard Vite bundling pipelines.

## Zero-Noise Release Timeline
- **@solidjs/start@2.2.1** (2026-11-03) [COMPATIBLE]: Preserve file and blob metadata in server function payloads. Update dependencies normally. Migration: None.

## Upgrade & Migration Q&A (GEO Direct Answers)
### Is solidjs/solid-start @solidjs/start@2.2.1 safe to upgrade in production?
solidjs/solid-start @solidjs/start@2.2.1 is classified as COMPATIBLE (PATCH release). Preserve file and blob metadata in server function payloads. Update dependencies normally. Migration: None.

### What breaking changes or compatibility risks exist in solidjs/solid-start @solidjs/start@2.2.1?
No breaking API changes or peer dependency conflicts are recorded for solidjs/solid-start @solidjs/start@2.2.1 in the RepoSense compatibility graph.

### What is the bundle size impact of @solidjs/start @solidjs/start@2.2.1?
Measured bundle size telemetry is currently unavailable for @solidjs/start @solidjs/start@2.2.1; verify build output locally before deploying.

### How do I upgrade @solidjs/start to @solidjs/start@2.2.1?
Upgrade @solidjs/start to @solidjs/start@2.2.1 by running "npm install @solidjs/start@@solidjs/start@2.2.1" and applying the migration steps: npm i @solidjs/start@2.2.1