I'd just like to clarify what you are requesting.

It's important to understand that Replete does not run as a single process. Rather, there is a "master" process controlling several "padawan" processes, one for each REPL environment:

   +------------------------------------------+
   |                                          |
   |               Your program               |
   |         (such as a text editor)          |
   |                                          |
   +----------------+-------------------------+
                    |        ^
                    |        |
   Command messages |        | Result messages
                    |        |
                    V        |
+----------------------------+--------------------+
|                                                 |
|         Replete (deno or node process)          |
|                                                 |
+---------+----------------+--------------+-------+
          |                |              |
          v                v              v
+---------------+ +---------------+ +--------------+
|Browser padawan| |Node.js padawan| | Deno padawan |
|(browser tab)  | |(node process) | |(deno process)|
+---------------+ +---------------+ +--------------+

The code for the master process was originally written to run on Node.js. Later, I discovered that the same code ran on Deno, thanks to Deno's excellent Node.js compatibility layer. Deno, unlike Node.js, is capable of loading code directly over the network, removing the most complicated step of Replete's installation, so it became the preferred runtime. As you rightly point out, this convenience came at a cost: a dependency on Deno.

The only way the master can run in a Bun process is if Bun implements the required Node.js APIs.

Now, the padawans. Obviously Deno code must be evaluated in a Deno process, and Node.js code in a Node.js process. But because the interface between master and padawan is loose, any combination of master and padawan is allowed. For example, the following configurations all work:

a Node.js master and Deno padawan
a Deno master and a Node.js padawan
a Deno master and Deno padawan

It is also possible to disable REPLs that are not required, simply by omitting the --which_node or --which_deno arguments.

I am optimistic that I can write a Bun padawan. But unless Bun's Node.js compatibility layer is sufficiently comprehensive, the dependency on Deno or Node.js for the master process will remain.

Does your team have Node.js installed? If so, it should be possible for you to avoid installing Deno whilst still using Replete to evaluate Bun code.

Support for Bun #9

Description

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions