Cannot find module 'jimp' #143
Comments
|
hey @ctsimpouris ! apologies about this. yes, jimp is required for our next/image support, but no, you shouldn't have to install it yourself. can you do me a favor and try using https://github.com/netlify/netlify-plugin-nextjs instead of the standard next-on-netlify configuration you're using? if you do try it, make sure you uninstall jimp before re-attempting a build/deploy. |
|
I am receiving the same issue even with your suggestion. I have no issues building locally. |
|
Installing critter as a dev dependancy has fixed the issue and my site loads fine. Thank you! |
|
hey @gregg-cbs! critters is a separate issue from jimp, believe it or not 😆 what next version are you using? the critters issue should be resolved now per #103 (comment) |
|
Hi @lindsaylevine I'm also unable to deploy due to my Netlify deployment being unable to find jimp: This is with Next version 10.0.5 and after installing https://github.com/netlify/netlify-plugin-nextjs through the UI about 20 minutes ago. |
|
@lindsaylevine this is a fresh site linked up to GitHub, not deployed through the CLI at all if that helps. Apart from Next version being slightly different to another site I deployed without any issues roughly a month ago (10.0.3 vs 10.0.5), I can't see any differences between the apps in terms of config/versions/deploy method etc. |
|
Creating a netlify.toml file containing: and installing |
|
@james-work-account hey james! so sorry about this. we're not sure why our functions bundling logic can't find jimp when it's a dependency of both the plugin and next-on-netlify. the fact that you installed the plugin as a dev dependency and it worked is good info for us; that means simply having it in the plugin on runs does not affect the bundling at all aka why the UI wouldn't work (because the one-click UI won't install it to your project). your project has to have it as a dependency or peer dependency, which shouldn't be the case. i'll be rolling this back later, i think, instead of telling everyone to temporarily install the plugin or jimp. appreciate the patience and the helpful comments! <3 |
|
Yeah i Had the same issue and installed @netlify/plugin-nextjs then added the toml file and now it deployed successfully. |
|
hey all, just released next-on-netlify with the revert. headed to update the plugin now. won't have answers to the jimp issue til tuesday earliest. apologies once again! |
lindsaylevine
added
type: bug
|
I ended up using Heroku instead for a number of reasons. Not due to this, this was easy to solve but due to other Netlify limitations. I am happy with my decision. Thanks to the Author/Collaborator for a super quick response and action plan. Cant be easy managing side repos, life and your job. Respect. |
|
@gregg-cbs hey, thanks for your transparency! no worries at all, totally understand. would love to hear if you're willing to share the limitations you mentioned! will be helpful to pass along to the team :) and thanks for the kind words!! for everyone else - the internal fix has been released for this so i'm going to make an attempt to put the next/image support back in. will keep you updated! |
Describe the bug
Unfortunately no repo can be provided
Versions
Bug started to appear on Wednesday, 13/1/2021 after this commit.
Log
After this commit, the same code stopped being able to be deployed to Netlify with the following log
while also function
next_image.jsstarted to appear out of the blue. Due toCannot find module 'jimp', I proceed and installed dependencyjimp, making the deployment process work as expected. However, this is something that definitely within my repo is not used so far.The text was updated successfully, but these errors were encountered: