Most of the tests that currently cover core functionalities depend heavily on (and sometimes test) internal implementation characteristics. While they should be testing whether the given implementation produces desired outcome (treating its implementation more as a black box).

_Current state of things is problematic for eventual internal improvements and refactors which occasionally we want t

Issue Summary

Building with serverless results in an error:

Build error occurred
TypeError: Class extends value undefined is not a

Hi,

I wanted to enable binary support on API gateway, but could not find the way to do it via component's inputs.

Is this something that you would consider adding in the future?

If so, I can try to add this feature. It doesn't look too complicated.

Thanks!

Right now settings are just passed in through the settings file. This is somewhat limiting if there is a value that will be dynamic with deployments (such as a docker image file, etc.) We should support accepting settings through environment variables, the CLI, the current settings file, and any mix of those.

The order of precedence with mixed should be CLI -> environment -> config file.

If

I'm submitting a...

[x ] Bug report  
[ ] Feature request
[ ] Documentation issue or request

In package

[ ] @ng-toolkit/init
[ ] @ng-toolkit/serverless
[x] @ng-toolkit/universal
[ ] @ng-toolkit/pwa
[ ] @ng-toolkit/f

Hi everyone,

I'm building Saas app model where each client should have their own API_KEY specified expiry dateTime as additional authorization method (AWS Cognito User Pool is used by default authorization).

I can see we have one field API_Key but have no idea how appsync works out on selecting specifically which API_KEY corresponding for each clients.

Another scenario using API_Key as

synk report issue

Description

We are synk (https://snyk.io/) for checking used packages.

Synk is complaining about a security issue for serverless-step-functions.
https://snyk.io/vuln/SNYK-JS-DOTPROP-543489

Additional Data

• Serverless Framework Core Version you're using: 1.64.1
• The Plugin Version you're using: 2.17.1
• Operating System: macOS Majove 10.14

This is a Bug Report

Description

When