✨ Your new, shiny Nx workspace is almost ready ✨.
Learn more about this workspace setup and its capabilities or run npx nx graph to visually explore what was created. Now, let's get you up to speed!
libs/
├── tell-it/
│ ├── web/ # Angular-specific libraries
│ │ ├── feature/ # Angular feature libraries
│ │ ├── ui/ # Angular UI components
│ │ └── data-access/ # Angular services
│ ├── api/ # NestJS-specific libraries
│ │ ├── feature/ # NestJS feature modules
│ │ └── data-access/ # NestJS services, repositories
│ └── shared/ # Shared between web and api
│ ├── models/ # Shared interfaces/types
│ └── util/ # Shared utilities
├── shared/ # Cross-domain shared code
To run any task with Nx use:
npx nx <target> <project-name>These targets are either inferred automatically or defined in the project.json or package.json files.
More about running tasks in the docs »
To deploy an application:
nx deploy
For APIs, dockerfiles are used to generate docker images. Make sure to correctly setup the registry to allow the repo to push images. Manage package settings > Choose repo > Role: Admin
Learn more about Nx release »
Nx automatically updates TypeScript project references in tsconfig.json files to ensure they remain accurate based on your project dependencies (import or require statements). This sync is automatically done when running tasks such as build or typecheck, which require updated references to function correctly.
To manually trigger the process to sync the project graph dependencies information to the TypeScript project references, run the following command:
npx nx syncYou can enforce that the TypeScript project references are always in the correct state when running in CI by adding a step to your CI job configuration that runs the following command:
npx nx sync:check