As of now, we can't jump straight to v4 in dev deps because some tests still require the v3 version (because we are mocking some stuff and the v4 only ship a binary).
The short solution is just to allow 4 in peer deps. But we prefer to have a running test that ensure a package is properly generated with deps inside.
As we can't use the internal tooling @serverless/test anymore in v4 (the project might be dead and no tests are running on the v4 official repo 😳, anyway) we are using the binary directly to package the example project. We were forced to use an access key from serverless dashboard and some aws valid credentials. But it now works ✅
As of now, we can't jump straight to v4 in dev deps because some tests still require the v3 version (because we are mocking some stuff and the v4 only ship a binary).
The short solution is just to allow
4in peer deps. But we prefer to have a running test that ensure a package is properly generated with deps inside.As we can't use the internal tooling
@serverless/testanymore in v4 (the project might be dead and no tests are running on the v4 official repo 😳, anyway) we are using the binary directly to package the example project. We were forced to use an access key from serverless dashboard and some aws valid credentials. But it now works ✅Fix https://github.com/serverless-heaven/serverless-webpack/issues/1923