You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to setup our prject to use nx-container but It would really help if there was some output about what the package is doing when running with NX_VERBOSE_LOGGING=true or nx <command> --verbose
I tried cloning the repo, and doing the changes myself, but when husky tries to validate package-lock.json, it can't read it.. It's probably something to do with my corporate windows computer (i know husky have issues with windows).
In plugins/nx-container/src/executors/build/ executor.ts I propose the following additions:
//...constargs: string[]=awaitengine.getArgs(inputs,defContext);constbuildCmd=engine.getCommand(args);logger.verbose(`Build command: ${buildCmd.command}${buildCmd.args.join(' ')}`);// <-- first additionawaitgetExecOutput(buildCmd.command,buildCmd.args.map((arg)=>interpolate(arg)),{ignoreReturnCode: true,}).then((res)=>{logger.verbose(res.stdout);// <-- Second additionif(res.stderr.length>0&&res.exitCode!=0){thrownewError(`buildx failed with: ${res.stderr.match(/(.*)\s*$/)?.[0]?.trim()??'unknown error'}`);}});awaitengine.finalize(inputs,ctx);//...
This would let you see the final build command that is sent to docker or what ever engine you are using, and It will let you see the output from that command.
The text was updated successfully, but these errors were encountered:
Alexamakans
pushed a commit
to Alexamakans/nx-tools
that referenced
this issue
Sep 5, 2024
I'm trying to setup our prject to use
nx-container
but It would really help if there was some output about what the package is doing when running withNX_VERBOSE_LOGGING=true
ornx <command> --verbose
I tried cloning the repo, and doing the changes myself, but when husky tries to validate package-lock.json, it can't read it.. It's probably something to do with my corporate windows computer (i know husky have issues with windows).
In
plugins/nx-container/src/executors/build/ executor.ts
I propose the following additions:This would let you see the final build command that is sent to docker or what ever engine you are using, and It will let you see the output from that command.
The text was updated successfully, but these errors were encountered: