Vercel/NextJS build fails indicating Elysia is not installed

[rekkisomo]

What version of Elysia is running?

1.1.24

What platform is your computer?

Microsoft Windows NT 10.0.26120.0 x64

What steps can reproduce the bug?

Admittedly, our setup is unconventional. As we wanted the eden types to be usable by people who don't have access to our server's repository, we have the types built by the server then sent to the repo. This works (and correctly typed) on the client when running the next dev server, as well as passing linting by intellij, but fails linting when being built.

1. Install Wolfbite-Labs/voyagesdk-ts as a dependency
2. Do the following in a Next.JS project:

const { vg } = new VoyageSDK()

const server= vg.server.describeServer.get()
//       ^? returns { availableUserDomains: [], ...} fine, with IDE typing
//       but building fails indicating no Elysia installed, even though it is.

3. Build using next build

What is the expected behavior?

No response

What do you see instead?

Type error Property 'pack' does not exist on type '"Please install Elysia before using Eden" & { supabase?: SupabaseClient<any, any, any> | undefined; }'.

IntelliJ linting reports:

Additional information

elysia-autoload is being used as well, but don't believe its an issue there

Have you try removing the node_modules and bun.lockb and try again yet?

Yes

[rekkisomo]

Using Eden types directly from the server (import {ServerTypes} from "../some-server" instead from the build results in the same issue.