Bun runtime: "Requested module is not instantiated yet"

Help
23

Apologies for the delay, the Bun team told us that this can happen when using top-level await along with require and cyclic dependencies. Any minimal reproduction would be appreciated to help getting this fixed.

1 Like
24

I can confirm for me, the issue was using path aliases in tsconfig.json. My project is Bun + Elysia, and by removing baseUrl and paths from tsconfig everything works fine, and I get the joys of import foo from “../../../lib/foo/bar.js” now :smile: but at least it works

25

Found a workaround for the Requested module is not instantiated yet error when using ConvexHttpClient with the Bun runtime on Vercel.

The issue seems tied to how the Bun runtime preset handles module resolution in Serverless Functions. I fixed this by switching the execution environment to the Node.js runtime while keeping the Bun toolchain for the rest of the flow.

The Fix:

  1. Use @elysiajs/node (or your framework’s Node adapter).

  2. Set vercel.json to use @vercel/node for the build.

  3. Use strict ESM imports (include .js extensions) in your TS files so the Node runtime can resolve them.

This setup allows you to keep using Bun for local dev and fast installs, but utilizes the stable Node.js runtime in production to avoid the Convex instantiation bug.

26

So, is it strictly forbidden to use aliases in Bun projects? In my case, I’m using Elysia with absolute paths (“@/…”). This is necessary for good code readability. I ran into this error about four hours ago, but there’s very little documentation on this specific issue.

27

Bug Update: “Requested module is not instantiated yet” with Convex

I have identified that this error specifically occurs when using ConvexHttpClient from the convex package (v1.32.0).

The Root Cause:

The issue stems from a circular module graph within the convex/browser ESM entry points. Specifically:

  1. convex/dist/esm/browser/simple_client.js imports from ./index.js.

  2. index.js re-exports simple_client.js.

While this resolves correctly in Node.js and local Bun environments, the Vercel Bun Runtime (Beta) fails during the module linking phase, leading to the TypeError: Requested module is not instantiated yet.

Official Issue Tracked Here:

I have opened a formal issue with the Convex team to see if the module graph can be flattened:

https://github.com/get-convex/convex-backend/issues/394

Current Workaround:

To unblock your deployment, switch from the Bun runtime to the Node.js runtime on Vercel:

  1. Use @elysiajs/node (or your framework’s Node adapter).

  2. Update vercel.json to use the @vercel/node builder.

  3. Important: Ensure all internal relative imports in your TypeScript files use explicit .js extensions (e.g., import { routes } from './routes.js') so the Node ESM loader can resolve them without the “module not found” error.

28

I initially suspected my path aliases (@/...) were causing this, but after some deep diving, I found that wasn’t the case. Path aliases are generally fine in Bun/Elysia projects as long as they are mapped correctly in your tsconfig.json.

In my case, the Requested module is not instantiated yet error was actually triggered by the convex package (@1.32.0). There is a circular dependency in their ESM entry point (convex/browser) that the Vercel Bun runtime (Beta) struggles to link, even though it works fine in local Bun and Node.js environments.

If you are seeing this error and using Convex (or other libraries with complex barrel exports), the aliases might be a red herring. The real issue is likely the runtime’s ESM linker.