Closed benpsnyder closed 3 months ago
Here is the output with NX_DAEMON=true
; line 11 is a workaround so line 12 I can output the log to console
Success with bun --bun nx
; please note bun nx
did not work
@jaysoo / @Jordan-Hall you may be interested in this ^
Success with
bun --bun nx
; please notebun nx
did not work@jaysoo / @Jordan-Hall you may be interested in this ^
So forcing nx to run in complete bun working fine hmm I wonder if its soemthing missing inside bun then. I'll have to try and debug it soon
Opened https://github.com/nrwl/nx/issues/25978 to track building with bun nx run ....
(not bun --bun
) while also installing with bun install -y
to produce a yarn.lock
file
Opened #25978 to track building with
bun nx run ....
(notbun --bun
) while also installing withbun install -y
to produce ayarn.lock
file
We dont need to use yarn.lock here. The reason for failing is the same. bun has a better max buffer by default. I think the solution will work for it
I am building out a testing repo here: https://github.com/benpsnyder/nx-bun-testing
Is this related to this problem or should it be a separate issue? If no bun.lockb projects runs fine, if bun.lockb is present then it errors:
* Executing task: bun nx run my-project:serve
$ nx run my-project:serve
node:internal/process/promises:289
triggerUncaughtException(err, true /* fromPromise */);
^
[Failed to process project graph. Run "nx reset" to fix this. Please report the issue if you keep seeing it.
The "nx/js/dependencies-and-lockfile" plugin threw an error while creating dependencies:
Error: Target project does not exist: npm:http-proxy-middleware
at validateCommonDependencyRules (/Projects/my-project/node_modules/nx/src/project-graph/project-graph-builder.js:323:15)
at validateDependency (/Projects/my-project/node_modules/nx/src/project-graph/project-graph-builder.js:313:5)
at /Projects/my-project/node_modules/nx/src/plugins/js/lock-file/yarn-parser.js:214:80
at Array.forEach (<anonymous>)
at /Projects/my-project/node_modules/nx/src/plugins/js/lock-file/yarn-parser.js:205:49
at Array.forEach (<anonymous>)
at /Projects/my-project/node_modules/nx/src/plugins/js/lock-file/yarn-parser.js:203:72
at Array.forEach (<anonymous>)
at /Projects/my-project/node_modules/nx/src/plugins/js/lock-file/yarn-parser.js:200:26
at Array.forEach (<anonymous>)] {
name: 'ProjectGraphError'
}
Is this related to this problem or should it be a separate issue? If no bun.lockb projects runs fine, if bun.lockb is present then it errors:
* Executing task: bun nx run my-project:serve $ nx run my-project:serve node:internal/process/promises:289 triggerUncaughtException(err, true /* fromPromise */); ^ [Failed to process project graph. Run "nx reset" to fix this. Please report the issue if you keep seeing it. The "nx/js/dependencies-and-lockfile" plugin threw an error while creating dependencies: Error: Target project does not exist: npm:http-proxy-middleware at validateCommonDependencyRules (/Projects/my-project/node_modules/nx/src/project-graph/project-graph-builder.js:323:15) at validateDependency (/Projects/my-project/node_modules/nx/src/project-graph/project-graph-builder.js:313:5) at /Projects/my-project/node_modules/nx/src/plugins/js/lock-file/yarn-parser.js:214:80 at Array.forEach (<anonymous>) at /Projects/my-project/node_modules/nx/src/plugins/js/lock-file/yarn-parser.js:205:49 at Array.forEach (<anonymous>) at /Projects/my-project/node_modules/nx/src/plugins/js/lock-file/yarn-parser.js:203:72 at Array.forEach (<anonymous>) at /Projects/my-project/node_modules/nx/src/plugins/js/lock-file/yarn-parser.js:200:26 at Array.forEach (<anonymous>)] { name: 'ProjectGraphError' }
This is different, this looks like not everything is copied into the docker. npm:http-proxy-middleware. This is missing
Error: Target project does not exist: npm:http-proxy-middleware
@benpsnyder can you check with 19.2 beta please to see if this still exists?
Fixed in latest beta release :)
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
My
buildbase
image has already copied the whole repo (./
) and lines 6, 7, and 8 in this screenshot are just copying any changed files. I added lines 10, 11 and 12 for my testing process.Expected Behavior
I expected to be able to build all my apps.
GitHub Repo
https://github.com/benpsnyder/nx-bun-testing
Steps to Reproduce
Use a Dockerfile (perhaps with a docker-compose.yaml) to copy in a repo using bun as the package manager. Note I am not using a yarn lock file.
Nx Report
Failure Logs
No response
Package Manager Version
bun 1.1.9
Operating System
Additional Information
No response