chore(deps): update dependency vite to v6.1.5 [security] - abandoned

.github/labeler.yml

@@ -22,20 +22,14 @@
   - 'packages/start-api-routes/**/*'
 'package: react-start-client':
   - 'packages/react-start-client/**/*'
-'package: react-start-config':
-  - 'packages/react-start-config/**/*'
 'package: react-start-plugin':
   - 'packages/react-start-plugin/**/*'
-'package: react-start-router-manifest':
-  - 'packages/react-start-router-manifest/**/*'
 'package: react-start-server':
   - 'packages/react-start-server/**/*'
 'package: start-server-functions-client':
   - 'packages/start-server-functions-client/**/*'
 'package: start-server-functions-fetcher':
   - 'packages/start-server-functions-fetcher/**/*'
-'package: start-server-functions-handler':
-  - 'packages/start-server-functions-handler/**/*'
 'package: start-server-functions-ssr':
   - 'packages/start-server-functions-ssr/**/*'
 'package: router-cli':
@@ -74,8 +68,6 @@
   - 'packages/solid-start-server/**/*'
 'package: start':
   - 'packages/start/**/*'
-'package: start-config':
-  - 'packages/start-config/**/*'
 'package: start-server-functions-server':
   - 'packages/start-server-functions-server/**/*'
 'package: valibot-adapter':

.gitignore

@@ -61,12 +61,14 @@ nx-cloud.env
 gpt/db.json
 
 app.config.timestamp-*
+vite.config.timestamp-*
 vite.config.js.timestamp-*
 vite.config.ts.timestamp-*
 app.config.js.timestamp-*
 app.config.ts.timestamp-*
 
 app.config.timestamp_*
+vite.config.timestamp_*
 vite.config.js.timestamp_*
 vite.config.ts.timestamp_*
 app.config.js.timestamp_*

.npmrc

@@ -1,3 +1,3 @@
 link-workspace-packages=true
 prefer-workspace-packages=true
-provenance=true
+provenance=false

.prettierignore

@@ -7,7 +7,6 @@
 pnpm-lock.yaml
 **/snapshots
 **/.vercel
-**/.vinxi
 **/.output
 **/node_modules
 node_modules

docs/router/eslint/create-route-property-order.md

@@ -29,7 +29,7 @@ Examples of **incorrect** code for this rule:
 /* eslint "@tanstack/router/create-route-property-order": "warn" */
 import { createFileRoute } from '@tanstack/react-router'
 
