Closed benpsnyder closed 3 months ago
@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 https://github.com/nrwl/nx/blob/445916f18a3065fcabd1bac0e1a4369ad1ec1d73/packages/nx/src/plugins/js/index.ts#L58 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 useENV 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