v2 -> v3 migration, missing types #4947
-
I'm migrating my node application from the v2 aws-sdk to the v3. I see that part of this migration calls for modularization of packages, so instead of importing all of aws-sdk you would instead import just @aws-sdk/client-eventbridge (for example). There are some types I'm currently using in my project that I don't see in the new v3 @AWS-SDK package. For example, the Is this going to cause issues as I try to migrate over from v2 to v3 or will the non-scoped aws-sdk package stay around? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
Hi @ghidalgo93, v2 and v3 are code base totally different, even though they are aimed to accomplish the same tasks. Therefore types in v2 will not be compatible with V3. In V3 the equivalent to AWSError could be ServiceException, which is the base exception class defined here. However, each operation has its own exception class. Here is our upgrading guide that can provide you with great information how to properly migrate from v2 to v3. Please let me know if you have any questions or need anything else. I hope this helps! Thanks! |
Beta Was this translation helpful? Give feedback.
-
Hello! Reopening this discussion to make it searchable. |
Beta Was this translation helpful? Give feedback.
Hi @ghidalgo93, v2 and v3 are code base totally different, even though they are aimed to accomplish the same tasks. Therefore types in v2 will not be compatible with V3. In V3 the equivalent to AWSError could be ServiceException, which is the base exception class defined here. However, each operation has its own exception class.
Here is our upgrading guide that can provide you with great information how to properly migrate from v2 to v3.
Please let me know if you have any questions or need anything else.
I hope this helps!
Thanks!