begoon
Can non-TS artefacts (images, MD files, etc.) be added to the "deno build" bundle?
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.
6 replies
thread 'tokio-runtime-worker' has overflowed its stack
Submitted a bug report -- https://github.com/denoland/deno/issues/24325
6 replies
thread 'tokio-runtime-worker' has overflowed its stack
I have just realised that in the dockerfile, there is a version of deno which I didn't upgrade. The application DOES work with that version:
deno --version
deno 1.43.1 (release, aarch64-apple-darwin)
v8 12.4.254.12
typescript 5.4.3
I have downgraded my main CLI deno to 1.43.1 and... the crash is gone.
Something had been broken between 1.43.1 and 1.44.4.
6 replies
Outgoing connection over TLS (port 465) from the deno deployment is failing
So far, I removed the email-sending part from my Deno Deploy deployment and instead created an endpoint at Vercel, which allows sending emails. That endpoint is in SvelteKit/TS, facilitating the "nodemailer" library. Now, my application at Deno Deploy calls that endpoint to send email instead of doing directly.
10 replies
Outgoing connection over TLS (port 465) from the deno deployment is failing
@suchislife801 I use 1.6.0. The code when running from my local development computer works normally. I even discovered the issue only when I deployed.
In theory, the edge runtime, which Deno Deploy hosting implements, should not allow socket connectivity at all. Only fetch-based network calls are allowed in edge functions. But in this case the code should fail with a missing function error or something. But here the error seems to come from the OS network layer, when the socket connection had in fact been attempted.
10 replies