Setup AWS Serverless Project with Typescript Lambda Functions 

Site is offline for me atm.

Glad I could help!

Thanks, KhanDoor! Yeah, I personally love using Serverless, I hope to eventually get to learn about those things you mentioned and if I do I will be sure to make a video on it!

Thanks Christopher, my feelings is that I wish I had more time to be able to get my hands dirty with it haha. I've heard good things about it though!

Oh I haven't quite come across that recently. I will try and get around to it if I can!

I have not had the chance to use Hasura but I have heard good things about it.

​@@CodeDunks I'm actually working with it right now and I need to create a user when a user confirms his signup. Do you know I could test a lambda that is triggered when the user confirms the signup. Right now I'm getting an error "Unrecognizable lambda output" This is my lambda: import { GraphQLClient } from 'graphql-request'; import { Callback, Context } from 'aws-lambda'; const adminSecret = process.env.ADMIN_SECRET; const hgeEndpoint = process.env.HGE_ENDPOINT; export const handler = async (event: any, context: Context, callback: Callback): Promise => { try { const headers = { headers: { 'x-hasura-admin-secret': adminSecret as string, }, }; const graphqlClient = new GraphQLClient(hgeEndpoint as string, headers); const qv = { email: event.request.userAttributes.email, }; await graphqlClient.request( `mutation InsertUser($user: users_insert_input!) { insert_users_one(object: $user) { id } }`, qv ); callback(null, event); } catch (e) { console.warn('error', e); callback(null, false); } };

Thank you!

Hey Glen, when you say a library from a separate file what do you mean? For example, if you have this lambda project as a sub repository and are accessing another sub repositories interface then this is expected. The reason for that is that serverless will only package up the lambda projects files. So locally it works because it can access the "other library" on your local machine, but that "other library" does not exist within the package on AWS. This link might be of some use also aws.amazon.com/premiumsupport/knowledge-center/lambda-deployment-package-nodejs/

​@@CodeDunks Hello Leo, from further investigation I can see that it is just any node module that cannot be found. Which perplexes me greatly, as I've followed the same structure as you have. From the link you send, do I understand correctly that this article wants me to change my code structure to have functions in root with package.json?

@@glenjensen3683 Hmm that is odd. Couple of things you can try. 1) run yarn install again to make sure dependencies are installed correctly 2) run "yarn sls package -s dev" then check in your .serverless folder in the root of your current directory for your projects generated zip, then within that zip see that node_modules is in there with whatever dependency it says that it's missing. 3) If all else fails, try possibly copying the project from my repo in the description and see if that works.

Hey there you can look at either my video or article I made about it. Video: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-xYko2bHNgVA.html Article: documentationnerds.com/blog/tech/template-cli-with-node-and-inquirer

I've worked with both mocha and jest and found that the overall experience with Jest is a lot better in my own personal opinion. Every industry position I've worked on has also used Jest

I am not entirely sure what is being asked here. Could you elaborate?

Hey Rekefa, I actually just got a new computer and therefore don't have the configs yet. But here is the article I used to kinda set it up. Its a combination of windows terminal and cmder. medium.com/talpor/windows-terminal-cmder-%EF%B8%8F-573e6890d143

@@CodeDunks Thank you very much!