@aws-amplify/deployed-backend-client
Advanced tools
Responsible for reading stack output and metadata from deployed stacks and presenting it in a validated and typed format. You could think of this package as our "database client" (but instead of a database, we have CloudFormation metadata and output). It
Responsible for reading stack output and metadata from deployed stacks and presenting it in a validated and typed format. You could think of this package as our "database client" (but instead of a database, we have CloudFormation metadata and output). It does not perform transformation of the data, it just understands how to read the data format.
This package is expected to be browser friendly.
FAQs
Responsible for reading stack output and metadata from deployed stacks and presenting it in a validated and typed format. You could think of this package as our "database client" (but instead of a database, we have CloudFormation metadata and output). It
The npm package @aws-amplify/deployed-backend-client receives a total of 88,199 weekly downloads. As such, @aws-amplify/deployed-backend-client popularity was classified as popular.
We found that @aws-amplify/deployed-backend-client demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 6 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
/Research
A phishing attack targeted developers using a typosquatted npm domain (npnjs.com) to steal credentials via fake login pages - watch out for similar scams.
Security News
Knip hits 500 releases with v5.62.0, refining TypeScript config detection and updating plugins as monthly npm downloads approach 12M.
Security News
The EU Cyber Resilience Act is prompting compliance requests that open source maintainers may not be obligated or equipped to handle.
