Adam Coulombe

I use a similar approach as @nathobson to get the element with a`ref`, but I use class components and initiate `locomotiveScroll` in `componentDidMount`. https://codesandbox.io/s/proud-resonance-ou1rz The main thing to just be...

@aaadamgo i guess use the destroy method ``` componentWillUnmount(){ myScroller.destroy() } ```

It’s possible that the destroy method only cleans up the events. Take a look at the source: https://github.com/locomotivemtl/locomotive-scroll/blob/4240f83c01d57b60256189ad5960163c3ec5e197/src/scripts/Core.js#L211 Because of this you may also need to manually remove elements that...

> Has anyone managed to get this to destroy completely. > > @adamcoulombe i think i'm experiencing what you stated, when i leave the page with the locomotive-scroll on i'm...

Here is an updated example with 3.3.5 showing usage with react and using the `update()` method when the route changes. I did find that you need to call it after...

> Unfortunately, with the Gatsby case, it still seems like I have to call `update()` on intervals to ensure that the scroll works correctly for all kinds of pages. >...

Await constant needs to go in an async function in order for it to work like so: ``` async function getTweets(){ const { data } = await client.get('tweets', { ids:...

Thanks for your help. I submitted PR #3 to maybe help others get started, the whole babel/webpack workflow was not something I was very familiar with when I found your...

My GIFs arent looping either. Would be nice if this was the default setting. Thanks, love the app!

this patch made scrolling glitchy for me