Rafał Chłodnicki

I've tried on the database I have handy and couldn't reproduce. I think this could depend on the structure of the database. If you have exact steps, including db structure...

I will have a look when I have more time but maybe it would make sense to also support big numbers by using BigInt (would require changing requirements to at...

The `@aws-sdk/client-dynamodb-v2-node` package is at version `0.1.0-preview-2` and hasn't been updated in over a year. Given that, I'm don't feel confident switching to it.

Not sure 100% but numbers in dynamodb are represented as strings, I believe (based on [that](https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_AttributeValue.html)). So as long as SDK supports BigInt, it should work.

I would be fine with upgrading to v3-beta if there wouldn't be any compatibility issues with existing tables. I would think there shouldn't be as SDK should at most break...

No, I meant I'm fine with upgrading to v3 if it doesn't break compatibility with dynamodb. I expected it doesn't but wanted to be sure.

The configuration needs to be serialized one way or another. This is how Nuxt modules work. So you can't just reference some import in your configuration like that and expect...

So do you need to override it for server or the client?

But I see now why the server options will also not work in this case. This is because this module "freezes" the server options at build time. The reason this...

Thanks for reporting. This is discussed in https://github.com/nuxt/framework/discussions/751#discussioncomment-1468163 a bit. I would still like some answers from the team and better documentation since it's not clear how things should look...