You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I use yarn as my packager for serverless-webpack. In my package.json I have defined resolutions to force yarn to use a specific version of a dependency. This works quite well in my project, but it won't get applied when I run sls webpack.
In my output folder of serverless-webpack (.webpack/) is a package.json without the resolutions field. If I run yarn list <package> I get multiple entries of this dependency where I expected exactly one. If I run yarn install --frozen-lockfile I get Lockfile has incorrect entry for "graphql@^0.11.7". Ignoring it. which leads to this missbehavior.
Hi @otbe ,
thanks for raising the issue. I think this is a bug in serverless-webpack. It should be fixed to use and copy the resolutions definition from your original package.json to the created ones.
As you confirmed that adding the section solves the problem, this should be the right way to go.
This is a Bug Report
Description
I use yarn as my packager for serverless-webpack. In my
package.json
I have definedresolutions
to force yarn to use a specific version of a dependency. This works quite well in my project, but it won't get applied when I runsls webpack
.In my output folder of
serverless-webpack
(.webpack/) is a package.json without the resolutions field. If I runyarn list <package>
I get multiple entries of this dependency where I expected exactly one. If I runyarn install --frozen-lockfile
I getLockfile has incorrect entry for "graphql@^0.11.7". Ignoring it.
which leads to this missbehavior.This is my serverless-webpack related config:
If I add
resolutions
to package.json it works as it should.This may be a bug within yarn itself, because I expect when using
--frozen-lockfile
it should take whats in the lockfile.Versions:
serverless-webpack@5.1.3
webpack@4.6.0
serverless@1.26.1
yarn@1.6.0
Thanks!
The text was updated successfully, but these errors were encountered: