Frédéric Barthelet

@nhammond101 you can try your config with TS 4.1. Using a baseUrl is not required anymore: https://devblogs.microsoft.com/typescript/announcing-typescript-4-1/#paths-without-baseurl

@nhammond101 thanks for your awesome work :) ! Do you think you can provide a PR to the template to : - add dependency to `tsconfig-path` - add require option...

Hi @pveller and thanks for reporting your issue. Regarding your issue, the code that will be used for typescript definition generation is https://github.com/serverless/serverless/blob/19805d71eabb68bd7fd4046aa23090ef85fb1c36/lib/plugins/aws/package/compile/events/stream.js#L15-L90 This JSON schema definition can be improved...

Hi @bfaulk96, as you can see in the linked issue #1, Quicktype is misbehaving regarding JSON Schema `additionalProperties` specification. You can find additional details on https://github.com/quicktype/quicktype/issues/1615

Hi @remcoabc and thanks for submitting this issue. Could you please provide your serverless.ts file :) ?

Thanks @remcoabc. Your service file looks perfectly fine. Could you share as well your node version and your package.json for better understanding (i'm particulary interested in your TypeScript version). Could...

Thanks @remcoabc, can you provide your `tsconfig.json` as well ? My understanding is that your current configuration checks for dependancies as well. You can bypass this behavior in 2 ways...

@grimm2x @remcoabc thanks to both of you for your insights. A bit of context concerning the appearance of this issue : - type checking started failing at [release v2.24.0](https://github.com/serverless/serverless/releases/tag/v2.24.0) of...

There currently is a PR ongoing in `json-schema-to-typescript` that will solve this issue. Do not hesitate to upvote :) https://github.com/bcherny/json-schema-to-typescript/pull/383

In case somebody experiences this issue, one way to reduce this issue in the mean time is to use subdefinition like this : ```ts import type { AWS } from...