URGENT : Cloudinary Image Upload Editor Disappeared Post Builder SDK upgrade to V3

Technical Questions
1

Hey Builder team ,

This is super URGENT !!!
We are facing an issue in LIVE & pages are broken because of this .

We really need your help on our current situation on priority that appeared in front of us post this BUILDER SDK upgrade . We followed the instructions given in this doc to upgrade the api version + SDK .

Below are the issues we are facing post upgrade.

  1. We found that our image component which used to have cloudinary editor in it , is now completely gone from all the docs . Here is a test doc .

  2. So far we have seen 1 live page going down because of this . However , all the other pages still work but we can’t uploda images from cloudinary as the option is gone . I think , it is some sort of caching that still keep other pages alive .

We are also thinking about reverting the upgrade , but don’t know the down side of that which is why we are reluctant to do that currently . So we need your URGENT help in fixing this and bring back the cloudinary editor with our customized options that we had .

Additional info :

Builder react sdk version (@builder.io/react) : “2.1.0”

kroma-builderio-widget : “1.3.0”

We are also okay to give our current code base access if that helps . it’s in NEXT JS . Let us know if you need any more info .

2

Hello @SrittamMishra,

Would you be able to upgrade to our latest SDK version?

"@builder.io/react": "^3.1.1",
"@builder.io/widgets": "^1.2.24",

Additionally, providing us with the image component code will help us investigate and address the issue promptly.

3

@manish-sharma ,

I know that we are in multiple tickets on this , you can choose to stick to any one .

I am getting below error while upgrading @builder.io/react :

error /Users/srittammishra/Desktop/projects/Kroma-Headless/node_modules/isolated-vm: Command failed.
Exit code: 1
Command: prebuild-install || (node-gyp rebuild --release -j 4 && node-gyp clean)
Arguments: 
Directory: /Users/srittammishra/Desktop/projects/Kroma-Headless/node_modules/isolated-vm
Output:
prebuild-install warn install No prebuilt binaries found (target=16.0.0 runtime=node arch=arm64 libc= platform=darwin)
gyp info it worked if it ends with ok
gyp info using node-gyp@7.1.2
gyp info using node@16.0.0 | darwin | arm64
gyp info find Python using Python version 3.9.6 found at "/Library/Developer/CommandLineTools/usr/bin/python3"
gyp http GET https://nodejs.org/download/release/v16.0.0/node-v16.0.0-headers.tar.gz
gyp http 200 https://nodejs.org/download/release/v16.0.0/node-v16.0.0-headers.tar.gz
gyp http GET https://nodejs.org/download/release/v16.0.0/SHASUMS256.txt
gyp http 200 https://nodejs.org/download/release/v16.0.0/SHASUMS256.txt

===========

Secondly , which package is this @builder.io/widgets ?
I am not using any such package and also i am new to this project . I can see this package is being used kroma-builderio-widgets .

Here is a screenshot of my folder strutchur and package.json.

Screenshot 2024-01-16 at 6.15.43 PM
Screenshot 2024-01-16 at 6.15.43 PM836×1800 112 KB

Package.json :

{
  "name": "kroma-headless",
  "version": "0.1.0",
  "private": true,
  "scripts": {
    "dev": "next dev",
    "build": "next build && next export && next build",
    "start": "next start",
    "lint": "next lint",
    "server": "NODE_OPTIONS='--inspect' next dev",
    "bundleAanalyser": "ANALYZE=true yarn build"
  },
  "dependencies": {
    "@builder.io/react": "2.1.0",
    "@fortawesome/fontawesome-svg-core": "^6.1.2",
    "@fortawesome/free-regular-svg-icons": "^6.1.2",
    "@fortawesome/free-solid-svg-icons": "^6.1.2",
    "@fortawesome/react-fontawesome": "^0.2.0",
    "@sentry/nextjs": "7.77.0",
    "@tanstack/react-query": "^4.0.10",
    "accoutrement": "^3.0.1",
    "algoliasearch": "^4.14.2",
    "aos": "^2.3.4",
    "axios": "^0.27.2",
    "body-scroll-lock": "^4.0.0-beta.0",
    "classnames": "^2.3.2",
    "cookies-next": "^2.1.1",
    "graphql": "^16.5.0",
    "graphql-request": "^4.3.0",
    "hamburgers": "^1.2.1",
    "kroma-builderio-widgets": "1.3.0",
    "next": "12.1.6",
    "react": "18.2.0",
    "react-dom": "18.2.0",
    "react-fittext": "^1.0.0",
    "react-infinite-scroll-component": "^6.1.0",
    "react-player": "^2.12.0",
    "react-responsive": "^9.0.0-beta.10",
    "react-slick": "^0.29.0",
    "sass": "^1.62.1",
    "slick-carousel": "^1.8.1",
    "slugify": "^1.6.5"
  },
  "devDependencies": {
    "@next/bundle-analyzer": "^13.5.1",
    "autoprefixer": "^10.4.7",
    "axios": "^0.27.2",
    "eslint": "8.18.0",
    "eslint-config-next": "12.1.6",
    "postcss": "^8.4.14",
    "postcss-loader": "^7.0.0",
    "swiper": "^9.0.5",
    "tailwindcss": "^3.1.5",
    "xmlhttprequest": "^1.8.0"
  }
}
4

Hello @SrittamMishra,

You don’t have to use the widgets package “@builder.io/widgets”, it’s not required.