npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

ask-sdk-local-debug

v1.1.0

Published

Local debug package for Alexa Skills Kit SDK

Downloads

1,674

Readme

ASK SDK Local Debug (Node.js)

About

ASK SDK Local Debug is a package which enables you to test your skill code locally against your skill invocations by routing requests to your developer machine. This enables you to verify changes quickly to skill code as you can test without needing to deploy skill code to Lambda.

NOTE: Feature is currently only available to customers in the NA region(https://developer.amazon.com/en-US/docs/alexa/custom-skills/develop-skills-in-multiple-languages.html#h2-multiple-endpoints).

Installation

npm install --save ask-sdk-model@^1.29.0
npm install --save-dev ask-sdk-local-debug

Configuration

USING Alexa SKills toolkit for VS code

The Alexa Skills Toolkit for Visual Studio offer integrated support for local debugging. To get started, please review our technical documentation on how to Test your local Alexa skill using VS Code.

NOTE: If you have existing an ASK CLI profile, you will need to sign in again using the latest version of ASK CLI (>=2.13). Once installed, simply re-run ask configure to re-authorize your profile for local debugging.

USING with other IDEs and Debuggers

  1. To instantiate a connection to the local debugging service, execute the following from your skill’s lambda directory:
node ./node_modules/ask-sdk-local-debug/dist/LocalDebuggerInvoker.js 
      --accessToken <ACCESS_TOKEN>
      --skillId <SKILL_ID>
      --skillEntryFile <FILE_NAME>
      --handlerName <HANDLER_NAME>
      --region <REGION> # Optional argument. Region defaults to NA.
1. ACCESS_TOKEN:
    1. Install ASK CLI v2
    2. npm install ask-cli@2 -g
    3. Generate the accessToken using ASK CLI
    4. ask util generate-lwa-tokens --scopes alexa::ask:skills:debug
    5. You will be directed to a Login with Amazon page. Sign in and retrieve your ACCESS_TOKEN from the terminal.
2. SKILL_ID: The ID of the skill you are trying to debug. Ensure that the developer account you used to login to obtain the access token has access to this skill.
3. FILE_NAME: The path to your skill code's main file (typically `index.js`). This file or module contains the skill's handler function.
4. HANDLER_NAME: The exported handler method (typically `handler`). For example, please see the [Hello world example](https://github.com/alexa/skill-sample-nodejs-hello-world/blob/master/lambda/custom/index.js#L159).
5. REGION: The region of the developer account. The accepted values are NA(North America), FE(Far East), EU(Europe). Defaults to NA. Instructions on finding out your region can be found [here](https://developer.amazon.com/en-US/docs/alexa/ask-toolkit/vs-code-testing-simulator.html#test).
  1. Configure your preferred IDE or other debugging tool to attach to the above process or execute directly from your preferred IDE. For example, in VS Code, this would be included in the launch.json:
{
     "type": "node",
     "request": "launch",
     "name": "Skill Debug",
     "program": "<5. Program>",
     "args": [
          "--accessToken","<ACCESS_TOKEN>",
          "--skillId", "<SKILL_ID>",
          "--skillEntryFile", "<FILE_NAME>",
          "--handlerName" , "<HANDLER_NAME>",
          "--region", "<REGION>" # Optional argument. Region defaults to NA.
      ]
}

Things to note

  1. Local debugging is only available for a skill’s development stage.
  2. A connection remains active for **1 hour. **You will need to reinstantiate the connection after 1 hour.
  3. All Alexa requests for the skill will be routed to your development machine while the connection is active.
  4. Only one connection session may be active for a given skill ID and developer account.

Opening Issues

For bug reports, feature requests and questions, we would like to hear about it. Search the existing issues and try to make sure your problem doesn’t already exist before opening a new issue. It’s helpful if you include the version of the SDK, Node.js or browser environment and OS you’re using. Please include a stack trace and reduced repro case when appropriate, too.

License

This SDK is distributed under the Apache License, Version 2.0, see LICENSE for more information.