Couldn't able to deploy app to serverless environment
See original GitHub issueI’m submitting a…
[ ] Bug report
In package
[ ] @ng-toolkit/serverless
[ ] @ng-toolkit/universal
Current behavior
Getting npm ERR! code ELIFECYCLE. For more info refer snap,
Expected behavior
Able to deploy an app without any interruption
Minimal reproduction of the problem with instructions
I got the above error while running this command npm run build:serverless:deploy
I followed deployment steps from this source https://coursetro.com/posts/code/165/Deploying-your-Angular-App-to-a-Serverless-Environment-
Environment
Angular version: 8.1.1
- Node version: v10.16.0
- Platform: Linux
Issue Analytics
- State:
- Created 4 years ago
- Comments:8
Top Results From Across the Web
Top 10 Serverless Deployment Errors (and How to Fix Them)
1. Invalid CloudFormation state · 2. Unable to fetch parameters · 3. API Gateway: No integration defined for method · 4. Codebuild deploy...
Read more >Deploying serverless applications - AWS Documentation
You have two main options for using AWS SAM to deploy your serverless applications: 1) Modify your existing pipeline configuration to use AWS...
Read more >Deploying to AWS - Serverless Framework
Deploy Function. This deployment method does not touch your AWS CloudFormation Stack. Instead, it simply overwrites the zip file of the current function...
Read more >Why does my Serverless Function work locally but not when ...
One of the common reasons for different behavior across environments is whether or not your Serverless Functions depend on packages with native dependencies....
Read more >Serverless deploy - Function not found - sls deploy
I've faced this issue with Serverless. The issue is caused by how Serverless handles, tracks, and deploys your functions.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@KingDarBoja Hey thanks, might be the issue in AWS. I could have tried this earlier 🙃
I’m closing this issue.
@HenonoaH 🎉 Glad it works now! And yeah, probably something on the AWS side.