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.

Support yarn 2 version

See original GitHub issue

Add support for `Yarn 2.*`

Description

For bug reports:

What went wrong? Running sls package with yarn 2.22.2 results in error:

Error: yarn install --frozen-lockfile --non-interactive failed with code 1

What did you expect should have happened? Build package without any errors
What was the config you used?

    webpack:
        webpackConfig: ./buildWebpackConfig.js
        includeModules: true
        packager: 'yarn'
        excludeFiles: src/**/__tests__/*

What stacktrace or error message from your provider did you see?

For feature proposals:

Update this command https://github.com/serverless-heaven/serverless-webpack/blob/38135e4443c7d7e8506010f0c3e411220abe6f24/lib/packagers/yarn.js#L120

So it will executed succesfully with yarn 2.* version. Example: yarn install --immutable --immutable-cache https://yarnpkg.com/cli/install

Additional Data

Serverless-Webpack Version you’re using: 5.3.5
Webpack version you’re using: 4.29.6
Serverless Framework Version you’re using: 1.74.1
Operating System: darwin
Stack Trace (if available):

  Error: yarn install --frozen-lockfile --non-interactive failed with code 1
      at ChildProcess.<anonymous> (/Users/user/projects/lambda/node_modules/serverless-webpack/lib/utils.js:91:16)
      at ChildProcess.emit (events.js:223:5)
      at ChildProcess.EventEmitter.emit (domain.js:475:20)
      at maybeClose (internal/child_process.js:1021:16)
      at Process.ChildProcess._handle.onexit (internal/child_process.js:283:5)