Henric Persson
Henric Persson
Try setting the `fireOnRapidScroll` prop to false.
That sound like a good start, although we'd have to make a few substantial changes to the component in order to remove the dependency on a DOM. Here are just...
This is tricky. I agree that it would be nice to get rid of the `add-module-exports` dependency. But doing so would break a lot of applications (because they would have...
Are you processing node_modules through babel by any chance? `babel-plugin-add-module-exports` is a [dev dependency that we use in the build process](https://github.com/brigade/react-waypoint/blob/8e149164afa6e58548a4235d5f2aa0fff1951fc2/package.json#L39). When you have installed `react-waypoint`, you shouldn't have to...
I see. For now I think you should exclude `react-waypoint` from being loaded by babel. Something like ```js { test: /\.js$/, use: { loader: babelLoader, }, exclude: [/node_modules\/react-waypoint/], }, ```...
Glad you found a workaround!
Alright. I changed the title to better reflect what the goal of this thread is.
@robhuzzey I see, thanks for reporting. I wonder if things would just work ™️ if the `.babelrc` file wasn't there? Would you mind removing it manually (something like `rm node_modules/react-waypoint/.babelrc`)...
Switching to github actions sounds like a good idea. 👍
It's hard to know what's going on without also knowing the css styles for the elements. The most likely thing is that the waypoint is consistently "visible" in the scrollable...