oak VS pkg

Are you using Oak? If not you should check it out https://oakserver.github.io/oak/

oak

oak - web framework

Hey @cjonas, I'm a developer on Supabase Edge Functions team. We do have plans to improve the current database trigger behavior. Will share more updates on this in the coming months.

Can you explain what do you mean by template URLs? Do you mean route params like `/v1/functions/users/:id`? If so, you can use a framework like Oak[1] to handle them. Edge Functions will make the full path including querystring available to the router.

Source maps, is it broken during local dev or when you deploy the function? Also, by broken you mean in a stack trace the file / line numbers aren't accurate?

[1] https://github.com/oakserver/oak

Oak framework [Website]

If you don’t want to use a full stack framework, you can develop your frontend and backend separately. With Cloudflare, you can serve your frontend and static assets with Pages or Workers Sites. With Deno Deploy, you can serve static assets from the filesystem. As for the backend, you probably want to use an HTTP framework such as Sunder (if you target Cloudflare Workers), oak, Router, or Sift (if you target Deno Deploy).

Oak server - middleware framework for Deno's native HTTP server. 'destjs' use it under the hood.

The issue about resources vanishing does happen, e.g. this example, meaning things like CI outages / non-deterministic builds / etc are possible, especially under a decentralized package hosting model.

Here's an example that uses Oak, a web application framework for Deno, to create a basic web server:

I don't remember the details, and cannot find my notes on vercel/pkg. But looking at https://github.com/vercel/pkg right now I see the project has been deprecated in favour of single-executable-applications

> Standalone CLI — we haven’t worked on a standalone CLI for the new engine yet, but will absolutely have it before the v4.0 release.

This part is the most exciting to me. Given the rest of the release announcement, I'm assuming this means that it'll be built in Rust rather than embed Node. While I'm not a Rust zealot of anything, I'm very partial to not embedding Node. Particularly when it depends on using Vercel's now-abandoned pkg[1] tool.`

[1] https://github.com/vercel/pkg

The npm package called "pkg" seems to be the standard for packaging NodeJS applications

https://www.npmjs.com/package/pkg

Unfortunately you also need to bundle all your code into a single file for it to work, but you can use any bundler (webpack, parcel, etc) you want at least

Nodejs support for "single executable applications" is getting there - this issue below is preventing wider adoption at the moment:

"The single executable application feature currently only supports running a single embedded script using the CommonJS module system."

https://nodejs.org/api/single-executable-applications.html

Should be an awesome game changer for node.js when the feature gets rounded out.

Also check out vercel's `pkg`: https://github.com/vercel/pkg/issues/1291

Yes, you can. Check out pkg for a fun option, which can package up your project and Node.js into a single executable.

Further, you could experiment with the pkg tool that allows you to package up Node JS, your source, and your dependencies into one single executable for easy distribution.

package the app using https://github.com/vercel/pkg and use a smaller base image like alpine, busybox or even scratch (if possible)

Check this thread: https://github.com/vercel/pkg/issues/1685