serverless-nested-stack icon indicating copy to clipboard operation
serverless-nested-stack copied to clipboard

fix deploy error on node.js 10

Open desmondchou opened this issue 4 years ago • 7 comments

added callback function parameter when calling fs.writeFile in order to address issue #9

desmondchou avatar Oct 11 '19 03:10 desmondchou

@aditmalik-synechron Any chance we can get this merged in? node v8 is end of life next month on AWS.

willfarrell avatar Nov 11 '19 16:11 willfarrell

This patch works for me as expected.

dunin avatar Mar 14 '20 19:03 dunin

Can this be merged please? AWS Lambda Node 8 runtime has been deprecated for a while now and this is causing deployment issues.

sverraest avatar Mar 20 '20 03:03 sverraest

Facing the same issue as the rest, please have this merged. Thanks!

kedarnag138 avatar Sep 02 '20 12:09 kedarnag138

Any chance that we get this merged? Or any other package that has similar functionality out there?

vKongv avatar Sep 18 '20 03:09 vKongv

How do you revamp your serverless application to below the 200 limit? I have tried several approaches and all of them are not really elegant solutions to me...

I’m currently considering serverless-additional-stacks to split all my resources into a different stack and refer them in my lambda function through ImportValue fn On 18 Sep 2020, 12:22 PM +0800, desmondchou [email protected], wrote:

@desmondchou commented on this pull request. In index.js:

@@ -107,8 +107,7 @@ class ServerlessNestedPlugin {

                    this.serverless.service.provider.compiledCloudFormationTemplate = parentStack;
                    fs.writeFile(this.packagePath + '/compiled-cloudformation-template.json',
  •                        JSON.stringify(parentStack, null, ' '));
    
  •                    resolve();
    
  •                        JSON.stringify(parentStack, null, ' '), () => { resolve(); });
    

JSON.stringify(parentStack, null, ' '), resolve); This can probably work. However, I am no longer using this plugin already. I have revamped the lambda functions and shrink the no of objects. — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

vKongv avatar Sep 18 '20 04:09 vKongv

Luckily I managed to do it by consolidating handler functions. Reducing number of functions bring the total number of objects down below 200

desmondchou avatar Sep 19 '20 08:09 desmondchou