Replies: 5 comments
-
|
I'm also having the same issue, so I'm very curious. |
Beta Was this translation helpful? Give feedback.
-
|
I suggest wrap AnimatePresence inside layout |
Beta Was this translation helpful? Give feedback.
-
|
Running into the same issue. |
Beta Was this translation helpful? Give feedback.
-
|
anyone found something on this? |
Beta Was this translation helpful? Give feedback.
-
|
Sorry for the late reply. I was in a situation like this when I tried to roll-in and roll-out a changing text on my company website. After some time I found that the best and seems like only solution is to use: console.warn = () => {}This will override the warn method that throws warnings to an empty one, not making framer (or any other component) log any. 1 - Build Tool (recommended)in a deployment pipeline you can use the build tool to drop the console. terserOptions: {
compress: {
drop_console: true,
},
...
}or NextJS const nextConfig = {
compiler: {
removeConsole: true,
},
...
};2 - PipelineYou could technically add the override dynamically but I don't really like this solution as it is very "dirty". Hope that helps! P.s. I haven't yet tried to switch the ENV="" variable to PRODUCTION/PROD to see if Motion still throws warnings in productions, but that could also be a viable option. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
So, I'm doing some stuff which framer motion doesn't really like and print a warning:
However, it all works fine, I tested it multiple times and it works well. Is there any way to get rid of this warning in console? I don't really want to change layout because of it
Beta Was this translation helpful? Give feedback.
All reactions