Difference between dev and build

[lionelhorn]

Hello,

Thanks for your previous help. Continuing on my exploration:

I'm trying to use Deepkit runtime types (https://deepkit.io/documentation/runtime-types) with react-server.

In a gist, deepkit will transform the original source code to add type information so reflection and other features will be available at runtime.

// index.tsx

import "./index.css";
import {ReflectionClass} from "@deepkit/type";

export default function Index() {
  interface User {
    username: string;
    first: string;
    last: string;
    age: number;
  }

  const r = ReflectionClass.from<User>();
  const properties = r.getPropertyNames();

  return (
    <>{JSON.stringify(properties)}</>
  );
}

In dev mode, everything works. The following code (according to vite inspect plugin) gets transpiled (via a deepkit vite plugin) to

import "./index.css";
import { ReflectionClass } from "@deepkit/type";

export default function Index() {
    const __ΩUser = ['username', 'first', 'last', 'age', 'User', 'P&4!&4"&4#\'4$Mw%y'];
    const r = (ReflectionClass.from.Ω = [[() => __ΩUser, 'n!']], ReflectionClass.from());
    const properties = r.getPropertyNames();
    return (<>{JSON.stringify(properties)}</>);
}
Index.__type = ['Index', 'P"/!'];

//# sourceMappingURL=index.jsx.map

In build + start mode, code breaks and errors. The following code is built ./index.mjs

import {Fragment as t, jsx as e} from "react/jsx-runtime";
import {ReflectionClass as o} from "@deepkit/type";

function n() {
  const r = o.from().getPropertyNames();
  return e(t, {children: JSON.stringify(r)})
}

n.__type = ["Index", 'P"/!'];
export {n as default};

For instance the following line has been removed by something in the build pipeline

const __ΩUser = ['username', 'first', 'last', 'age', 'User', 'P&4!&4"&4#\'4$Mw%y'];

Any suggestions on how to troubleshoot the issue?

[lionelhorn]

Added repro https://github.com/lionelhorn/reproductions/tree/main/lazarv-reactserver-deepkit

[lazarv]

Thanks for the repro, it was really helpful to understand how you would like to use Deepkit with the framework. Deepkit worked for me in my own repro without any issue and then checked your repro where you provided the tsConfig path directly into the plugin.

There was a missing Vite configuration flag in build that caused the vite.config.ts to be loaded multiple times and that caused to resolve the tsconfig.json differently and so it messed up the result of the Deepkit transform.

Please update to the latest version, it should work now!

You can also remove "@lazarv/react-server/types" from your tsconfig.json, it is no longer needed since a few weeks ago.

[lionelhorn]

Confirmed. Working now :)

[github-actions]

This issue has been locked since it has been closed for more than 30 days.

If you have found a concrete bug or regression related to it, please open a new bug report with a reproduction against the latest version of @lazarv/react-server. If you have any other comments you should create a new discussion.