-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
fix(remix-dev/cli): remove AWS Lamba
copy
#6484
Conversation
🦋 Changeset detectedLatest commit: 942965c The changes in this PR will be included in the next version bump. This PR includes changesets to release 18 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Hi @fwang, Welcome, and thank you for contributing to Remix! Before we consider your pull request, we ask that you sign our Contributor License Agreement (CLA). We require this only once. You may review the CLA and sign it by adding your name to contributors.yml. Once the CLA is signed, the If you have already signed the CLA and received this response in error, or if you have any questions, please contact us at [email protected]. Thanks! - The Remix team |
Thank you for signing the Contributor License Agreement. Let's get this merged! 🥳 |
AWS Lamba
copy
Thanks @fwang! |
🤖 Hello there, We just published version Thanks! |
🤖 Hello there, We just published version Thanks! |
Hm, we must have a bug in our bot logic - this is not included in https://github.com/remix-run/remix/compare/[email protected]@1.17.1-pre.1 |
🤖 Hello there, We just published version Thanks! |
🤖 Hello there, We just published version Thanks! |
🤖 Hello there, We just published version Thanks! |
🤖 Hello there, We just published version Thanks! |
Hi team, I'm a maintainer of SST. SST helps Remix users deploy their Remix apps to AWS.
We've received feedback indicating that the
Architect (AWS Lambda)
option in thecreate-remix
flow is causing some confusion. SST wraps around the defaultRemix App Server
inside a Lambda handler, but we've noticed several users mistakenly selecting theArchitect (AWS Lambda)
deployment target. (please see the attached screenshot for reference)This PR removed the
AWS Lambda
copy from theArchitect
deployment target to alleviate this confusion.