-
Notifications
You must be signed in to change notification settings - Fork 90
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
fix: update apq middleware build #839
Conversation
This LGTM so far |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Couple of things I've noticed but I don't think any of them are huge blockers at all if they prove to be oversights, otherwise LGTM :)
@@ -1,5 +1,7 @@ | |||
import React, { useState } from 'react' | |||
import { GraphQLClient, ClientContext } from 'graphql-hooks' | |||
// eslint-disable-next-line no-unused-vars |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Was including this intended?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah, the APQ issue with crypto
not being polyfilled with webpack 5 only surfaces when the middleware is imported, once #847 is complete, that example could be used for the acceptance tests
@aws-crypto/sha256-universal
with@aws-crypto/sha256-browser
APQMiddleware
now a named exportresolves #819