dnt

for some packages but not others. * Figure out how to get Lodash working with TypeScript. It's not simple. [0] * Use a hack to get typeorm with sqlite working. [1] * Try out `deno compile`, only to determine that it somehow works differently than `deno run`. My project simply wouldn't work with `deno compile`, probably because my project has some system dependencies that don't get properly linked/included. * Setup my scripts to properly lint my project. Deno has formatting/linting built-in, but it's split across many commands with different usages. For example, I can run `deno fmt` to format my entire project, but I have to give Deno a path to run `check` or `lint`, e.g. `deno check src/index.ts ` * Patch a third-party library that was setting an HTTP header to `null`. NodeJS handles this case just fine, but Deno throws an error [2]. * Attempt to build my UI (astro + react) with Deno. It seems some people have gotten this partially working, but I gave up and stayed on NodeJS for building my UI. This led to me: * Using dnt [3] to build a Deno package for consumption with NodeJS/npm frontend. This was actually surprisingly simple; kudos to the author of the dnt library. After all of that work, I finally was able to use Deno in my project. It was really cool! Unfortunately, both VS Code and IntelliJ with Deno are essentially unusable [4]. Or, at least, unacceptably slow compared to what I had with NodeJS. [-1]: https://github.com/shepherdjerred/glitter-boys/tree/sj/deno [0]: https://stackoverflow.com/a/66073607 [1]: https://github.com/typeorm/typeorm/issues/6123#issuecomment-... [2]: https://github.com/Sansossio/twisted/issues/97 [3]: https://github.com/denoland/dnt [4]: https://github.com/denoland/vscode_deno/issues/895