publint VS oak

Creating npm packages can be challenging. We've seen many tools in this domain, and I encourage you to try dnt. With dnt, I was finally able to pass the package.json linter, which is no small achievement (try jotai, redux, vite).

Only regret is not mentioning https://publint.dev which is similar in many ways (and also great -> just didn't know about it at the time). Maybe we gotta find the publint people/person and do an episode with them??

There are many quirks related to this however, for example if you use "types" it should always be the first entry in your exports, and if you use "default" it should always be the last entry in your exports. Package exports are easy to mess up, and get wrong. Thankfully, there's a really nice project called publint that helps you with things like these.

Not currently, but missing deps is planned under https://github.com/bluwy/publint/issues/13 which should be doable once the infrastructure is done. Deprecated dependencies are probably out of scope for now as that package could technically still work, and it avoids a fetch to npm.

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: