patch-package
bun
Our great sponsors
patch-package | bun | |
---|---|---|
65 | 288 | |
9,953 | 70,488 | |
- | 2.9% | |
6.3 | 10.0 | |
11 days ago | 6 days ago | |
TypeScript | Zig | |
MIT License | - |
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.
patch-package
-
Finding Stars and Affirmations in the Sky with Three.js for Ayra Starr
In order to allow users to use their device as a controller to adjust the position of the camera and find stars, I use the depreciated DeviceOrientationControls by patching it back into Three. In order for DeviceOrientationControls to function, we need access the user to grant access to their device's orientation. I attempt to gain access to this, alongside their camera, during a previous step of the UX using a custom composable I wrote for this purpose. You can see that permission step in the mockup video above. Once this permission is granted, we can initialize our DeviceOrienationControls with a single line.
-
TypeScript NPM Packages Done Right
If you use Yarn, there’s the `yarn patch` command [1], which lets you maintain patches for your dependencies. Even though I try to upstream patches wherever possible, sometimes you just want to apply a quick patch and move on, especially if the dependency is poorly maintained or even worse, deeply nested in your dependency hierarchy. I use `yarn patch` regularly, it’s one of the main reasons why I moved to Yarn in the first place.
If you’re not using Yarn, there seems to be a similar thing on npm, `patch-package`. [2] I never had to use that though.
[1]: https://yarnpkg.com/cli/patch
[2]: https://www.npmjs.com/package/patch-package
- Fix broken node modules instantly
-
How to ignore an error , that happens in a node modules library ?
You can use patch-package to edit the part of the library.
- Jest not recommended to be used in Node.js due to instanceOf operator issues
-
Getting kinda stuck with a build error, any help much appreciated
patch-package
-
Credentials Leak with Knex
NPM doesn't have a patch command, but you can use patch-package to achieve the same result.
-
Why react native is so shit
If there's issue ticket discussing it and someone can fix it, ask for patch file and use patch-package to patch it
- Eas local build, how skip npm install
-
Invariant Violation: ViewPropTypes has been removed from React Native. Migrate to ViewPropTypes exported from 'deprecated-react-native-prop-types'.
You can try this (I highly recommend you to use the Patch Package library to track changes on any external library that you are using. (https://www.npmjs.com/package/patch-package)
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?
husky - Git hooks made easy 🐶 woof!
vite - Next generation frontend tooling. It's fast!
node-pre-gyp - Node.js tool for easy binary deployment of C++ addons
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
vercel - Develop. Preview. Ship.
fastify - Fast and low overhead web framework, for Node.js
Faker.js - What really happened with Aaron Swartz?
go-pg - Golang ORM with focus on PostgreSQL features and performance
basic-ftp - FTP client for Node.js, supports FTPS over TLS, passive mode over IPv6, async/await, and Typescript.
deno - A modern runtime for JavaScript and TypeScript.