Modeled after deno compile, it would be cool to be able to "compile" an Ink project into a single executable. Deno achieves this by producing binary of the form:
original deno binary + bundled JavaScript string + magic number (0xD3N0) + uint64 pointer to start of JS
We can do something very similar. To do this, we first need to write an Ink bundler that can compile Ink projects into a single Ink source file, or a "bundle" file.
There's no great reason why this feature has to be a part of the Ink project per se, as opposed to a separate project that does both the compile and bundle tasks.
Modeled after deno compile, it would be cool to be able to "compile" an Ink project into a single executable. Deno achieves this by producing binary of the form:
We can do something very similar. To do this, we first need to write an Ink bundler that can compile Ink projects into a single Ink source file, or a "bundle" file.
There's no great reason why this feature has to be a part of the Ink project per se, as opposed to a separate project that does both the compile and bundle tasks.