sambarfoot
sambarfoot
Hi Justin, thanks for the prompt response. Here is a screenshot of my directory. below is the hello.js file, generated from the ts. ```"use strict"; Object.defineProperty(exports, "__esModule", { value: true...
apologies, helloworld must have been typing error in the ticket. ``` { "configurations": [ { "type": "aws-sam", "request": "direct-invoke", "name": "lambda debug", "invokeTarget": { "target": "code", "projectRoot": "", "lambdaHandler": "lib/lambdas/hello/hello.handler"...
this is build logs ``` Preparing to debug locally: Lambda "lib/lambdas/hello/hello.handler" Building SAM application... Running command: (not started) [/usr/local/bin/sam build --build-dir /tmp/aws-toolkit-vscode/vsctk4iy1xo/output --template /Users/sambarfoot/Documents//app/debug_locally/app___vsctk___template.yaml --base-dir /Users/sambarfoot/Documents//app/debug_locally] Building codeuri: /Users/sambarfoot/Documents//app/debug_locally runtime:...
I used the add debug configuration button from within the .js I tried trying the changing the path like you said but still the same issue below is a copy...
Are we likely to see support for typescript soon? Do you think if I change the output of the build, it might work? Using the following launch.json the code runs....
@justinmk3 thank you for the update I will try this
so I tried the debugger and get this error 
installing typescript globally seems to fix the problem, shame you can't use the project one. npm install -g typescript Update: it would seem that none of the packages are available...
@justinmk3 what do you need from me?