NestJS, Angular 6, Server Side Rendering (Angular Universal), GraphQL, JWT (JSON Web Tokens) and Facebook/Twitter/Google Authentication, Mongoose, MongoDB, Webpack, TypeScript
Stars
333
Forks
75
Watchers
333
Open Issues
87
Overall repository health assessment
7.0.27.0.27.0.27.0.27.0.27.0.0-beta.197.0.27.0.27.0.27.0.27.0.27.0.27.0.25.4.05.4.05.4.05.4.05.1.05.4.05.4.07.0.27.0.21.5.01.4.01.3.92.4.51.0.92.1.01.18.34.1.31.4.32.5.74.16.47.1.314.0.21.0.02.10.04.0.32.0.83.14.014.0.48.3.05.3.90.4.03.3.02.1.04.0.01.0.01.3.02.8.00.1.122.88.06.3.36.3.30.9.156.1.00.8.260.10.47.0.47.0.27.0.21.4.14.16.07.1.114.0.30.0.422.8.92.0.514.0.08.3.05.3.010.12.20.4.73.0.11.0.332.48.06.0.14.5.04.0.13.3.04.2.13.1.12.2.01.0.12.0.41.1.21.4.04.10.04.0.35.4.12.6.25.3.07.0.15.11.03.6.03.1.64.24.03.1.21.7.2145
commits
5
commits
Merge branch 'master' of github.com:heralight/nest-angular
c233938View on GitHubIn 1205d9cc2b50529b4acba2736fc3b685236375d0 I changed the base tsconfig's target to es6 because the @nestjs/passport package needs to be compiled in es6 in order to work.. Angular on the other hand needs to be compiled in es5/es3 so since the client tsconfig extends the base tsconfig I had to override the target in the client tsconfig
424cae8View on GitHubWe now make use of the @nestjs/passport package so we can use AuthGuard for invoking the JWT strategy at route level - perfect for graphql resolvers, for example
1205d9cView on GitHubThe JWT secret is now in a separate file in the newly created folder keys in the root of the project - we are using a 1024bit private key (precaution against brute forcing hs256 - see https://auth0.com/blog/brute-forcing-hs256-is-possible-the-importance-of-using-strong-keys-to-sign-jwts/)
e3a09d7View on GitHubMerge branch 'master' of https://github.com/bojidaryovchev/nest-angular
3ab86bcView on GitHubUpdated the Readme to include instructions about GraphQL
f9a7dc3View on GitHub