Actual use case for JavaScript PROXY! 

ONE OF THE BESTEXPLANATION THABK YOU❤

First js vido in my life that i actually enjoyd.

Awesome video Kevin! It is a very helpful use-case. Thank you so much for this

Great video! I've found of a use-case for proxies before, but this seems really useful.

Very nice tutorial! Definitely an underrated channel..

This was a great example and use case, thank you!

I'll definitely share this one, truly amazing content.

Nice video. It is inaccurate to say the original commits are “deleted” when performing a rebase. They still exist and can be accessed and even recovered if you know their original hashes. They do end up in an orphaned state and can be “cleaned up” under certain circumstances in the future.

This is super helpful, thank you

Amazing video, you just earned yourself a new subscriber!

Great video, thanks for the info!

Great explanation, thanks

Great Video ! Thanks SIr !

Great Vedio, very helpful

Thx very good video

For me it seems more obvious and simple just to add to the `fontSized` object a property `__proto__: legacyFontSizes`. Then `extreaLagre` and `extraSmall` won't appear by iteration, but not break the legacy code as e.g. with an attempt of getting `extraSmall` the `gigantic` will be returned. I still find your video very clear-cut and helpful, thank you! But can you please answer if in this particular case my solution is inferior to the approach with `Proxy`?

Can I ask what font do you use in the video?

You can literally just set the forntsizes extralarge to the new translation. The proxy isnt doing anything magical. FontSizes.ExtraLarge.Value When you have to update your code for depricated values you can just set the value from the object. What is it that a proxy can do that cant be done in a simple return value or if then statements?

Why we can't do something like const FontSize = { ....... tiny: tiny, get extraSmall() { console.warn('warning...') return this.tiny } ....... }