Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Packing external modules: stderr maxBuffer exceeded

See original GitHub issue

I am using gitlab ci for building and deploy with serverless and i am getting this error.

Serverless: WARNING: Could not determine version of module nodes2ts
Serverless: Adding explicit peers for dependency graphql-tools
Serverless: WARNING: Could not determine version of module long
Serverless: Package lock found - Using locked versions
Serverless: Packing external modules: ramda@^0.24.1, nodes2ts, aws-sdk@^2.122.0, graphql-tools@^1.2.3, graphql@^0.11.3, jsonwebtoken@^8.1.0, apollo-server-lambda@^1.1.2, handlebars@^4.0.11, long
 
  Error --------------------------------------------------
 
  stderr maxBuffer exceeded
 
     For debugging logs, run again after setting the "SLS_DEBUG=*" environment variable.
 
  Get Support --------------------------------------------
     Docs:          docs.serverless.com
     Bugs:          github.com/serverless/serverless/issues
     Forums:        forum.serverless.com
     Chat:          gitter.im/serverless/serverless
 
  Your Environment Information -----------------------------
     OS:                     linux
     Node Version:           6.10.3
     Serverless Version:     1.24.0

Issue Analytics

State:
Created 6 years ago
Comments:7 (3 by maintainers)

Top GitHub Comments

1reaction

klimentLambevskicommented, Nov 27, 2017

Probably it is because i use npm 5 on local machine and npm 3 on docker.

0reactions

tommedemacommented, Dec 18, 2017

@HyperBrain in my case I use a lerna repo. And some of the packages use serverless-webpack, while others do not (they don’t even have functions often; but they have plugins). So I still benefit from having one root / project level package.json with all dev dependencies.

For now I will just use forceExclude; it’s only been a problem with aws-sdk. Still, I think this is a fair case, it would be better if it would include Nth level dependencies.