My apologies to the pnpm faithful (myself included). The `patch-package` module didn't work for me, but that does not mean that you can't patch with pnpm. Pnpm has native functionality for patching, as does yarn, with the `pnpm patch` or `yarn patch` commands. Though these commands vary in their options and use.
My first thought was, huh why didn't Jack know until recently about patching packages and then my second thought was exactly what you are pointing out. I use this at least once in every project, using pnpm natively. I hope he adds a little floating note to the video pointing out his mistake. Also spent way too much time on this video because of its non-descriptive title. Should've scrubbed.
Thanks for the clarification. This was an honest mistake. I tried patch-package with pnpm and it didn't work, but I didn't go looking for the native patch functionality within pnpm. I'll add some text to the video and an expository comment.
Infinite Red is the sponsor of this weeks video. Infinite Red is an React-Native consultancy. They have been in the React-Native community from the start. And they have built amazing framework like Ignite and MLKit to support React-Native devs. If you are looking for some help with your React-Native application, give them a look! You'll get a great consultancy and you'll help this channel! infinite.red/
Remembering this. I wanted to use KY with React Native project I was working on. I didn't work out of the box, used "patch-package" to fix what caused the issue.
Because if a package needs patching that's usually an indication that it shouldn't be used in the first place. If you ever run into a situation where you feel you need to patch a package, there's almost always a better up-to-date package or DIY solution. If you do decide to patch a package you increase the maintenance overhead for every package you patch. I don't know why patching is a standard part of the dev flow for react native devs, my best assumption is that react native is fragile relative to react so it can take more tinkering to get things working across devices and systems.
@@_y7ya That makes sense, thanks. Yeah there are a lot of moving pieces with changes on the iOS and Android sides that a particular package may not have kept up with resulting in it not working for certain versions of React Native leading devs to utilize patches to get their apps running until updates are released.
@@_y7ya I am also an RN developer. patch-package is usually used for legacy projects. A year ago in the company I got a project on a very old version of RN. 1/4 of the packages had not been updated for a while, and since there was no budget to rewrite those funkconalities we patch-packaged those packages to run on the latest RN. It is not a beautiful solution, but for large projects it is a savior.
Instead of using a dedicated library to do patches you can use the existing patching functionality in all package managers (except npm) E.g. bun patch bad-library
Not a react native dev but I’ve used patch package a brunch for tooling that doesnt behave well in our monorepo at work. I understand click bait titles are a part of getting reach on RUclips but nothing secret about me and got a bit annoyed at the scrubbing it took to find out what this was about.
It will show a warning message and attempt to apply the changes in the patch file. If the patch file is no longer applicable due to changes in the source file, it will error.
Even the low end phones have 8GB RAM. I use Capacitor, let user's mobile browser handle that thing. Also I'm done with styling RN components. I don't like the ecosystem at all.
![Megan Thee Stallion - Bigger In Texas [Official Video]](http://i.ytimg.com/vi/QxTkZTLWdo4/mqdefault.jpg)
My apologies to the pnpm faithful (myself included). The `patch-package` module didn't work for me, but that does not mean that you can't patch with pnpm. Pnpm has native functionality for patching, as does yarn, with the `pnpm patch` or `yarn patch` commands. Though these commands vary in their options and use.
This DOES work with pnpm. Actually, pnpm supports this feature natively: pnpm patch
My first thought was, huh why didn't Jack know until recently about patching packages and then my second thought was exactly what you are pointing out. I use this at least once in every project, using pnpm natively. I hope he adds a little floating note to the video pointing out his mistake. Also spent way too much time on this video because of its non-descriptive title. Should've scrubbed.
Pnpm patch seem to be a better alternative
Thanks for the clarification. This was an honest mistake. I tried patch-package with pnpm and it didn't work, but I didn't go looking for the native patch functionality within pnpm. I'll add some text to the video and an expository comment.
Got excited for a second for RN content, but turns out its SSR content, sadge ;_;
Infinite Red is the sponsor of this weeks video. Infinite Red is an React-Native consultancy. They have been in the React-Native community from the start. And they have built amazing framework like Ignite and MLKit to support React-Native devs. If you are looking for some help with your React-Native application, give them a look! You'll get a great consultancy and you'll help this channel! infinite.red/
💜 Thanks Jack, you're the best. Great vid too! patch-package is an essential tool IMO
Good stuff! We heavily use RN.
The irony of installing yet another package to fix a broken package
Remembering this. I wanted to use KY with React Native project I was working on. I didn't work out of the box, used "patch-package" to fix what caused the issue.
Nice! I've had to do this a couple times in the past. Very useful!
I'm a RN dev. I always thought this was a JS/React ecosystem thing, not just RN 🤯
It's more of an ecosystem thing, but I've only seen folks use it in RN-land.
try doing that with minified code
@jherr Hi Jack, could you please share your custom oh-my-posh json? it looks fantastic. Thank you
As someone who is primarily a RN dev, why would there be hesitation in using patch-package from those in React-land?
Because if a package needs patching that's usually an indication that it shouldn't be used in the first place. If you ever run into a situation where you feel you need to patch a package, there's almost always a better up-to-date package or DIY solution. If you do decide to patch a package you increase the maintenance overhead for every package you patch.
I don't know why patching is a standard part of the dev flow for react native devs, my best assumption is that react native is fragile relative to react so it can take more tinkering to get things working across devices and systems.
@@_y7ya That makes sense, thanks. Yeah there are a lot of moving pieces with changes on the iOS and Android sides that a particular package may not have kept up with resulting in it not working for certain versions of React Native leading devs to utilize patches to get their apps running until updates are released.
@@_y7ya I am also an RN developer. patch-package is usually used for legacy projects. A year ago in the company I got a project on a very old version of RN. 1/4 of the packages had not been updated for a while, and since there was no budget to rewrite those funkconalities we patch-packaged those packages to run on the latest RN. It is not a beautiful solution, but for large projects it is a savior.
Instead of using a dedicated library to do patches you can use the existing patching functionality in all package managers (except npm)
E.g. bun patch bad-library
Someone else pointed out that pnpm already has that feature
Great stuff… but how did u get those icons in your terminal, especially the react one ? Never seen that before
Its some MAC bullshit thing. You cant get this on windows because windows terminals sucks. You will spend hours to make one work.
Wow this is great
This video comes after I thought of creating a mobile App (I'm a frontend dev), and researched React Native yesterday. Is it fate?
Not a react native dev but I’ve used patch package a brunch for tooling that doesnt behave well in our monorepo at work.
I understand click bait titles are a part of getting reach on RUclips but nothing secret about me and got a bit annoyed at the scrubbing it took to find out what this was about.
what if you npm update a patched package
It will show a warning message and attempt to apply the changes in the patch file. If the patch file is no longer applicable due to changes in the source file, it will error.
Audio is kinda out of sync
It's not secret anymore🥴
Even the low end phones have 8GB RAM.
I use Capacitor, let user's mobile browser handle that thing.
Also I'm done with styling RN components. I don't like the ecosystem at all.
ekhm... this comment seems to off tthe topic...
L video
Agreed. Patching a package for SSR purposes is such a terrible use case.