-export const Route = createFileRoute('/foo/bar/$id')({
+export const Route = createFileRoute({
   loader: async ({context}) => {
     await context.queryClient.ensureQueryData(getQueryOptions(context.hello)),
   },
@@ -43,7 +43,7 @@ Examples of **correct** code for this rule:
 /* eslint "@tanstack/router/create-route-property-order": "warn" */
 import { createFileRoute } from '@tanstack/react-router'
 
-export const Route = createFileRoute('/foo/bar/$id')({
+export const Route = createFileRoute({
   beforeLoad: () => ({hello: 'world'}),
   loader: async ({context}) => {
     await context.queryClient.ensureQueryData(getQueryOptions(context.hello)),

docs/router/framework/react/api/router/createFileRouteFunction.md

@@ -26,7 +26,7 @@ A new function that accepts a single argument of type [`RouteOptions`](./RouteOp
 ```tsx
 import { createFileRoute } from '@tanstack/react-router'
 
-export const Route = createFileRoute('/')({
+export const Route = createFileRoute({
   loader: () => {
     return 'Hello World'
   },

docs/router/framework/react/api/router/retainSearchParamsFunction.md

@@ -39,7 +39,7 @@ const searchSchema = z.object({
   two: z.string().optional(),
 })
 
-export const Route = createFileRoute('/hello')({
+export const Route = createFileRoute({
   validateSearch: zodValidator(searchSchema),
   search: {
     middlewares: [retainSearchParams(true)],

docs/router/framework/react/api/router/stripSearchParamsFunction.md

@@ -30,7 +30,7 @@ const searchSchema = z.object({
   two: z.string().default(defaultValues.two),
 })
 
-export const Route = createFileRoute('/hello')({
+export const Route = createFileRoute({
   validateSearch: zodValidator(searchSchema),
   search: {
     // strip default values
@@ -68,7 +68,7 @@ const searchSchema = z.object({
   two: z.string().default('xyz'),
 })
 
-export const Route = createFileRoute('/hello')({
+export const Route = createFileRoute({
   validateSearch: zodValidator(searchSchema),
   search: {
     // remove all search params

docs/router/framework/react/decisions-on-dx.md

@@ -225,7 +225,7 @@ Let's take a look at how the route configuration for the previous example would
 // src/routes/posts/index.ts
 import { createFileRoute } from '@tanstack/react-router'
 
-export const Route = createFileRoute('/posts/')({
+export const Route = createFileRoute({
   component: () => 'Posts index component goes here!!!',
 })
 ```

docs/router/framework/react/guide/external-data-loading.md

@@ -48,7 +48,7 @@ Here is a naive illustration (don't do this) of using a Route's `loader` option
 // src/routes/posts.tsx
 let postsCache = []
 
-export const Route = createFileRoute('/posts')({
+export const Route = createFileRoute({
   loader: async () => {
     postsCache = await fetchPosts()
   },
@@ -80,7 +80,7 @@ const postsQueryOptions = queryOptions({
   queryFn: () => fetchPosts(),
 })
 
-export const Route = createFileRoute('/posts')({
+export const Route = createFileRoute({
   // Use the `loader` option to ensure that the data is loaded
   loader: () => queryClient.ensureQueryData(postsQueryOptions),
   component: () => {
@@ -105,7 +105,7 @@ export const Route = createFileRoute('/posts')({
 When an error occurs while using `suspense` with `Tanstack Query`, you'll need to let queries know that you want to try again when re-rendering. This can be done by using the `reset` function provided by the `useQueryErrorResetBoundary` hook. We can invoke this function in an effect as soon as the error component mounts. This will make sure that the query is reset and will try to fetch data again when the route component is rendered again. This will also cover cases where users navigate away from our route instead of clicking the `retry` button.
 
 ```tsx
-export const Route = createFileRoute('/posts')({
+export const Route = createFileRoute({
   loader: () => queryClient.ensureQueryData(postsQueryOptions),
   errorComponent: ({ error, reset }) => {
     const router = useRouter()

docs/router/framework/react/guide/router-context.md

@@ -92,7 +92,7 @@ Once you have defined the router context type, you can use it in your route defi
 
 ```tsx
 // src/routes/todos.tsx
-export const Route = createFileRoute('/todos')({
+export const Route = createFileRoute({
   component: Todos,
   loader: ({ context }) => fetchTodosByUserId(context.user.id),
 })
@@ -122,7 +122,7 @@ Then, in your route:
 
 ```tsx
 // src/routes/todos.tsx
-export const Route = createFileRoute('/todos')({
+export const Route = createFileRoute({
   component: Todos,
   loader: ({ context }) => context.fetchTodosByUserId(context.userId),
 })
@@ -158,7 +158,7 @@ Then, in your route:
 
 ```tsx
 // src/routes/todos.tsx
-export const Route = createFileRoute('/todos')({
+export const Route = createFileRoute({
   component: Todos,
   loader: async ({ context }) => {
     await context.queryClient.ensureQueryData({
@@ -234,7 +234,7 @@ So, now in our route's `loader` function, we can access the `networkStrength` ho
 ```tsx
 import { createFileRoute } from '@tanstack/react-router'
 
-export const Route = createFileRoute('/posts')({
+export const Route = createFileRoute({
   component: Posts,
   loader: ({ context }) => {
     if (context.networkStrength === 'STRONG') {
@@ -282,7 +282,7 @@ const router = createRouter({
 ```tsx
 import { createFileRoute } from '@tanstack/react-router'
 
-export const Route = createFileRoute('/todos')({
+export const Route = createFileRoute({
   component: Todos,
   beforeLoad: () => {
     return {

docs/router/framework/react/guide/tanstack-start.md

@@ -47,15 +47,12 @@ TanStack Start is powered by the following packages and need to be installed as
 
 - [@tanstack/start](https://github.com/tanstack/start)
 - [@tanstack/react-router](https://tanstack.com/router)
-- [Vinxi](https://vinxi.vercel.app/)
-
-> [!NOTE]
-> Vinxi is a temporary dependency that will be replaced by a simple vite plugin or a dedicated Start CLI.
+- [Vite](https://vite.dev/)
 
 To install them, run:
 
 ```shell
-npm i @tanstack/react-start @tanstack/react-router vinxi
+npm i @tanstack/react-start @tanstack/react-router vite
 ```
 
 You'll also need React and the Vite React plugin, so install their dependencies as well:
@@ -72,16 +69,16 @@ npm i -D typescript @types/react @types/react-dom
 
 # Update Configuration Files
 
-We'll then update our `package.json` to use Vinxi's CLI and set `"type": "module"`:
+We'll then update our `package.json` to use Vite's CLI and set `"type": "module"`:
 
 ```jsonc
 {
   // ...
   "type": "module",
   "scripts": {
-    "dev": "vinxi dev",
-    "build": "vinxi build",
-    "start": "vinxi start",
+    "dev": "vite dev",
+    "build": "vite build",
+    "start": "vite start",
   },
 }
 ```
@@ -97,12 +94,10 @@ export default defineConfig({})
 
 # Add the Basic Templating
 
-There are four required files for TanStack Start usage:
+There are 2 required files for TanStack Start usage:
 
 1. The router configuration
-2. The server entry point
-3. The client entry point
-4. The root of your application
+2. The root of your application
 
 Once configuration is done, we'll have a file tree that looks like the following:
 
@@ -111,10 +106,8 @@ Once configuration is done, we'll have a file tree that looks like the following
 ├── app/
 │   ├── routes/
 │   │   └── `__root.tsx`
-│   ├── `client.tsx`
 │   ├── `router.tsx`
 │   ├── `routeTree.gen.ts`
-│   └── `ssr.tsx`
 ├── `.gitignore`
 ├── `app.config.ts`
 ├── `package.json`
@@ -123,7 +116,7 @@ Once configuration is done, we'll have a file tree that looks like the following
 
 ## The Router Configuration
 
-This is the file that will dictate the behavior of TanStack Router used within Start. Here, you can configure everything
+This is the file that will dictate the behavior of TanStack Router used within Start for both the server and the client. Here, you can configure everything
 from the default [preloading functionality](./preloading.md) to [caching staleness](./data-loading.md).
 
 ```tsx
@@ -149,52 +142,9 @@ declare module '@tanstack/react-router' {
 > `routeTree.gen.ts` is not a file you're expected to have at this point.
 > It will be generated when you run TanStack Start (via `npm run dev` or `npm run start`) for the first time.
 
-## The Server Entry Point
-
-As TanStack Start is an [SSR](https://unicorn-utterances.com/posts/what-is-ssr-and-ssg) framework, we need to pipe this router
-information to our server entry point:
-
-```tsx
-// app/ssr.tsx
-import {
-  createStartHandler,
-  defaultStreamHandler,
-} from '@tanstack/react-start/server'
-import { getRouterManifest } from '@tanstack/react-start/router-manifest'
-
-import { createRouter } from './router'
-
-export default createStartHandler({
-  createRouter,
-  getRouterManifest,
-})(defaultStreamHandler)
-```
-
-This allows us to know what routes and loaders we need to execute when the user hits a given route.
-
-## The Client Entry Point
-
-Now we need a way to hydrate our client-side JavaScript once the route resolves to the client. We do this by piping the same
-router information to our client entry point:
-
-```tsx
-// app/client.tsx
-import { hydrateRoot } from 'react-dom/client'
-import { StartClient } from '@tanstack/react-start'
-import { createRouter } from './router'
-
-const router = createRouter({
-  scrollRestoration: true,
-})
-
-hydrateRoot(document!, <StartClient router={router} />)
-```
-
-This enables us to kick off client-side routing once the user's initial server request has fulfilled.
-
 ## The Root of Your Application
 
-Finally, we need to create the root of our application. This is the entry point for all other routes. The code in this file will wrap all other routes in the application.
+Finally, we need to create the root of our application. This is the entry point for all application routes. The code in this file will wrap all other routes in the application.
 
 ```tsx
 // app/routes/__root.tsx

docs/router/framework/react/migrate-from-react-location.md

@@ -112,7 +112,7 @@ export const Route = createRootRoute({
 // src/routes/index.tsx
 import { createFileRoute } from '@tanstack/react-router'
 
-export const Route = createFileRoute('/')({
+export const Route = createFileRoute({
   component: Index,
 })
 ```
@@ -125,7 +125,7 @@ export const Route = createFileRoute('/')({
 // src/routes/posts.tsx
 import { createFileRoute, Link, Outlet } from '@tanstack/react-router'
 
-export const Route = createFileRoute('/posts')({
+export const Route = createFileRoute({
   component: Posts,
   loader: async () => {
     const posts = await fetchPosts()
@@ -164,7 +164,7 @@ function Posts() {
 // src/routes/posts.index.tsx
 import { createFileRoute } from '@tanstack/react-router'
 
-export const Route = createFileRoute('/posts/')({
+export const Route = createFileRoute({
   component: PostsIndex,
 })
 ```
@@ -177,7 +177,7 @@ export const Route = createFileRoute('/posts/')({
 // src/routes/posts.$postId.tsx
 import { createFileRoute } from '@tanstack/react-router'
 
-export const Route = createFileRoute('/posts/$postId')({
+export const Route = createFileRoute({
   component: PostsId,
   loader: async ({ params: { postId } }) => {
     const post = await fetchPost(postId)

docs/router/framework/react/overview.md

@@ -42,7 +42,7 @@ It's probably no surprise at this point that picking a router is so important th
 
 **Does this mean that TanStack Router is a framework?**
 
-TanStack Router itself is not a "framework" in the traditional sense, since it doesn't address a few other common full-stack concerns. However TanStack Router has been designed to be upgradable to a full-stack framework when used in conjunction with other tools that address bundling, deployments, and server-side-specific functionality. This is why we are currently developing [TanStack Start](https://tanstack.com/start), a full-stack framework that is built on top of TanStack Router and tools like Nitro, and Vite.
+TanStack Router itself is not a "framework" in the traditional sense, since it doesn't address a few other common full-stack concerns. However TanStack Router has been designed to be upgradable to a full-stack framework when used in conjunction with other tools that address bundling, deployments, and server-side-specific functionality. This is why we are currently developing [TanStack Start](https://tanstack.com/start), a full-stack framework that is built on top of TanStack Router and Vite.
 
 For a deeper dive on the history of TanStack Router, feel free to read [TanStack Router's History](./decisions-on-dx.md#tanstack-routers-origin-story).