-
-
Notifications
You must be signed in to change notification settings - Fork 140
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: adds noInstall
option for Yarn packager
#421
feat: adds noInstall
option for Yarn packager
#421
Conversation
noInstall
option for Yarn packager
hi @chrishutchinson not sure how to cover it with e2e test either. seems like |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@chrishutchinson lgtm, thank you for your contribution👍🏼
@all-contributors please add @chrishutchinson for the new code, small but valuable contribution |
🎉 This PR is included in version 1.37.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
I've put up a pull request to add @chrishutchinson! 🎉 |
I've been trying to get
serverless-esbuild
working with my Yarn 3.x setup, and as far as I understand the package is not compatible at the moment. After doing some testing locally, and comparing this toserverless-webpack
, it looks like just deactivating the install step should be enough to get it working in my context.As such, and following the implementation in
serverless-webpack
here, I have added anoInstall
packagerOptions
option, which exits out of the install process early. This trusts I have installed the dependencies myself.I wanted to add an e2e test to cover this scenario but I couldn't quite follow the setup of
individually
vs.complete
etc. I think I actually just want a dedicated e2e suite that is a copy of minimal with Yarn as the package manager, but I'd happily take guidance on what that should look like.Thank you!