@nx/node

Using @nx/node daily in a monorepo with multiple Node services has been largely positive. The generators (`nx g @nx/node:application` and `nx g @nx/node:library`) create well-structured projects with sensible defaults including TypeScript, ESLint, and Jest configurations. The TypeScript support is first-class with proper path mappings and project references that actually work out of the box. IDE autocomplete for workspace libraries is seamless.

The build orchestration and caching are where this really shines - dependency graph-based task execution means you only rebuild what changed. The `serve` executor supports watch mode with fast rebuilds. Error messages during build failures are clear and point to the actual issue, not buried in orchestration noise.

Migration between versions can be bumpy when Nx makes breaking changes to executors or project structure. The documentation is comprehensive but sometimes lags behind latest features. You'll occasionally need to dig into the source to understand executor options that aren't well documented.

Using @nx/node daily in production monorepos has been largely positive from a security perspective. The generated Node applications come with sensible TypeScript configurations that catch type-related vulnerabilities at compile time. The build process properly handles environment variables without leaking secrets into bundles, and the generated .gitignore patterns appropriately exclude sensitive files.

One notable strength is the clear separation between build artifacts and source code, which helps prevent accidental deployment of development dependencies. The webpack configurations generated for production builds strip development-only code effectively. However, dependency management requires vigilance—Nx doesn't enforce any special supply chain security practices beyond standard npm, so you're still responsible for tools like npm audit and lock file integrity.

Error handling in generated code is minimal but not dangerous—it doesn't expose stack traces in production by default. The authentication/authorization patterns are intentionally left to you, which is appropriate for a build tool. TLS configuration for HTTPS servers isn't scaffolded, requiring manual setup with proper certificate validation.

Using @nx/node daily in a monorepo with multiple Node services has been largely positive. The generators (`nx g @nx/node:application` and `nx g @nx/node:library`) scaffold projects quickly with sensible defaults including TypeScript, Jest, and ESLint configurations. The best part is how seamlessly it integrates with Nx's computation caching - builds and tests only run when dependencies actually change, which saves massive amounts of CI time.

The learning curve is moderate if you're new to Nx. The documentation covers common scenarios well, with clear examples of setting up Express apps, configuring build options, and managing dependencies. Error messages are generally helpful, especially around circular dependencies and misconfigured project boundaries. When things break, the `nx graph` command is invaluable for debugging dependency issues.

The main friction point is understanding Nx's project configuration structure (project.json vs workspace-level settings). Migration guides between major versions can be sparse, and some breaking changes require manual intervention. GitHub issue response time is reasonable, though some edge cases remain unresolved for extended periods.