Tomáš Hübelbauer

This is related to `bun build`, but what about the `bun index.ts` case - no build step, just Bun running a file at runtime with some plugins in the Bunfig...

I am not attempting to create a custom protocol, I have an existing custom protocol which I am looking to bridge Bun into supporting. It is possible that runtime plugins...

Whatever is on the other side of the import is dynamic, I can't bake it in or use a static `data:` protocol import.

Thanks for the PR, I noted in the repro repo README and in my initial post in this issue that I can't use `build.module` because it doesn't take a regex....

I cannot write out all the specifiers I am expecting as the specifiers are dynamic, not known at compile time.

With `build.module` being able to return virtual modules, there is no need to map every module specifier to a path on the disk, especially if the module isn't backed by...

Here's the simplest case I can think of to demonstrate `build.module` with a regex: ``` import { plugin } from "bun"; await plugin({ name: "test", async setup(build) { console.log("Plugin loaded!",...

@rhuanbarreto that seems to be about an HTTP2 client (making HTTP2 calls from Bun) not a server.

@guest271314 Not waiting for Bun to add stuff it currently doesn't have is great! Anyone can mix and match what's at their disposal at any one time. This ticket is...

Note, this issue is also happening when SSGing RSC route. See #42760 for details. In that case, the issue behaves a bit differently in that instead of the route path...