AWS Amplify Next.js NextAuth Prisma GraphQL Nexus.js
Stars
10
Forks
3
Watchers
10
Open Issues
1
Overall repository health assessment
^0.5.2-next.19^3.5.0^3.5.0^15.7.2^9.3.4^0.1.112.0.4^4.0.0-beta.7^1.1.017.0.217.0.2^0.1.216.11.917.0.357.32.012.0.4^3.5.04.5.215
commits
fix for the Object literal may only specify known properties, and 'authorize' does not exist in type 'NexusOutputFieldConfig<"Query", "accounts">' error https://github.com/graphql-nexus/nexus/issues/511
b22d0fcView on GitHubfix for the Object literal may only specify known properties, and 'authorize' does not exist in type 'NexusOutputFieldConfig<"Query", "accounts">' error https://github.com/graphql-nexus/nexus/issues/511
208a877View on GitHubfix for the Object literal may only specify known properties, and 'authorize' does not exist in type 'NexusOutputFieldConfig<"Query", "accounts">' error https://github.com/graphql-nexus/nexus/issues/511
b532633View on GitHubMerge branch 'main' of https://github.com/bojidaryovchev/next-amplify into main
c14d870View on GitHubmade use of the Nexus fieldAuthorizePlugin in order to implement the support for protected / unprotected GraphQL access
f98753aView on GitHubnext.config setting for Prisma in order to make it work in the serverless AWS Lambda environment
37f5bd6View on GitHubadded Prisma NextAuth and configured Google as an OAuth provider
98ea099View on GitHub