Glad you like them!

Thank you so much 😀

I'm glad you enjoyed it

Gald it's useful

Glad you think so!

Thanks :)

No problem!

Hey Pete, Just looked through all of my videos and realised that I never uploaded my webpack video. I'll do that this week but for now heres a summary Short summary: We use webpack as by default serverless uploads all the code from the repo into every lambda. When you have lots of code (10-15 endpoints and lots of common code) you hit the upload limit of the lambda. Webpack works to only include the code that you need, reducing the upload size. Steps to setup: npm install --save-dev webpack serverless-webpack add serverless-webpack to the plugin list add this to your serverless.yml file package: individually: true Create a webpack.config.js file at the root of your repo containing this module.exports = { target: 'node', mode: 'none', };

@@CompleteCoding thanks Sam I have that working in the code now but I can't get the offline dynamodb to start in the final step. Everything else works. The error seems to point to (!child.pid) - any idea where I'm going wrong? Could it be something to do with the Java developer kit? It's not clear in the video what role that plays.

Error -------------------------------------------------- Error: spawn java ENOENT at Process.ChildProcess._handle.onexit (internal/child_process.js:232:19) at onErrorNT (internal/child_process.js:407:16) at process._tickCallback (internal/process/next_tick.js:63:19) For debugging logs, run again after setting the "SLS_DEBUG=*" environment variable.

@@PeteWhelan Have you installed the Java Runtime Engine? www.oracle.com/java/technologies/javase-jre8-downloads.html

@@CompleteCoding Thanks Sam - the following steps solved this issue. I downloaded the java engine from the link, rebooted my computer. Deleted DynamoBd folder from the code and reinstalled DynamoDB PS on your video and Github code - you have "ProvisionedThoughput", I've assumed that is a typo and have replaced with "ProvisionedThroughput" in the player-score.json. Looking forward to the next video. :)

Thanks Here's the link github.com/SamWSoftware/ServerlessKZfaqSeries/tree/l19-serverless-offline

You no longer need to create that file. Serverless now takes the definition straight from the serverless file

@@CompleteCoding I have completely opposite issue, I dont want to define table in yml file, since it is already deployed through another service. Is it possible? or can I make serverless.yml to ignore the table while deploying and only use it for testing?

@@usamashahid3172 There should be a way to do that but it's not simple and would be easier if you were using serverless.ts create a new js/ts file just for your dynamo config. In that file it needs to be a function that takes the serverless config as a parameter. That function should check if this is running as a deployment or running locally and return either no resources when deploying and the dynamo table resource when running locally. I've never had to do this but it should be possible

That's a great idea. I'll add it to the list

That's strange. I would check that you are calling the response function with all the data you want to be returning.

I've changed my opinion on this since making the video. I mainly do end to end testing once it's been deployed. I either have a 'dev' environment or a temporary one. Offline is ok if your app is super simple ( just API and Dynamo) but once you add any other services, trying to mock things becomes too messy

The link is in the description

Awesome to hear. I'll update the description

Glad that you figured out how to fix it :) well done

I've never worked in Java and I think that it might be more difficult as lambda doesn't natively support java. You could look into the new serverless containers (docker) to run your java code

Looks like in recent versions of serverless-offline, they've added process.env.IS_OFFLINE support back in.

@@joostschuur Yes I was amazed to see that

Yes you can. If you are using VS-Code then you can stick breakpoints wherever you like. You can then use the built in debugger to run all of your tests, stopping at the breakpoints so you can view the variables at that point. completecoding.io/content/images/2020/03/Screenshot-2020-03-06-at-07.29.36.png

@@CompleteCoding do you have a video with the setup for vscode debugging?

@@juanjoseramirezcalderon2618 I do actually kzfaq.info/get/bejne/rsdydL2el9DKiIU.html

You would have to create a dyanmoDB table config for each of the tables you use to get it working with serverless dynamo local. You would then have to add some logic to the table so it doesn't actually try deploying it - as you would be trying to create a table that already exists. You can use "conditions" in cloudformation to do that. "Conditions": { "CreateDynamoResources": { "Fn::Equals": [ { "Ref": "EnvType" }, "test" ] } }, "Resources": { "DynamoTable1": { "Type": "AWS::DynamoDB::Table", "Condition": "CreateDynamoResources", "Properties": { ... } },

@@CompleteCoding can't we use serverless-dynamodb-local and write the code without AWS credentials?

It runs a local dynamodb table on your machine. So the data is technically stored in the ram of your computer.

Yes, this video was recorded back when it was serverless-offline 5.x and that didn't require this change. I'll add something to the description to outline this

Have you set up an aws credentials profile on your computer? It appears to be looking for the correct AWS credentials to use.

You can call it what you want. It could just be called 'player-points.json' or anything els

I've worked in Go a little bit but not enough yet to be confident making videos on it. The serverless parts of my videos should be the same, just with a change in the actual lambda file

Check the code in your lambda. Make sure that there isn't a loop or something in the code. If it is a request with Dynamo, make sure that you'e installed `sls dynamodb install`. There is also a change with v6 of the serverless offline plugin where process.env.IS_OFFLINE doesn't exist. If you add a console.log to the code and log out that variable you should see what it's value is. If it is undefined then you can resolve this by changing the version of serverless-offline (in you package.json) file to 5.12.1, deleting node modules and package-lock and running `npm install` again

​@@CompleteCoding just got it ... thank you very much ... you saved my life SAM ...

Well done Dhanwa

I've never worked with Serverless and Express but I think I know the issue. If you run 'sls info' what urls do you get? If you don't get "someapi/{stage}/*" then you might need to change the paths in your function definition I'm assuming you have one function with all your express logic in? It should look something like this ExpressFunction: handler: src/ExpressFunction.main events: - http: path: * method: ANY cors: true

never mind you have a full video on this

This is something that I've started to do a lot more in my lambda development

Have you installed the plugin and added it to the plugin list? www.serverless.com/plugins/serverless-offline

You don't need a whole folder for offline, just adding "serverless-offline" as a plugin in the serverless.yml file. I've also used "serverless-dynamodb-local" in this video for running Dynamo local as well

@@CompleteCoding You are missing the offline/migrations folder in the code repo for this video. The repo for the next video in this playlist has the folder.

@@ddsmax You don't need that folder. Dynamo-local will automatically use the Dynamo config in your resources file to create the local table. If you are connecting to a dynamo table that you don't create in that repo you can use this migrations folder. I need to delete it from the next repo as it's not needed

That looks like a really smooth library. Do you know if there is any history of requests? One of the things I do most in postman is searching through old request to re-use one.

Awesome to hear

Haha :P It's so hard to do a video on Serverless without saying it all the time

I know, it is very frustrating. You can install version 5.12.1 of serverless offline which still works. I'll comment again when I have a solution to resolve this.