Unlike some of my other posts, this one is going to be straight-forward.
I'll cover some of the less-frequently-used browser devtools features tha...
For further actions, you may consider blocking this person and/or reporting abuse
Best to the point article🚀🚀🚀🚀!!!
@jayantbh Next article on using performance profiler or react profiler for debugging infinite re-renders of components.
While writing this one, I actually thought that a post about using the browser and react profiler might be a good next option.
Let's go!!
Been building stuff in React/Next for the past 3 years and I still didn't know more than half of these tricks! Super Article @jayantbh
Thanks, my dude!
The console one is quite surprising to me. I have debugged using browser, but there is always new thing to learn. Lighthouse is a open-source project I believe.
Yeah! Technically Chromium is the open source one, and lighthouse is now part of it. It used to be a separate thing previously, but now it's in the browsers too.
github.com/GoogleChrome/lighthouse
For anyone interested in that repo.
Super informative article
Thank you, @ayush2390!
Gotta love the fight between the Next.js Image component sizing and the Lighthouse first-contentful (FCP) paint tug-of-war.
Nice writeup, good reading points!
That's a fight that ultimately benefits the devs, and the users ✨✨
If you hate node.js debugging, try Errsole , Its the only solution who can help you to resolve the node.js issue in just minutes.
I wouldn't say anyone "loves" debugging. XD
But making it as painless as possible is definitely a priority. 😂
True, fixing bugs is a pain in the azz, especially on vacation days. 😂
Debugged and fixed my real comment. 😛
Haha! That's more relatable! ❤️
Hey great post
Also can you add do an performance profiling specific post ? It would be very useful
Interesting to see some interest around it.
@cvam01 mentioned something along the same lines too. Might actually do that!