Closed y0hnn closed 3 years ago
Same here
Same here, seems like trigger does not run at all. There is nothing logged in the console. exit={{ trigger: ({ node, e, exit, entry }) => console.log(node, e, exit, entry) // here node refers to the DOM node of the exiting page }}
Yeah 100% broke for me yesterday when updating all my packages. Narrowed it down to the gatsby version. Running on 2.24.67 makes things work again. I was using a simple "cover" background color transition. Now, the colour being passed in was correct, but the swipe itself never used that colour. So although it didn't break animations, it definitely stopped doing what it was supposed to do.
For me all of my custom transitions totally broke and nothing fired same as @riginosk
Hey everyone, I think I have a fix for this. 🤞 might take me a little bit to release it but I'm working on it
Hey yall! I just published a fix in gatsby-plugin-transition-link@1.20.4
! Let me know if you run into any problems with it :)
Update to gatsby-plugin-transition-link@1.20.5
because I broke builds in the last version 😆
FFS Tyler 🤦🏼♂️
Kind regards,
Joe
On 17 Oct 2020, at 18:33, Tyler Barnes notifications@github.com wrote:
Update to gatsby-plugin-transition-link@1.20.5 because I broke builds in the last version 😆
— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.
Hey,
It seems something in Gatsby@2.24.70 broke the animations. Maybe related to https://github.com/gatsbyjs/gatsby/pull/27261 ?