Closed ThomasVuillaume closed 4 years ago
Turned out it was an ask-cli related problem, caused by a failing Powershell module during Zip file construction ... All info (for unfortunate Windows users like me) are there : https://github.com/alexa/ask-cli/blob/develop/docs/FAQ.md#q-for-windows-users-if-your-skill-return-empty-response-and-log-shows-module-not-found-genericerrormapper-or-cannot-find-module-dispatchererrormappergenericerrormapper-how-to-resolve
I'm submitting a...
I retrieved the latest version of the ask-cli (2.2.0) and I was trying to give a try on a fresh example. I chose the
ask new
command with theHello World
template, with the CloudFormation option. Then, I do nothing more thanask deploy
which indeed deploys everything to AWS (I can see the Lambda) and Alexa (I can see the skill). When I run theask dialog --locale en-US
command, and then demand toopen hello world
, and error is prompted.See the full log below.
Expected Behavior
Well, that it works like in the tutorial.
Current Behavior
The lambda (runtime : Node.js 12.x, but I tried 10.x with same result) seems to direct-crash at startup, and it's because of this error (which I see in the CloudWatch). Aparently, some data are not found from
ask-sdk-runtime
Also, I retrived the .zip file on the S3 bucket declared in the CloudFormation, that is used for the Lambda : it contains a full node_module folder, including the file in
node_modules\ask-sdk-runtime\dist\dispatcher\error\mapper
...Possible Solution
No idea...
Steps to Reproduce (for bugs)
Context
Just trying to create a new test project, based on a provided template example, then do nothing more and just try to deploy it.
Your Environment
Node.js and NPM Info
More interesting info : the package-lock.json file generated in the .ask folder is the following :