contributing-tests
bun
contributing-tests | bun | |
---|---|---|
2 | 291 | |
1,103 | 70,962 | |
0.0% | 2.6% | |
10.0 | 10.0 | |
about 3 years ago | 6 days ago | |
Zig | ||
- | - |
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.
contributing-tests
-
Jest not recommended to be used in Node.js due to instanceOf operator issues
https://github.com/testdouble/contributing-tests/wiki/London...
-
Are you in favor of small functions/clean code or opposed to it?
I hope I'm not coming across as patronizing here, I'm sure you understand the single object responsibility principle here I just thought I'd explain my approach. There's some really great resources on testing available on the TestDouble git page: https://github.com/testdouble/contributing-tests/wiki/Test-Driven-Development it'd be worth reading about London School TDD and how it might benefit your approach here :)
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?
oletus - Minimal ECMAScript Module test runner
vite - Next generation frontend tooling. It's fast!
react-ssd1306 - 📟 A React Renderer for SSD1306 OLED chip on Raspberry Pi.
GORM - The fantastic ORM library for Golang, aims to be developer friendly
nvm - Node Version Manager - POSIX-compliant bash script to manage multiple active node.js versions
fastify - Fast and low overhead web framework, for Node.js
go-pg - Golang ORM with focus on PostgreSQL features and performance
deno - A modern runtime for JavaScript and TypeScript.
just - the only javascript runtime to hit no.1 on techempower :fire:
Vue.js - This is the repo for Vue 2. For Vue 3, go to https://github.com/vuejs/core
Svelte - Cybernetically enhanced web apps
pgx - PostgreSQL driver and toolkit for Go