-
### Current Behavior
I am using `nx@19.8.6' instead of `nx@latest`, which results in the same issue. When I create a Go workspace using the command specified in your docs, it creates the workspace.…
-
### Current Behavior
Attempting to upgrade an angular 16 project to 18, however I assume I need to upgrade nx as well. I am currently using 16.3.2, but I have installed nx 20.1.2 globally. Running th…
-
### Current Behavior
After upgrading to nx version `20.1.0` following the steps in https://nx.dev/nx-api/nx/documents/migrate, i faced a bug where a remote frontend is not working. After serving the …
-
`nx release` doesn't build libraries. And we can't build them before running a script because versions must be bumped first. So the current workaround is to run everything manually. The possible solut…
-
### Current Behavior
I first thought it is a question, thus I asked it [here](https://github.com/nrwl/nx/discussions/28990#discussion-7512851). But as you can see there this `nx upgrade latest` does …
-
### Current Behavior
When running `nx serve test-app` and then later closing the terminal tab/window the app is running in, node continues to run and immediately starts using 100% CPU until the proce…
-
### Current Behavior
With `@nx/vite/plugin` installed and `vite.config.ts` referencing the Remix Cloudflare plugin, every time the Nx daemon reads the Vite config file, it spawns a [`workerd`](https:…
-
### Current Behavior
There are certain times when `@nx/workspace:move` will not move libraries when I need it to, instead choosing to print up an error (as seen in the appropriate later field, which …
-
### Current Behavior
I just installed a fresh Nx workspace and can't generate a NestJS or NextJS app, as it says it doesn't "support the current TypeScript" setup, whatever that means. Even using `--…
-
**Describe the bug**
The tool is not able to read the electron version on a nx-electron. I assume this is due to the fact that the package.json sits at the root of the nx-monorepo project instead of …