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
Describe the bug
When using Serverless V4, serverless-esbuild and serverless-s3-sync, the sls package command gets stuck in the step Packaging.
I tracked it down to being caused by s3-sync using https://github.com/auth0/node-s3-client. If you include require('@auth0/s3'); in the index.ts of serverless-esbuild, the open event on the writeStream here will not be called and the promise never returns.
Moving serverless-s3-sync to the top of the plugins in serverless.yml seems to solve the problem in some cases, at least when serverless-domain-manager is between serverless-s3-sync and serverless-esbuild.
Steps to Reproduce
Open a project with serverless v4 and serverless-esbuild
Install @auth0/s3: npm i @auth0/s3
Add require('@auth0/s3'); to node_modules/serverless-esbuild/dist/index.js
Run Serverless: npx sls package --verbose
Screenshots
Versions (please complete the following information):
OS: Mac
Serverless Framework Version: 4.4.11
Plugin Version: 1.54.6
The text was updated successfully, but these errors were encountered:
Describe the bug
When using Serverless V4, serverless-esbuild and serverless-s3-sync, the
sls package
command gets stuck in the stepPackaging
.I tracked it down to being caused by s3-sync using https://github.com/auth0/node-s3-client. If you include
require('@auth0/s3');
in the index.ts of serverless-esbuild, theopen
event on the writeStream here will not be called and the promise never returns.Moving serverless-s3-sync to the top of the plugins in serverless.yml seems to solve the problem in some cases, at least when serverless-domain-manager is between serverless-s3-sync and serverless-esbuild.
Steps to Reproduce
npm i @auth0/s3
require('@auth0/s3');
to node_modules/serverless-esbuild/dist/index.jsnpx sls package --verbose
Screenshots
Versions (please complete the following information):
The text was updated successfully, but these errors were encountered: