-
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
When using Bun and building in containers, respect the yarn.lock file #25978
Comments
@Jordan-Hall kindly track this issue. I will work on getting a repo public to reproduce the issues so we can all debug more easily. Cc: @jaysoo |
@benpsnyder its not so much it needs to respect the yarn file here but they an issue with this line nx/packages/nx/src/plugins/js/index.ts Line 58 in 445916f
It's hitting the max buffer limit. Let me look into a solution for this |
@benpsnyder Could you do me a favour and check out the PR locally and try using the new solution please. I've not currently got a bigger enough project to test this on |
@Jordan-Hall I am building out a testing repo here https://github.com/benpsnyder/nx-bun-testing I will add a Dockerfile build system within 30-60 minutes |
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
Within your Dockerfile, use
bun install -y
which should generate ayarn.lock
See the errors faster if you use
ENV NX_DAEMON=false
; ifENV NX_DAEMON=true
then you will need to do something like this to see your errorsuse
bun nx run ...
and notbun --bun nx run ...
Expected Behavior
I expect builds to go forward using the
yarn.lock
without throwing this kind of messageGitHub Repo
https://github.com/benpsnyder/nx-bun-testing
Steps to Reproduce
Use https://github.com/benpsnyder/nx-bun-testing
Nx Report
Failure Logs
No response
Package Manager Version
bun 1.1.9
Operating System
Additional Information
No response
The text was updated successfully, but these errors were encountered: