Getting "Invalid Table" error

[brettstack]

This works locally, but when I deploy to Lambda, the table.constructor.name is empty, causing dynamodb-toolbox to throw https://github.com/jeremydaly/dynamodb-toolbox/blob/v0.2/classes/Entity.js#L46-L69.

I'm using serverless-webpack which may have something to do with it?

[jeremydaly]

Yes, this is caused by webpack. I'm going to flag this as a bug, although it technically isn't, but clearly needs to be addressed so that it works with webpack out of the box. Thanks for noticing.

[brettstack]

Confirmed this works 🎉

[jeremydaly]

@brettstack, there are a few other places that use the constructor.name syntax (mostly around batches). Let me know if you run into issues with those.

[aldebout]

@jeremydaly this is the same minification issue right?

If so, a temporary fix is to disable minification in your webpack config:

optimization: {
    minimize: false,
  },

[jeremydaly]

@aldebout, I'd rather not require that, but yes, should work for temporary fixes. There are other ways to verify the correct instances are passed, so I'll hunt for these and add fixes.