-
Notifications
You must be signed in to change notification settings - Fork 1
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
recycling this deprecated name on npm? #2
Comments
@WebReflection A while ago I've already passed this module to @rauchg. @rauchg do you need this (I don't see anything published)? If not, then I think we should be happy to pass it to @WebReflection (assuming I'll maintain the rights to publish updates to v0.4 version). |
ping for @rauchg ... by any chance you can hand over the repo to me? |
@WebReflection I took that to email (it'll probably work better), therefore closing this issue |
I wanted to contact you via PVT on twitter but for some reason you don't follow me so here I am.
You flagged this as deprecated, mind passing this name to me so I can bump a new major and push a completely different library borrowing
next
name?The TL;DR version of that library is
next.frame(cb)
ornext.idle(cb)
ornext.clear(cb)
to optimize, and centralize,requestAnimationFrame
andrequestIdleCallback
operations in a smarter way, similar toprocess.nextTick
in node, but compeltely browser-side centric.Please let me know if that works for you, otherwise I'll try to find another name
( but unfortunately cool names are all taken on npm :-( )
Cheers
The text was updated successfully, but these errors were encountered: