Lauri Svan

Closing this one - stupid user error (that's me!) - it appears that actually verifying the sign-in attempt from within Google Accounts -> Security page removes this nagging.

@JPLemelin The problem actually reappeared for me as well when turning on MFA. I cannot see that verification form again. Previously Google recognised google-aws-auth authentication attempts as new devices that...

We have also recently faced this issue when using tedious via Lambda functions. In such cases the number of dependencies matter - both for cold start of the Lambdas (bigger...

@TheThing > @laurisvan you might wanna check out node-sqlserver-v8: https://github.com/TimelordUK/node-sqlserver-v8 It does require ODBC drivers to be installed but if you can get that, then it's a much smaller package....

I have an issue which I believe has this same root cause. We have several schemas that default their input values based on schema. Now that JIT compiler interprets unset...

Since my project very much needs CSP to work and we are using this package, I spent some time investigating this one. It appears "use strict" is may be added...

I made a PR #1664 for a brute force replacement of "use strict". I believe it should have no shortcomings except that somebody could slip unstrict code into web builds....

@notclive How did you manage to do such an import? Would be nice to get it working in our webpack based build.

IMHO maintaining two versions in the same repository feels a bit tedious (think about two sets of node module dependencies). I'd suggest moving 0.5 compatible stuff to 0.5 branch, and...

DataLoaders are currently our main memory hog, indeed creating 1000s of Promises, JS context objects or array literals as we have a few levels of GraphQL resolvers, resolving up a...