| ▲ | Garlef 2 days ago | |
Their stack builds a lot of abstractions on top of each other and this works only well as long as you don't deviate from the beaten path. One example: You can't really build custom TS providers for AWS resources. Why? Because this feature is built using the compilation magic that makes inline lambdas work. But the compilation step omits the AWS SDKs since these are present in a lambda anyways. So you can't use the AWS SDK in custom providers. | ||