Chris

Results 48 comments of Chris

The `./amplify/.config/local-env-info.json` should be git ignored: https://docs.amplify.aws/cli/reference/files/#gitignore So the action fails because the file is not available during runtime. A simple `touch ./amplify/.config/local-env-info.json` before `echo` should make it work I...

I don't see the validation property in VSCode intellisense, but could be due to the reason I'm using TypeScript. Thats what I see: ![image](https://user-images.githubusercontent.com/950244/92715076-46968880-f35d-11ea-86df-23356d6aa360.png) With cleaning the object you mean...

I was able to suppress the TypeScript error message for `validation` with a `//@ts-ignore comment` However, now I get the following error: ``` Error: Not sure how to validate validation...

I'd like to join this conversation as I'm facing the same issues. I'm in the middle of converting a service from Node14 to the newly supported runtime Node16 to use...

@git-chrisp thank you for this detailed explanation. I was able to get ESM working with `serverless.ts` and `esbuild`. The PR #10657 already added support for loading ESM plugins: https://github.com/serverless/serverless/blob/37b29b029579191e82348afbf855590c2cb37062/lib/utils/import-module.js#L3-L13 To...

@git-chrisp I opened PR https://github.com/serverless/serverless/pull/11147 and explained the implementation as detailed as possible. Nevertheless, in your https://github.com/serverless/serverless/issues/11039#issuecomment-1121492620 above you mentioned the error `[ERR_UNKNOWN_FILE_EXTENSION]: Unknown file extension ".ts"` even though `ts-node`...

> Thanks a lot for sharing your PR @zirkelc - there are some failing tests, could you please look into that? @pgrzesik the import of `require('node:child_process')` didn't work for Node...

@deser @LL782 I added a `ChoiceRule` type and some other fields. The whole definition is available in this gist: https://gist.github.com/zirkelc/084fcec40849e4189749fd9076d5350c Here's the type again so you can update your comment:...

I would take this issue over if there's a chance the fix makes it back into the package?