New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using v0.1.17 caused a heroku build to hang indefinitely. #76
Comments
Thanks for your feedback, can you provide the logs from heroku during deployment? I think that would help us to understand this kind of issue. 🤔 |
|
Interesting, actually it seems that your build just took too much, so I don't think the problem is from including this library. How different is the log when it succeeds? |
As a side note, we're actually hosting our production app on Heroku and using the v0.1.17 library without issues. |
Here's a successful build, the only difference is the successful build uses Thanks for maintaining pulltorefresh.js
|
Definitely a good issue, I can't figure out why the change of library would have side-effects on building steps. I'm not heavy ruby/heroku user but afaik it should build locally too, it does? |
Bug report
I was working on a mobile web app in Rails and I found this package, which I think is fantastic by the way. I built my features on v0.1.17 and everything was fine in Dev and CI, but when deploying to Heroku the build hung then timed out. Normally I wouldn't bring this to your attention, but downgrading this package, the one from
NPM
btw, to v0.1.16 fixed my build.Let me know if you need more details, I can readily reproduce the problem.
Current behavior:
Building with Rails/webpacker/webpack on heroku hangs indefinitely on v0.1.17 from
NPM
but not v0.1.16.Expected behavior:
Not hanging the webpack build
JSFiddle URL for demo with bug:
N/A
Browsers affected:
N/A
The text was updated successfully, but these errors were encountered: