Deno v1.27

• windmill

  38 8,463 10.0 Svelte

  Open-source developer platform to turn scripts into workflows and UIs. Fastest workflow engine (5x vs Airflow). Open-source alternative to Airplane and Retool.

  

  We bet big on deno with Windmill (OSS platform to turn scripts into internal UI and workflows) [1][2] and are extremely pleased. The language design choices made and the performances/caching strategies are a perfect match. However, the compatibility with npm was the most requested feature. Before the compatibility mode with npm was released, we were about to build a completely separate mode of execute based on node. This solves it very elegantly.

  Also super excited about the lsp improvements. I believe we are the only project to have a webeditor that features lsp integration with deno in the web (to test, go on [3], New Script -> Next, it works really well). It's very pleasant to work with and make the webeditor experience match closely a local dev setup. We are super excited about the improvements and I am about to try tonight if we can have the inline hints work with monaco. As we are fully open-source, one can see how we are able to pull it off [4][5].

  [1]: https://windmill.dev

• language-server-protocol

  18 10,657 8.7 HTML

  Defines a common protocol for language servers.

  

  Our editor integration is completely editor agnostic. Deno implements the Language Server Protocol [1], which essentially all editors support. Because of this the new inlay hints feature, is supported on all editors that support inlay hints and use our LSP integration. The Jetbrains integration for Deno uses our LSP, but I don't know if they support inlay hints yet.

  You can find docs on using Deno LSP with other editors here: https://deno.land/manual/getting_started/setup_your_environm...

  [1]: https://microsoft.github.io/language-server-protocol/

• WorkOS

  workos.com

  sponsored

  The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

  

• just.billywhizz.io

  0 3 6.3 HTML

  website

  

  My on-the-sidelines take is:

  Bun seems most promising to me, because it's chasing amazing performance _and_ widespread adoption.

  Like Just-JS has amazing performance [1], but the author is "just" (a very amazing/talented) benchmark hacker and not necessarily trying/wanting to put in the effort to have "a node replacement" and/or extend his Techempower-specific optimizations into APIs/libraries that would affect the performance day-to-day business apps.

  Deno is kinda :shrug: b/c its original "great security" pitch doesn't really matter to anyone who runs in containers.

  [1]: https://github.com/just-js/just.billywhizz.io/issues/3

• deno

  46 92,799 9.9 Rust

  A modern runtime for JavaScript and TypeScript.

  

  No real support, just a placeholder on their roadmap: https://github.com/denoland/deno/issues/1739

• deno_std

  1 1,038 0.0 TypeScript

  Discontinued deno standard modules

  

  At least for the ones related to trees, it's just a renaming. Below is a link to the PR. When I initially implemented these trees, I chose the names BSTree and RBTree to keep the names short. I'm guessing the person that proposed renaming them did so to make it more obvious what they are.

  https://github.com/denoland/deno_std/pull/2400

  The standard library is separate from the runtime. It wouldn't break backward compatibility if you were to update. For example, if you were importing RBTree and upgraded Deno to the latest release, it would keep working just fine. You would only really need to switch to using RedBlackTree instead if there was a change made to it that you wanted.

  I think the only time you would need to update your standard module imports to be able to use newer versions of the Deno runtime if the standard module were depending on runtime APIs that have a breaking change.

• fresh

  23 11,832 9.7 TypeScript

  The next-gen web framework.

  

• deploy_feedback

  7 73 2.2

  For reporting issues with Deno Deploy

  

  I'd say deno, because they've already established a proper ecosystem since day one, has a working usage such as Deno Deploy[0] and Fresh[1], and already addresses some issues about distribution issue on Node, while bun still acts like a replacement for Node.

  [0]:https://deno.com/deploy

• InfluxDB

  www.influxdata.com

  sponsored

  Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

  

Suggest a related project