aws-sdk dependency about dynamodb-toolbox HOT 5 CLOSED

The dependency has been removed in the v0.2 branch.

from dynamodb-toolbox.

Been thinking more about this and I'm going to remove this dependency from the project. Instead, I'm going to require you to pass in an instance of the DynamoDB DocumentClient. v0.2 is moving to issuing calls directly (rather than just returning a formatted call), so this will give you the ability to fully control your AWS SDK settings.

from dynamodb-toolbox.

The recommended practice is NOT to rely on the included SDK in the Node runtimes, but making this optional would make sense. Also, if you are webpacking your Lambda functions, then the tree-shaking will significantly reduce the dependency size.

from dynamodb-toolbox.

Thanks for your response.

Oh, that's strange; why's it not good practice to rely on the included SDK? Why wouldn't it be safe to assume that the version appropriate to the NodeJS runtime is available and fully functional. I've never had any problems, but that's not to say their aren't things I'm not aware of!

from dynamodb-toolbox.

Hi @alexdilley
I don't want to start a discussion over this topic (it's not the place). However, I can offer you a hack that can be useful in development when you deploy to AWS often and you are not using sets.

Go to node_modules/dynamodb-toolbox/package.json in your project and remove aws-sdk from dependencies. Then the serverless framework will not include it. For my simple project package size went down from 9MB to ~600KB, deploys are significantly faster now.

Also, in your own project set aws-sdk as dev dependency otherwise, this hack will not work for you.

@jeremydaly is using AWS-SDK to create sets on line 508 & 512 you can see it here
https://github.com/jeremydaly/dynamodb-toolbox/blob/master/index.js#L508. If you're not using it you're safe to remove it.

Again, it's a dirty hack. You've been warned :-)

from dynamodb-toolbox.