I should update the README w/ how this compares to the newly-added --include option in deno compile.
See: denoland/deno#26939
And: denoland/deno#20885
I want to do some testing to make sure I'm understand how it works before I document things, but as it stands, it looks like the new --include option has some weaknesses vs. deno-embedder:
- Only works with
deno compile not deno run jsr:…?
- Works by hijacking the
Deno.read*() functions to return embedded data instead of reading from the FS. (Doesn't this make reads ambiguous? Or is import.meta.dirname returning something like embedded:// so it's unambiguous?)
- Requires granting
--allow-read. (Avoiding that need is a big part of the purpose of deno-embedder. But I suppose this is moot since you're limited to deno compile anyway.)
I should update the README w/ how this compares to the newly-added
--includeoption indeno compile.See: denoland/deno#26939
And: denoland/deno#20885
I want to do some testing to make sure I'm understand how it works before I document things, but as it stands, it looks like the new
--includeoption has some weaknesses vs. deno-embedder:deno compilenotdeno run jsr:…?Deno.read*()functions to return embedded data instead of reading from the FS. (Doesn't this make reads ambiguous? Or isimport.meta.dirnamereturning something likeembedded://so it's unambiguous?)--allow-read. (Avoiding that need is a big part of the purpose of deno-embedder. But I suppose this is moot since you're limited todeno compileanyway.)