composable-functions VS denoify

Instead of adding multiple try/catch statements, we'll establish a pattern to deal with exceptions. For that, let me introduce you to Composable Functions, a library we created to make function composition easy and safe.

composable-functions

Last week, I started a Twitter thread about this and asked for help from some friends and TS experts. I was working on our library composable-functions on an issue by @danielweinmann that was experiencing this problem.

As already mentioned dnt might help you if you are willing to have deno as your primary development environment. I work in a project like this and the deno tooling is great. I don't even need a package.json since dnt will generate it for me.

If you’re building packages/libraries for the community to use you can take a look at Denoify. It’s a project that aims to change some of your files automatically when migrating and make it easier to maintain the project for both npm and deno.land/x.

I do Node-first packages and use https://github.com/garronej/denoify to produce deno-compatible code. (example: https://github.com/mxxii/leac )

You can use https://github.com/garronej/denoify for Node-first packages.

Or use ts-patten it's comming to Deno soon (thanks to Denoify).

So, if you tried Denoify in the past and it didn't work for you, maybe it will now. If you need a hand, I'm happy to help. Just ask anything on the newly opened discussion section of the github repo.

It has zero dependencies so was very easy to dual publish on both npm and deno.land using denoify. Literally just needed to add the .ts extension to imports.