Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Cloudinary field doesn't work on Node 13.3.2
See original GitHub issueBug report
Not sure if this is upstream or not…
Trying to use the cloudinary field on Node 13.3.2. It gives the error (node:50514) [DEP0135] DeprecationWarning: ReadStream.prototype.open() is deprecated in the console and a ‘nested error’ in the Admin UI.
Reverting back to node 12.13 fixes it for now
System information
- OS: Mac OS Catalina
Issue Analytics
- State:
- Created 4 years ago
- Reactions:2
- Comments:16 (16 by maintainers)
Top Results From Across the Web
Cloudinary field doesn't work on Node 13.3.2 #2101 - GitHub
Trying to use the cloudinary field on Node 13.3.2. It gives the error (node:50514) [DEP0135] DeprecationWarning: ReadStream.prototype.open() ...
Read more >Node.js SDK - Cloudinary
Cloudinary's Node.js SDK provides simple, yet comprehensive image and video upload, transformation, optimization, and delivery capabilities ...
Read more >Cloudinary Node.js SDK Quick Start
Quickly get started uploading, managing, transforming and delivering optimized images and videos with Cloudinary in your Node.js dev ...
Read more >Upload API Reference - Cloudinary
Note: The public ID for images does not include a file extension. transformation, String, A transformation to run on all the pages before ......
Read more >Correct way of uploading from buffer? - Cloudinary Support
Hi,. I have been researching for hours and I found out two solutions (using NodeJs), so that I can pass a buffer instead...
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 Free
Top 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
Fixed in
@keystonejs/keystone@18.0.0.Fixed it! I was using npm, not yarn, which doesn’t have resolutions.
So the fix is to use the above resolution with your package.json, but add this script:
"preinstall": "npx npm-force-resolutions"