Broken CldImage - element type is invalid

[artmadeit]

I created a very simple react component and the CldImage seems to be broken, it was working when using pages no for some reason with the app directory seems to be broken:

here is the code

my package.json contains a lot of packages:

{
  "name": "admin-front",
  "version": "0.1.0",
  "private": true,
  "scripts": {
    "dev": "next dev",
    "build": "next build",
    "start": "next start",
    "lint": "next lint"
  },
  "dependencies": {
    "@date-io/date-fns": "^2.16.0",
    "@emotion/css": "^11.10.0",
    "@emotion/react": "^11.9.3",
    "@emotion/styled": "^11.9.3",
    "@mui/icons-material": "^5.8.4",
    "@mui/material": "^5.9.0",
    "@mui/x-data-grid": "^5.13.1",
    "@mui/x-date-pickers": "^5.0.1",
    "@uppy/core": "^3.3.0",
    "@uppy/dashboard": "^3.4.1",
    "@uppy/drag-drop": "^3.0.2",
    "@uppy/file-input": "^3.0.2",
    "@uppy/locales": "^3.2.2",
    "@uppy/progress-bar": "^3.0.2",
    "@uppy/react": "^3.1.2",
    "@uppy/status-bar": "^3.2.1",
    "@uppy/xhr-upload": "^3.3.1",
    "axios": "^0.27.2",
    "camelcase-keys": "^8.0.2",
    "date-fns": "^2.30.0",
    "escape-html": "^1.0.3",
    "formik": "^2.2.9",
    "formik-mui": "^5.0.0-alpha.0",
    "formik-mui-x-date-pickers": "^0.0.1",
    "mui-tel-input": "^2.0.4",
    "next": "^13.4.9",
    "next-cloudinary": "^4.13.1",
    "qs": "^6.11.0",
    "react": "^18.2.0",
    "react-dom": "^18.2.0",
    "slate": "^0.82.1",
    "slate-history": "^0.66.0",
    "slate-hyperscript": "^0.77.0",
    "slate-react": "^0.83.1",
    "swr": "^2.1.3",
    "use-debounce": "^9.0.4",
    "yup": "^0.32.11",
    "yup-es": "^1.0.8"
  },
  "devDependencies": {
    "@types/escape-html": "^1.0.2",
    "@types/node": "20.2.3",
    "@types/qs": "^6.9.7",
    "@types/react": "18.2.7",
    "@types/react-dom": "18.2.4",
    "eslint": "8.20.0",
    "eslint-config-next": "^13.4.3",
    "prettier": "2.7.1",
    "typescript": "5.0.4"
  }
}

[colbyfayock]

Hey @artmadeit please try the latest version from a few hours ago 4.14.1 which has a workaround for an issue introduced in nextjs #227

[artmadeit]

super fast thanksss