Replies: 10 comments
-
@0x62 thanks for reporting. Still it looks as problem with webpack plugin. Can you please report it at https://github.com/serverless-heaven/serverless-webpack ? It's also very troubling to see that process just exits in a middle of a deployment (most likely with success exit code), with no error is passed to the Framework (so it can be exposed meaningfully to you). It'll be great to clarify that issue on plugin grounds as well. |
Beta Was this translation helpful? Give feedback.
-
@0x62 please also see #7503 (comment) |
Beta Was this translation helpful? Give feedback.
-
Previously we used node-externals to exclude all modules from webpack. It appears this no longer works as expected, either as a result of a bug with node-externals or serverless-webpack (still investigating). Updating our webpack config in
|
Beta Was this translation helpful? Give feedback.
-
Thanks @0x62 for feedback. It'll be great to clarify why process exited like that, I see it as main problem in this case (which I believe hidden real source of an issue) |
Beta Was this translation helpful? Give feedback.
-
Okay, so after digging into this still having issues. Setting
When set to |
Beta Was this translation helpful? Give feedback.
-
@0x62 note that this doesn't belong to this repository (we cannot do anything about that here), but more to: https://github.com/serverless-heaven/serverless-webpack Have you posted this issue over there? |
Beta Was this translation helpful? Give feedback.
-
@medikoo Discussion ongoing at serverless-heaven/serverless-webpack#571 (code to reproduce). Traced to an issue with packing git-rev-sync. I think this is still relevant to SLS core though, given the possibility for webpack to fail silently. Perhaps a verification step is needed in the deploy process to check the function was actually generated? |
Beta Was this translation helpful? Give feedback.
-
SLS doesn't explicitly give such possibility. However any plugin can just use Node.js API and call If user decides to rely on a plugin it's doing it with a faith, that it won't do any foul play or stupid things. Here we deal with a situation where most likely plugin does that, and that needs to be fixed on plugin level. |
Beta Was this translation helpful? Give feedback.
-
I am pretty new to Serverless. I am facing the same issue and my whole API works perfectly with serverless offline but the deploy command just gets stuck after.
And if I try to execute/test the endpoints on Postman, the GET requests throw And any other requests (POST, PATCH, DELETE) throw
I have done a couple of Serverless project deploys on Node.JS and Express API in JS. This time I have shifted to TS for the project and used aws-nodejs-typescript template to create a REST API with Express, Node, and TS. Any guidance would be greatly appreciated. |
Beta Was this translation helpful? Give feedback.
-
As it's neither a compliant bug report nor a feature request, I'm converting this issue to discussion |
Beta Was this translation helpful? Give feedback.
-
Bug Report
Description
Trying to deploy an existing serverless project. Running
serverless deploy
, the command runs for a short time (packaging via webpack), but then exits with no error/message and the function is not deployed.Same happens when running
serverless package
, or deploying through CD on serverless.com. The portal reports a successful deployment, but the application is not updated (verified by downloading the function from lambda - an old version). CD logs print success, followed by undefined where there is usually a link to view deployment:Here is the contents of the deployment bucket, note two deploys on 11th April.
And on the dashboard, 7 'successful' deployments (screenshot is truncated):
Based on the names of the folders in the deployment bucket, the last successful deploy was at 2020-04-11 11:23:28.
I've tried reverting to a known good commit from a week ago, and no difference.
Here is the full output of
SLS_DEBUG=* serverless deploy
:Beta Was this translation helpful? Give feedback.
All reactions