Can non-TS artefacts (images, MD files, etc.) be added to the "deno build" bundle?
Is there a way to add non-TS artifacts (images, MD-files, etc.) to the "deno build" bundle?
4 Replies
I wasn't able to find the answer to your question in the official Deno documentation regarding the inclusion of non-TS artifacts like images and Markdown files in the "deno build" bundle.
However, based on your message, there are no obvious syntax errors or mistakes. It's worth noting that the
deno build command is designed to compile TypeScript and JavaScript into a single executable, and it typically does not include assets like images or Markdown files.
Since this advice is not based on the Deno documentation, I recommend double-checking the accuracy of this information and exploring the Deno manual or other resources for any potential updates or community-driven solutions that might address your needs.deno build doesnt exist. What bundle are you talking about exactly?ah, I mistyped: I meant “deno compile…”.
I have an app which reads artefacts off the disk. When I run it with Deno and Deno Deploy normally — everything works fine. However, the complied by “deno compile” binary fails trying to open files from the file system in a location, where Deno executor unzips and runs that compiled file.
This package seems to fit: https://jsr.io/@nfnitloop/deno-embedder. There's also an older project, I don't know if it works anymore, but maybe it could still prove helpful: https://github.com/mandarineorg/leaf
GitHub
GitHub - mandarineorg/leaf: A fake file system for Deno binaries
A fake file system for Deno binaries. Contribute to mandarineorg/leaf development by creating an account on GitHub.