-
Notifications
You must be signed in to change notification settings - Fork 86
missing "jimp" dependency #85
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@jjojo hey! so sorry for this. this is because of our initial next/image support and for some reason our internal logic won't find jimp despite it being dependencies of next-on-netlify and the plugin.
this is an excellent question and something we need to address. to resolve your issue though - can you install |
@jjojo actually i think you should be able to pin your plugin version by installing the plugin into your project at whatever version. this will also solve the jimp issue. |
hey all - heads up that i reverted next/image support to avoid any more people seeing this jimp error until we can resolve it. please track here if you want to know when support is back! :) netlify/next-on-netlify#143 |
Thanks for the suggestions @lindsaylevine I'll look into it! I really liked the smooth deployment, and it is a great plugin! |
@jjojo totally understand! :) apologies again for the breaking changes!!! will be much more vigilant in the future especially as we transition to auto-installing this plugin for new next.js sites 👀 all feedback is welcome! |
related to #84, I think
[email protected]
introduced image support, which relies onjimp
. however, this plugin is set to@2.7.2
and that is somehow causing the next image support to run, butjimp
is not installed as a dependencyI don't know how or why, but wanted to track this here
The text was updated successfully, but these errors were encountered: