react-reveal icon indicating copy to clipboard operation
react-reveal copied to clipboard

Warning: Legacy context API has been detected within a strict-mode tree.

Open rayantovi opened this issue 4 years ago • 26 comments

`Learn more about this warning here: https://fb.me/react-legacy-context

in RevealBase (created by Slide)

in Slide (at App.js:44)

in nav (at App.js:33)

in header (at App.js:32)

in Header (at src/index.js:9)

in StrictMode (at src/index.js:8)

`

Re-installed react-reveal and still have this error

Annotation 2020-03-26 214038

rayantovi avatar Mar 26 '20 18:03 rayantovi

This is my code

Annotation 2020-03-26 214324

rayantovi avatar Mar 26 '20 18:03 rayantovi

@jgil-r That does not fix the issue. It just hides it.

mihaic195 avatar May 14 '20 18:05 mihaic195

Facing the same issue

AbhiJoshi32 avatar Jul 06 '20 20:07 AbhiJoshi32

Is there a way to ignore this error?

coltenkrauter avatar Jul 08 '20 00:07 coltenkrauter

Same issue here.

wildlifechorus avatar Jul 21 '20 08:07 wildlifechorus

Same issue here. Is this repository still maintained? The last publish was 2 years ago and there are pull requests that date back months. Can we get some help @rnosov ?

jefelewis avatar Jul 23 '20 05:07 jefelewis

This library looks good. but we need to fix this issue asap. Is there any way to fix it?

Eagle930705 avatar Jul 31 '20 19:07 Eagle930705

Up

JtawRobot avatar Sep 03 '20 10:09 JtawRobot

Bump

hafezoa avatar Sep 23 '20 03:09 hafezoa

bump

tuan43 avatar Oct 17 '20 20:10 tuan43

I'm having same issue.... I guess the only workaround is to use another library...

innakostiuk avatar Oct 20 '20 06:10 innakostiuk

Up

KilMer56 avatar Nov 10 '20 09:11 KilMer56

Facing the same issue. Any chances of a resolution anytime soon?

nefario7 avatar Nov 30 '20 12:11 nefario7

Any updates ?

ankit1738 avatar Dec 30 '20 12:12 ankit1738

Bump

Polliny avatar Jan 13 '21 19:01 Polliny

Bump!

aelainelong avatar Jan 30 '21 18:01 aelainelong

Bump

dtello2012 avatar Feb 05 '21 16:02 dtello2012

Facing same issue

mohzys23 avatar Feb 11 '21 22:02 mohzys23

Facing the same issue. any solution?

dayoolacodes avatar Feb 15 '21 17:02 dayoolacodes

No solution yet bro

On Mon, Feb 15, 2021, 5:31 PM Dayo Ayoola [email protected] wrote:

Facing the same issue. any solution?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/rnosov/react-reveal/issues/89#issuecomment-779364048, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJPIJDLYTDO6AVBHUXTWL6DS7FK67ANCNFSM4LUOPMPA .

mohzys23 avatar Feb 15 '21 17:02 mohzys23

No solution yet bro On Mon, Feb 15, 2021, 5:31 PM Dayo Ayoola @.***> wrote: Facing the same issue. any solution? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#89 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJPIJDLYTDO6AVBHUXTWL6DS7FK67ANCNFSM4LUOPMPA .

Know any alternative that can be used?

dayoolacodes avatar Feb 15 '21 17:02 dayoolacodes

Can this issue be fixed quickly? I rely on this for one animation and would rather not have this error in my console all the time. If this issue persists i might consider extracting the code from the component and making my own.

cryptoAlgorithm avatar May 24 '21 09:05 cryptoAlgorithm

Facing same issue. Any Update ?

image

Rafat97 avatar Jul 09 '21 08:07 Rafat97

No solution yet bro On Mon, Feb 15, 2021, 5:31 PM Dayo Ayoola @.***> wrote: Facing the same issue. any solution? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#89 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJPIJDLYTDO6AVBHUXTWL6DS7FK67ANCNFSM4LUOPMPA .

Know any alternative that can be used?

Use React Awesome Reveal instead.

thirashapw avatar Aug 19 '21 10:08 thirashapw

Getting the same error. Is this package maintained anymore? Anyone have a clue if there is something similar out there or have started working on something similar?

jpatterson933 avatar Oct 05 '21 03:10 jpatterson933

well, changing <React.Strictmode> to <React.Fragment> will certainely remove the error from console........

5HATIM5 avatar Jan 27 '22 07:01 5HATIM5