No package found which can optimize images.
See original GitHub issuelqip-loader is installed but i’m getting this error on server console.
Here is my next.config
module.exports = withPlugins([optimizedImages, withSass]);
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:13 (3 by maintainers)
Top Results From Across the Web
Can't set up next-optimized-images - Stack Overflow
I'm trying to set up next-optimized-images 2.6.2 with next js 9.3.6, ... I have also installed the following Optimization Packages
Read more >next-optimized-images - npm
Automatically optimize images used in next.js projects (jpeg, png, gif, svg).. Latest version: 2.6.2, last published: 2 years ago.
Read more >Next.js 10 Image Optimization and next-optimized-images
Let's build a page to show a list of images without image optimization as a control. In the control page, we put raw...
Read more >next-export-optimize-images-zabanshenas-edition - npm - Snyk
Based on project statistics from the GitHub repository for the npm package next-export-optimize-images-zabanshenas-edition, we found that it ...
Read more >Optimize Images | Cloudinary
You can often deliver images at less than half of the original file size with little to no visually noticeable difference. Optimizing image...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hi @cyrilwanner 👋, I have these installed;
Sorry for the late reply, I had some exams last week and wasn’t active on github because of this.
@jecassis thank you very much for the hint with node 12. It was indeed the problem that you have described.
I just published a patch on npm which should fix this problem. Can you install
v2.5.2
and check if the error is now gone? Thanks!