INVALID_REQUEST_TYPE

[splittix]

I just created a very simple alexa skill with this alexa-app npm module. And called my skill and I get the response "INVALID_REQUEST_TYPE". It's been a while since I've played with this module, but it looks like the values that Amazon is passing along to skills has changed in format. There hasn't been any code changes for about a year. Is this still supported? Is a new version recommended?

ex. request intent passed in from Amazon:

"request": {
        "type": "IntentRequest",
        "requestId": "amzn1.echo-api.request.ad7db8b4-d821-457d-bec0-95d26a3fc5a8",
        "timestamp": "2019-12-16T17:28:26Z",
        "locale": "en-US",
        "intent": {
            "name": "number",
            "confirmationStatus": "NONE",
            "slots": {
                "mynumber": {
                    "name": "mynumber",
                    "value": "3",
                    "confirmationStatus": "NONE",
                    "source": "USER"
                }
            }
        },
        "dialogState": "STARTED"
    }

[dblock]

Haven't seen much activity here, step in! I'm still running a skill with this code successfully, though.

[matt-kruse]

I still use alexa-app and it works perfectly for me. In fact, I just published a skill with it last week! [try it, enable Debbie Downer ;) ] I found that the tooling and process around this module now makes it too difficult for me to maintain or contribute to. Instead, I am working on alexa-app-bootstrap, a "helper" module where I am putting my innovations. While there have been changes and improvements to the Alexa requests over the last year or two, everything is backwards-compatible and alexa-app is flexible enough to support anything new, as far as I know. I'd like to know what code you have that generates this error.

[dblock]

@splittix Care to turn this into a failing unit test?