-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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(lambda-nodejs): pnpm installs frozen lockfile in a CI environment #24781
Conversation
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.
The pull request linter has failed. See the aws-cdk-automation comment below for failure reasons. If you believe this pull request should receive an exemption, please comment and provide a justification.
A comment requesting an exemption should contain the text Exemption Request
. Additionally, if clarification is needed add Clarification Request
to a comment.
Looking for an Exemption Request for the integration test as well. |
To provide the exemption request, can you please describe how this was manually tested? I am inclined to agree that this is difficult to write an automated test for. |
I'm removing the exemption request label for now. Please use a quote reply to my last message to add it back when you respond to my question so I see that this needs another look. Thanks for you work here! |
Hey @TheRealAmazonKendra! Appreciate your help with this! This was manually tested locally using the command dumped in the error output of the current command. Removing/replacing the asset staging path with a local one and rerunning the same commands in order (with the without mkdir asset-staging && \
echo '{"dependencies":{"pg":"8.10.0"}}' > "asset-staging/package.json" && \
cp "pnpm-lock.yaml" "asset-staging/pnpm-lock.yaml" && \
cd asset-staging && \
CI=true pnpm install --config.node-linker=hoisted --config.package-import-method=clone-or-copy && \
rm "node_modules/.modules.yaml" with mkdir asset-staging && \
echo '{"dependencies":{"pg":"8.10.0"}}' > "asset-staging/package.json" && \
cp "pnpm-lock.yaml" "asset-staging/pnpm-lock.yaml" && \
cd asset-staging && \
CI=true pnpm install --config.node-linker=hoisted --config.package-import-method=clone-or-copy --no-prefer-frozen-lockfile && \
rm "node_modules/.modules.yaml" |
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.
Thank you for your contribution!
✅ Updated pull request passes all PRLinter validations. Dissmissing previous PRLinter review.
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
@Mergifyio refresh |
✅ Pull request refreshed |
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
I there any ETA when this fix will be published? |
pnpm automatically enables
--frozen-lockfile
in CI environments which breaksNodejsFunction
local bundling.This change appends the
--no-prefer-frozen-lockfile
flag as described in pnpm/pnpm#1994 (comment)By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license