- Notifications
You must be signed in to change notification settings - Fork294
feat: support uv-managed projects#850
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
base:master
Are you sure you want to change the base?
Uh oh!
There was an error while loading.Please reload this page.
Conversation
stderr.includes( | ||
stdout.includes( |
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.
Something weird is going on here that, despite being thrown asthrow new serverless.classes.Error
it is being output on stdout instead of stderr. I'm uncertain of the cause, but I don't think it's related to this plugin.
Would love to have this! |
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
Uh oh!
There was an error while loading.Please reload this page.
Programmer-RD-AI commentedMay 24, 2025
I'm looking forward to this feature. UV support would be a great addition to the plugin. I appreciate the work on this! |
Uh oh!
There was an error while loading.Please reload this page.
Resolves#849
Adds support foruv managed projects, following the project's existing pattern of exporting a requirements file using the relevant project tool.
This does buck one-convention in this repo, in that it requires the user to have generated their own lock file, which is generally a best-practice when using one of these project management tools, and inspects for the existence of the
uv.lock
file as part of its check as to whether or not uv can be utilized with this plugin. This could be an issue for teams that are not otherwise committing their lock files to their repos and have automated deployments of their application in a CI/CD pipeline, although there exists trivial solutions to overcome that barrier.Note: there is another issue,#830, which also asks for uv support in replacing pip, which this PR does not intend to include.