Error: Can't find application template hello-world-typescript - check valid values in interactive init
See original GitHub issueAfter upgrading SAM CLI to version 1.50.0 from 1.47.0, sam init
stopped working for nodejs16.x
runtime and Hello World Example TypeScript
template. We are getting the following error:
Error: Can't find application template hello-world-typescript - check valid values in interactive init
Environment: Windows 10
Can anyone please help me with this asap?
Issue Analytics
- State:
- Created a year ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
sam init - AWS Serverless Application Model
Initializes a serverless application with an AWS SAM template. The template provides a folder structure for your AWS Lambda functions, and is connected...
Read more >AWS SAM - Esbuild Failed: cannot find esbuild - Stack Overflow
I had to install esbuild globally to get this working npm install -g esbuild.
Read more >AWS SAM CLIでTypeScriptがネイティブサポートされました ...
sam init を実行して、TypeScriptのAWSクイックスタートテンプレートで ... npm Application Template: hello-world-typescript Output Directory: .
Read more >How to Write Shell Scripts in Node with Google's zx Library
js projects. Writing Shell Scripts: the Problem. Creating a shell script — a script that's executed by a shell such as Bash or...
Read more >Meet AWS SAM CLI: sam init - Medium
“Initialize a serverless application with a SAM template, folder structure ... Possible Values: npm, pip, bundler, cli-package, maven gradle.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I had the same problem in windows. I traced the cli and found the git command it’s failing on. I was able to fix it by setting git longpaths true.
The fix (run from elevated prompt to configure for --system)
Thanks for confirming. I will be resolving this and leave the other one open for now. Please let us know if the recommended actions in other issue (https://github.com/aws/aws-sam-cli/issues/3781) is not resolving your problem.