nx
nx copied to clipboard
Smart Monorepos · Fast CI
## Current Behavior When building applications that depend on workspace libraries for deployment (particularly in containerized environments like Docker), developers must manually handle copying workspace dependencies and updating package.json references....
### Current Behavior nx 18 induces the following type errors: ``` node_modules/@types/node/fs.d.ts:21:1 - error TS6200: Definitions of the following identifiers conflict with those in another file: Type, promises, PathLike, PathOrFileDescriptor,...
## Current Behavior In the new TS Soln Setup with Package Manager Workspaces, there is currently no builtin method for creating a pruned lockfile that is agnostic across bundlers and...
### Current Behavior After updating Nx from version 21.1.2 to 21.1.3, the Angular application fails to compile. The console displays the following error: ```bash node:path - Error: Module build failed:...
### Current Behavior Since v21 Vite preview mode with `--watch` argument doesn't work anymore. This used to rebuild the project automatically on file change. Related PR - https://github.com/nrwl/nx/pull/14412 Same happens...
### Current Behavior If the outputPath for a project points to a directory outside the workspace, initial builds work correctly and build artifacts are created in the desired directory. However,...
## Current Behavior fix to run gradle on windows ./gradlew command is only macos ## Expected Behavior use @nx/gradle:gradle executor instead of command ./gradlew ## Related Issue(s) Fixes #
## Current Behavior Headings in the documentation site are wrongly arranged, making it difficult to navigate.  ## Expected Behavior "Options" heading should be nested inside the parent heading topic.
## Current Behavior Running Angular CLI schematic migrations that update project configurations that contain Nx tokens (e.g. `{workspaceRoot}`, `{projectRoot}`, `{projectName}`) does not work correctly. The schematic migrations receive the project...
### Current Behavior Naming project with a leading number seems to fail at the end of running `create-nx-workspace` ### Expected Behavior The `create-nx-workspace` should either allow the name to pass...