-
Notifications
You must be signed in to change notification settings - Fork 28
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
Drop babel-runtime #138
Comments
@mattkrick do you have any thoughts on this? |
yeah, you're absolutely right! I need to dig into this & check out the easiest way to do that. |
That's great, I'm glad you're onboard. I wonder if swapping async/await with good 'ol promises would be ok? (albeit much uglier) As soon as we can drop babel-runtime I have an awesome demo project to put online a la ember-cashay. |
yeah, that's not a terrible idea, especially since there are only 2 of them. https://github.com/MatAtBread/fast-async is another option |
@mattkrick are you working on this? If not I will take a stab at it. |
Not right now, I got a work sprint that's kicking my butt at the moment. If On Nov 18, 2016 12:49 PM, "Dustin Farris" notifications@github.com wrote:
|
Relying on this library can be problematic depending on the client environment. It is definitely problematic for me.
GraphQL's justification does a better job of explaining than I ever could—so I am going to quote their commit message from graphql/graphql-js@188881b
Note that the above change took effect in graphql 0.6.1. (cashay currently pegs graphql 0.6.0)
The text was updated successfully, but these errors were encountered: