React does not recognize the `fetchPriority` prop on a DOM element.
Answered
Cornish Rex posted this in #help-forum
Cornish RexOP
Hello, i get this weird error when using next/image, i couldnt find any solution to this on the internet maybe is just a bug
i use :
"react": "^18",
"react-dom": "^18",
"next": "14.2.3",
i use :
"react": "^18",
"react-dom": "^18",
"next": "14.2.3",
Answered by joulev
This is a React bug. Downgrade to 18.2.0. In your case, in package.json change both
https://github.com/vercel/next.js/issues/65161
This bug is not relevant to sharp.
^18 of react and react-dom to 18.2.0 without the ^ then run the install command again.https://github.com/vercel/next.js/issues/65161
This bug is not relevant to sharp.
55 Replies
@Naeemgg Where are you injecting the `fetchPriority` prop?
Cornish RexOP
i dont thats the thing
i dont use it anywhere
can you show your package.json?
Cornish RexOP
1 sec
@Naeemgg this warning appeared when i update the next js
try installing
"react": "^18.3.1",
"react-dom": "^18.3.1",it should work
Cornish RexOP
alr let me try
@Cornish Rex <@782907171721314315> this warning appeared when i update the next js
its likely possible that next v14.2 requires react v18.3
Cornish RexOP
still not
@Naeemgg should i downgrade ig?
what was the previous next version when things were good?
Cornish RexOP
let me check
And are you sure its coming with
Image component?@Naeemgg what was the previous next version when things were good?
Cornish RexOP
v13 something
@Naeemgg And are you sure its coming with `Image` component?
Cornish RexOP
wdym?
The source of the error
Cornish RexOP
the Image component works fine i just get that warning/error
Cornish RexOP
thats what is weird
You mentioned in the question its because
next/imageCornish RexOP
yes
when i dont use Image component that doesnt appear
anyway, looks like some of your dependencies are still using next v13
Cornish RexOP
ig i should just ignore it lol
it doesnt affect anything its just annoying
try
priority prop in ImageCornish RexOP
i did
same thing
if it gets rid of it
Ohh
Cornish RexOP
ig its incompatibility issue
you have
sharp installed?Cornish RexOP
nope
install it as dev dep
but if you're deploying on vercel then install v0.33.3
npm i -D sharp@0.33.3
Cornish RexOP
lel
madness
ig there is nothing we can do
Its very much weird behavior
if its not bothering you just ignore it for now maybe when you update the packages in future it will go away with its own
Cornish RexOP
yea thats what i was thinking
ty anyway
for ur time and effort
< 3
Cornish RexOP
@Cornish Rex Hello, i get this weird error when using next/image, i couldnt find any solution to this on the internet maybe is just a bug
i use :
"react": "^18",
"react-dom": "^18",
"next": "14.2.3",
This is a React bug. Downgrade to 18.2.0. In your case, in package.json change both
https://github.com/vercel/next.js/issues/65161
This bug is not relevant to sharp.
^18 of react and react-dom to 18.2.0 without the ^ then run the install command again.https://github.com/vercel/next.js/issues/65161
This bug is not relevant to sharp.
Answer
@joulev This is a React bug. Downgrade to 18.2.0. In your case, in package.json change both `^18` of react and react-dom to `18.2.0` without the `^` then run the install command again.
https://github.com/vercel/next.js/issues/65161
This bug is not relevant to sharp.
Cornish RexOP
i love you, worked tysm