studds

fwiw, the [official recommendation](http://www.typescriptlang.org/docs/handbook/declaration-files/publishing.html) from the typescript team in this case would be to publish the types to the @types organisation on npm, which is done by [submitting a PR](https://github.com/DefinitelyTyped/DefinitelyTyped#create-a-new-package)...

I've fleshed out the types we're using internally in preparation for opening a PR on DefinitelyTyped. I've also tried to combine with what you've got, @kasperisager. We're not doing any...

Ahhh, yes, that is a problem. I can't figure out how to get around that with plain types. Can I propose a different approach, in that case: wrapping unexpected and...

That's awesome, @kasperisager!

This would be great. I'm not familiar with any of the code bases involved, so I'm not sure just how much I can contribute, but I've be mulling this over...

Any update on this?

The way I've done lambda layers is not very useful, to be honest. It only works if you have a piece of custom code which you want to deploy as...

Good chatting today @vespertilian. It's clear that the way that nx-aws currently handled layers is broken. This is further complicated because the way sam handles layers [is](https://github.com/aws/aws-sam-cli/issues/2222) [broken](https://github.com/aws/aws-sam-cli/issues/2419). My preferred...

> So my first priority is to fix the way layers are handled in nx-aws so that valid layers "just work". This may be a breaking change to anyone who...

Hey @dbrody @vespertilian - I've been working away at a fix and a bunch of other enhancements. The problem is that I've got my branches twisted up 😦 I should...