nx-tools
nx-tools copied to clipboard
Nx Workspaces builders and tools
[](https://renovatebot.com) This PR contains the following updates: | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | [eslint-config-prettier](https://togithub.com/prettier/eslint-config-prettier) | [`9.0.0` -> `9.1.0`](https://renovatebot.com/diffs/npm/eslint-config-prettier/9.0.0/9.1.0) | [](https://docs.renovatebot.com/merge-confidence/)...
This PR contains the following updates: | Update | Change | |---|---| | lockFileMaintenance | All locks refreshed | 🔧 This Pull Request updates lock files to use the latest...
Hello, Are you planning to add Crystal support? Something like the following ```json { "plugin": "@nx-tools/nx-container", "options": { "buildTargetName": "container-build", } }, ``` you can infer the build target by...
The `secret-files` option for `@nx-tools/nx-container:build` seemingly ignores environment variables. I have a target defined like ``` "docker-build": { "dependsOn": ["build"], "executor": "@nx-tools/nx-container:build", "options": { "target": "production", "build-args": ["NODE_VERSION"], "context": "dist/{projectRoot}",...
**Description:** Currently, the `@nx-tools/nx-container` plugin generates Dockerfiles with npm commands for package installations, regardless of the package manager set in the nx.json file. To enhance compatibility and streamline development workflows,...
I'm trying to use @nx-tools/nx-container with yarn v4.3.0 with pnp install mode. Fails because PackageLoader only checks node_modules for a given package (@nx-tools/container-metadata in my case)  I believe there's...
I'll open a PR for this myself if you agree with the idea and will review it. `context` and `file` settings seem to be relative to where you run the...
I run nx-containers using Buildbot as our CI. The command `npx nx affected --base=origin/development --head= --target=container --parallel=1` fails with the following error: ``` Unsupported CI Provider... Using Local Environment as...
`@jscutlery/semver` generates a short git hash of 8 characters in length. Where `@nx-tools/container-metadata` default is 7. I had to dig into the code to find this `process.env.NX_CONTAINER_SHORT_SHA_LENGTH`, to figure out...
I don't know if anyone is experiencing this issue, but when we try to build with kaniko everything goes fine (no error shown). When we deploy the image in production...