-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
An error occured while creating pruned lockfile due to an issue with getParentPackage function #15835
Comments
Hi, we are facing with the same issue. But we use AWS SDK and createPackageJson is turned on webpack builder. |
We are facing the same issue |
Same here |
This issue is fixed by #15833 and will be rolled out in the upcoming 15.9.0 |
I still have it on 15.9.1:
|
@JumBay can you open another issue and provide repo where this can be reproduced? |
I think this one #16097 is the same issue |
still hitting this in 16.1.4 in my case its : Original error: Pruned lock file creation failed. The following package was not found in the root lock file: @nestjs/[email protected] ...but I have @nestjs/[email protected] installed. |
This issue has been closed for more than 30 days. If this issue is still occuring, please open a new issue with more recent context. |
Current Behavior
I am currently serving a NestJS application using the command nx serve api. However, I encounter an error message stating, "An error occurred while creating the pruned lockfile." Despite this error, the application compiles and runs successfully, and it also generates package.json and package-lock.json files in the dist directory. As a result, it is unclear what impact this error has on the process.
The error seems to originate from the getPackageParent function, which is utilized for lock-file generation. To provide a clearer understanding of the current issue, I will outline how this function operates:
At present, the function encounters a failure when consecutive segments return a parent with an undefined dependencies key, leading to the "undefined" error displayed in the failure log section. In the steps to reproduce, I have included a unit test that demonstrates this issue.
Expected Behavior
I would expect no error message.
GitHub Repo
See steps to reproduce below:
Steps to Reproduce
Here is a unit test to demonstrate the issue:
Nx Report
Failure Logs
Additional Information
No response
The text was updated successfully, but these errors were encountered: