Data Serialization and Deserialization override

[jadedevin13]

Which project does this relate to?

Router

Describe the bug

router/docs/router/framework/react/guide/ssr.md

Line 204 in 5412a94

## Data Serialization

This part of the guide is no longer true. Also hoping that we can override serialization on the server function please.

Your Example Website or App

N/A

Steps to Reproduce the Bug or Issue

N/A

Expected behavior

N/A

Screenshots or Videos

No response

Platform

• OS: [e.g. macOS, Windows, Linux]
• Browser: [e.g. Chrome, Safari, Firefox]
• Version: [e.g. 91.1]

Additional context

No response

[schiller-manuel]

can you explain what you would use the serialization override for?

[jadedevin13]

Hi @schiller-manuel.

There's a use case where I'm sending Uint8Array from the server to client and vice versa but it becomes just an array of int. I see sveltejs/devalue#69 supports this.

[m9tdev]

Would be great if this is added to Start! I now have to convert Prisma's Decimal and some bigints manually which is a lot of boilerplate for the amount of fields I have.

[m9tdev]

I've actually found how to do it in Start! (not sure about SSR when using Router without Start)

I've created src/start.ts with this content:

import { createStart } from "@tanstack/react-start";
import { createSerializationAdapter } from "@tanstack/react-router";
import { Decimal } from "decimal.js";

export const decimalAdapter = createSerializationAdapter({
  key: "decimal",
  test: (value: unknown): value is Decimal => Decimal.isDecimal(value),
  toSerializable: (decimal) => decimal.toNumber(),
  fromSerializable: (value) => new Decimal(value),
});

export const startInstance = createStart(() => {
  return {
    serializationAdapters: [decimalAdapter, bigIntAdapter],
  };
});

[LadyBluenotes]

This is supported now through createStart:

export const startInstance = createStart(() => ({
  serializationAdapters: [decimalAdapter],
}))

The adapters are used for both SSR hydration and server-function serialization. The Decimal setup in the latest comment is the right approach for custom types :)