Next.js Adventures: Some Blasphemy Against the Holy Image Component
1–4 of 4 posts
Re: Next.js Adventures: Some Blasphemy Against the Holy Image Component
#2If you believe that the component is the finest solution for handling images ever invented, then I suggest you stop reading right now and go find other interesting stuff.
Re: Next.js Adventures: Some Blasphemy Against the Holy Image Component
#3I’ve felt your pain. We run a Next app on Heroku and we had to disable such component because it was making the app consume in average 500mb of RAM. Our app doesn’t do anything special nor we have many visitors.
Re: Next.js Adventures: Some Blasphemy Against the Holy Image Component
#4I’ve felt your pain. We run a Next app on Heroku and we had to disable such component because it was making the app consume in average 500mb of RAM. Our app doesn’t do anything special nor we have many visitors.
Yeah, that's my other pain point - the higher usage of CPU & RAM.