websockets
bun
websockets | bun | |
---|---|---|
5 | 290 | |
41 | 70,962 | |
- | 2.6% | |
3.5 | 10.0 | |
about 2 months ago | 2 days ago | |
HTML | Zig | |
GNU General Public License v3.0 or later | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
websockets
-
JPEG XL and the Pareto Front
It's so frustrating how the chromium team is ending up as a gatekeeper of the Internet by pick and choosing what gets developed or not.
I recently come across another issue pertaining to the chromium team being not budging on their decisions, despite pressure from the community and an RFC backing it up - in my case custom headers in WebSocket handshakes, that are supported by other Javascript runtimes like node and bun, but the chromium maintainer just disagrees with it - https://github.com/whatwg/websockets/issues/16#issuecomment-...
- WebSocket still does not support setting the Authorization header
-
Kubernetes API smuggles its authorization tokens via fake WebSocket protocols
The anchor got stripped. The comment is here: https://github.com/whatwg/websockets/issues/16#issuecomment-...
The commit on Github is here: https://github.com/kubernetes/kubernetes/commit/714f97d7baf4...
-
Bun v0.5
Really appreciating bun's ability to set custom WebSocket headers.
Incidentally, what's up with the resistance against this from the standards maintainers? [1]
The request exists since 2017, there are tons of use cases and developer interest, but implementation is refused on technicalities. What gives?
[1] https://github.com/whatwg/websockets/issues/16
bun
-
Node Test Runner vs Bun Test Runner (with TypeScript and ESM)
It has a decent compatibility with both Jest and Vitest's APIs (you can track progress here so you can use it as almost a drop-in replacement for either. Just as Node's, it has describe/it, mock, test and others, but with the expect syntax (which I find more readable). For example:
-
SPA-Like Navigation Preserving Web Component State
In this third and final article in the series on HTML Streaming, we will explore the practical implementation of the Diff DOM Streaming library in web browsing. This approach will allow any website using web components to retain its state during browsing. We will discuss in detail how to achieve this step by step using VanillaJS and Bun.
-
React Server Components Example with Next.js
At Node Conference 2023, Jarred Sumner (creator of Bun) showed a demo of server components in Bun, so there is at least partial support in that ecosystem. The Bun repo provides bun-plugin-server-components as the official plugin for server components. And while I haven’t looked at it in-depth, Marz claims to be a “React Server Components Framework for Bun”.
- Bun – A fast all-in-one JavaScript runtime
-
From Node to Bun: A New Dawn for JavaScript Engines?
Continuously evolving, Bun is currently optimized for MacOS and Linux, with ongoing efforts towards Windows compatibility. Tailored for resource-constrained environments like serverless functions, it emerges as an ideal solution. The Bun team is committed to achieving comprehensive Node.js compatibility and seamless integration with prevalent frameworks. For those intrigued by Bun's potential and want to give it a try, more information is available on its website at https://bun.sh/.
-
Bun - The One Tool for All Your JavaScript/Typescript Project's Needs?
Let’s say you are interested in learning more about Bun and probably give it a try. Bun has a website, where you can learn more about Bun and its features (including all the benchmark data captured in this issue), and here is the link.
-
Bun 1.1
Looks like it, it seems the 2% are mostly odd platform specific issues that the authors' did not deem very important (my assumption for the release happening anyway). AFAIK this[1] PR tries to fix them.
[1]: https://github.com/oven-sh/bun/pull/9729
-
Bun-ify Your Project
Bun has a solution for it. First of all, it already has a list of trusted dependencies. For them, Bun will execute all necessary scripts by default. Otherwise, you can add it to trustedDependecies in your package.json file. In Bun community usage of trustedDependencies is a hot topic. There are several suggestions on how to improve it.
-
I have created a small anti-depression script
Install Node.js (or Bun, or Deno, or whatever JS runtime you prefer) if it's not there
-
JSR: The JavaScript Registry
I think maybe I was unclear. I'm talking about writing libraries that abstract across these differences and provide a single API, as sibling describes. I already know it's possible. I made a simple filesystem abstraction here[0] and a very simple HTTP library that uses it here[1]. They both work in Node/Deno and the browser. Unfortunately I ran into issues with Bun's slice implementation[2]. But I suspect there's a much better way of detecting and using the different backends.
[0]: https://github.com/waygate-io/fs-js
[1]: https://github.com/waygate-io/http-js
[2]: https://github.com/oven-sh/bun/issues/7057
What are some alternatives?
glob-match - An extremely fast glob matching library in Rust.
vite - Next generation frontend tooling. It's fast!
libuv - Go to
GORM - The fantastic ORM library for Golang, aims to be developer friendly
zig - General-purpose programming language and toolchain for maintaining robust, optimal, and reusable software.
nvm - Node Version Manager - POSIX-compliant bash script to manage multiple active node.js versions
node - Node.js JavaScript runtime ✨🐢🚀✨
fastify - Fast and low overhead web framework, for Node.js
ziglings - Learn the Zig programming language by fixing tiny broken programs.
go-pg - Golang ORM with focus on PostgreSQL features and performance
stdlib - ✨ Standard library for JavaScript and Node.js. ✨
deno - A modern runtime for JavaScript and TypeScript.