diff --git a/docs/generated/manifests/menus.json b/docs/generated/manifests/menus.json index 739a1d4e0a3f2..128c56ff3bc0e 100644 --- a/docs/generated/manifests/menus.json +++ b/docs/generated/manifests/menus.json @@ -86,6 +86,14 @@ "children": [], "disableCollapsible": false }, + { + "name": "Vue Standalone", + "path": "/getting-started/tutorials/vue-standalone-tutorial", + "id": "vue-standalone-tutorial", + "isExternal": false, + "children": [], + "disableCollapsible": false + }, { "name": "Node Standalone", "path": "/getting-started/tutorials/node-server-tutorial", @@ -178,6 +186,14 @@ "children": [], "disableCollapsible": false }, + { + "name": "Vue Standalone", + "path": "/getting-started/tutorials/vue-standalone-tutorial", + "id": "vue-standalone-tutorial", + "isExternal": false, + "children": [], + "disableCollapsible": false + }, { "name": "Node Standalone", "path": "/getting-started/tutorials/node-server-tutorial", @@ -237,6 +253,14 @@ "children": [], "disableCollapsible": false }, + { + "name": "Vue Standalone", + "path": "/getting-started/tutorials/vue-standalone-tutorial", + "id": "vue-standalone-tutorial", + "isExternal": false, + "children": [], + "disableCollapsible": false + }, { "name": "Node Standalone", "path": "/getting-started/tutorials/node-server-tutorial", diff --git a/docs/generated/manifests/nx.json b/docs/generated/manifests/nx.json index 7051ccb4fd8bd..73f014b7149f5 100644 --- a/docs/generated/manifests/nx.json +++ b/docs/generated/manifests/nx.json @@ -101,6 +101,16 @@ "path": "/getting-started/tutorials/angular-monorepo-tutorial", "tags": [] }, + { + "id": "vue-standalone-tutorial", + "name": "Vue Standalone", + "description": "", + "file": "shared/vue-standalone-tutorial/vue-standalone", + "itemList": [], + "isExternal": false, + "path": "/getting-started/tutorials/vue-standalone-tutorial", + "tags": [] + }, { "id": "node-server-tutorial", "name": "Node Standalone", @@ -217,6 +227,16 @@ "path": "/getting-started/tutorials/angular-monorepo-tutorial", "tags": [] }, + { + "id": "vue-standalone-tutorial", + "name": "Vue Standalone", + "description": "", + "file": "shared/vue-standalone-tutorial/vue-standalone", + "itemList": [], + "isExternal": false, + "path": "/getting-started/tutorials/vue-standalone-tutorial", + "tags": [] + }, { "id": "node-server-tutorial", "name": "Node Standalone", @@ -292,6 +312,16 @@ "path": "/getting-started/tutorials/angular-monorepo-tutorial", "tags": [] }, + "/getting-started/tutorials/vue-standalone-tutorial": { + "id": "vue-standalone-tutorial", + "name": "Vue Standalone", + "description": "", + "file": "shared/vue-standalone-tutorial/vue-standalone", + "itemList": [], + "isExternal": false, + "path": "/getting-started/tutorials/vue-standalone-tutorial", + "tags": [] + }, "/getting-started/tutorials/node-server-tutorial": { "id": "node-server-tutorial", "name": "Node Standalone", diff --git a/docs/map.json b/docs/map.json index 0344be49e5008..8efa10df9bfa9 100644 --- a/docs/map.json +++ b/docs/map.json @@ -63,6 +63,11 @@ "id": "angular-monorepo-tutorial", "file": "shared/angular-tutorial/angular-monorepo" }, + { + "name": "Vue Standalone", + "id": "vue-standalone-tutorial", + "file": "shared/vue-standalone-tutorial/vue-standalone" + }, { "name": "Node Standalone", "id": "node-server-tutorial", diff --git a/docs/shared/images/tutorial-vue-standalone/vue-tutorial-products-route.png b/docs/shared/images/tutorial-vue-standalone/vue-tutorial-products-route.png new file mode 100644 index 0000000000000..0137837eca698 Binary files /dev/null and b/docs/shared/images/tutorial-vue-standalone/vue-tutorial-products-route.png differ diff --git a/docs/shared/react-standalone-tutorial/react-standalone.md b/docs/shared/react-standalone-tutorial/react-standalone.md index 39291c482f1be..9cfa58514a3a5 100644 --- a/docs/shared/react-standalone-tutorial/react-standalone.md +++ b/docs/shared/react-standalone-tutorial/react-standalone.md @@ -237,7 +237,7 @@ Nx understands and supports both approaches, allowing you to define targets eith So, what are Nx Plugins? Nx Plugins are optional packages that extend the capabilities of Nx, catering to various specific technologies. For instance, we have plugins tailored to React (e.g., `@nx/react`), Vite (`@nx/vite`), Cypress (`@nx/cypress`), and more. These plugins offer additional features, making your development experience more efficient and enjoyable when working with specific tech stacks. -[visit our "Why Nx" page](/getting-started/why-nx) for more deails. +[Visit our "Why Nx" page](/getting-started/why-nx) for more details. ## Creating New Components diff --git a/docs/shared/reference/sitemap.md b/docs/shared/reference/sitemap.md index ded8f70cd3fea..cabe37b5b5e7d 100644 --- a/docs/shared/reference/sitemap.md +++ b/docs/shared/reference/sitemap.md @@ -11,6 +11,7 @@ - [React Monorepo](/getting-started/tutorials/react-monorepo-tutorial) - [Angular Standalone](/getting-started/tutorials/angular-standalone-tutorial) - [Angular Monorepo](/getting-started/tutorials/angular-monorepo-tutorial) + - [Vue Standalone](/getting-started/tutorials/vue-standalone-tutorial) - [Node Standalone](/getting-started/tutorials/node-server-tutorial) - [Core Tutorial](/core-tutorial) - [1 - Create Blog](/core-tutorial/01-create-blog) diff --git a/docs/shared/vue-standalone-tutorial/vue-standalone.md b/docs/shared/vue-standalone-tutorial/vue-standalone.md new file mode 100644 index 0000000000000..cbc93b650017b --- /dev/null +++ b/docs/shared/vue-standalone-tutorial/vue-standalone.md @@ -0,0 +1,846 @@ +# Building Vue Apps with the Nx Standalone Projects Setup + +In this tutorial you'll learn how to use Vue with Nx in a ["standalone" (non-monorepo) setup](/concepts/integrated-vs-package-based#standalone-applications). Not to be confused with the "Vue Standalone API", a standalone project in Nx is a non-monorepo setup where you have a single application at the root level. This setup is very similar to what the Vue CLI gives you. + +What are you going to learn? + +- how to create a new standalone (single-project) Nx workspace setup for Vue +- how to run a single task (i.e. serve your app) or run multiple tasks in parallel +- how to leverage code generators to scaffold components +- how to modularize your codebase and impose architectural constraints for better maintainability + +Note, while you could easily use Nx together with your manually set up Vue application, we're going to use the `@nx/vue` plugin for this tutorial which provides some nice enhancements when working with Vue. [Visit our "Why Nx" page](/getting-started/why-nx) to learn more about plugins and what role they play in the Nx architecture. + +## Warm Up + +Here's the source code of the final result for this tutorial. + +{% github-repository url="https://github.com/nrwl/nx-recipes/tree/main/vue-standalone" /%} + + + +## Creating a new Vue App + + + +Create a new Vue application with the following command: + +```{% command="npx create-nx-workspace@latest myvueapp --preset=vue-standalone" path="~" %} + > NX Let's create a new workspace [https://nx.dev/getting-started/intro] + +✔ Test runner to use for end to end (E2E) tests · cypress +✔ Default stylesheet format · css +✔ Enable distributed caching to make your CI faster · Yes + + > NX Creating your v17.0.0 workspace. + + To make sure the command works reliably in all environments, and that the preset is applied correctly, + Nx will run "npm install" several times. Please wait. +``` + +You can also choose [Playwright](/nx-api/playwright) for your e2e tests or a different stylesheet format. In this tutorial we're going to use Cypress and css. The above command generates the following structure: + +``` +└─ myvueapp + ├─ .vscode + │ └─ extensions.json + ├─ e2e + │ ├─ ... + │ ├─ project.json + │ ├─ src + │ │ ├─ e2e + │ │ │ └─ app.cy.ts + │ │ ├─ ... + │ └─ tsconfig.json + ├─ src + │ ├─ app + │ │ ├─ App.spec.ts + │ │ ├─ App.vue + │ │ └─ NxWelcome.vue + │ ├─ main.ts + │ └─ styles.css + ├─ index.html + ├─ nx.json + ├─ package.json + ├─ project.json + ├─ README.md + ├─ tsconfig.app.json + ├─ tsconfig.base.json + ├─ tsconfig.json + ├─ tsconfig.spec.json + └─ vite.config.ts +``` + +The setup includes.. + +- a new Vue application at the root of the Nx workspace (`src`) +- a Cypress based set of e2e tests (`e2e/`) +- Prettier preconfigured +- ESLint preconfigured +- Vitest preconfigured + +Let me explain a couple of things that might be new to you. + +| File | Description | +| -------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `nx.json` | This is where we fine-tune how Nx works. We define what [cacheable operations](/core-features/cache-task-results) there are, and configure our [task pipeline](/concepts/task-pipeline-configuration). More on that soon. | +| `project.json` | This file contains the targets that can be invoked for the `myreactapp` project. It is like a more evolved version of simple `package.json` scripts with more metadata attached. You can read more about it [here](/reference/project-configuration). | + +## Serving the App + + + +The most common tasks are already defined in the `package.json` file: + +```json {% fileName="package.json" %} +{ + "name": "myvueapp", + "scripts": { + "start": "nx serve", + "build": "nx build", + "test": "nx test" + } + ... +} +``` + +To serve your new Vue application, just run: `npm start`. Alternatively you can directly use Nx by using + +```shell +nx serve +``` + +Your application should be served at [http://localhost:4200](http://localhost:4200). + +Nx uses the following syntax to run tasks: + +![Syntax for Running Tasks in Nx](/shared/images/run-target-syntax.svg) + +All targets, such as `serve`, `build`, `test` or your custom ones, are defined in the `project.json` file. + +```json {% fileName="project.json"} +{ + "name": "myvueapp", + ... + "targets": { + "lint": { ... }, + "build": { ... }, + "serve": { ... }, + "preview": { ... }, + "test": { ... }, + "serve-static": { ... }, + }, +} +``` + +Each target contains a configuration object that tells Nx how to run that target. + +```json {% fileName="project.json"} +{ + "name": "myvueapp", + ... + "targets": { + "serve": { + "executor": "@nx/vite:dev-server", + "defaultConfiguration": "development", + "options": { + "buildTarget": "myvueapp:build" + }, + "configurations": { + "development": { + "buildTarget": "myvueapp:build:development", + "hmr": true + }, + "production": { + "buildTarget": "myvueapp:build:production", + "hmr": false + } + } + }, + ... + }, +} +``` + +The most critical parts are: + +- `executor` - this is of the syntax `:`, where the `plugin` is an NPM package containing an [Nx Plugin](/extending-nx/intro/getting-started) and `` points to a function that runs the task. In this case, the `@nx/vite` plugin contains the `dev-server` executor which serves the React app using Vite. +- `options` - these are additional properties and flags passed to the executor function to customize it + +Learn more about how to [run tasks with Nx](/core-features/run-tasks). + +## Testing and Linting - Running Multiple Tasks + + + +Our current setup not only has targets for serving and building the Vue application, but also has targets for unit testing, e2e testing and linting. Again, these are defined in the `project.json` file. We can use the same syntax as before to run these tasks: + +```bash +nx test # runs tests using Jest +nx lint # runs linting with ESLint +nx e2e e2e # runs e2e tests with Cypress +``` + +More conveniently, we can also run them in parallel using the following syntax: + +```{% command="nx run-many -t test lint e2e" path="myvueapp" %} + + ✔ nx run e2e:lint (1s) + ✔ nx run myvueapp:lint (1s) + ✔ nx run myvueapp:test (2s) + ✔ nx run e2e:e2e (6s) + + —————————————————————————————————————————————————————— + + > NX Successfully ran targets test, lint, e2e for 2 projects (8s) +``` + +### Caching + + + +One thing to highlight is that Nx is able to [cache the tasks you run](/core-features/cache-task-results). + +Note that all of these targets are automatically cached by Nx. If you re-run a single one or all of them again, you'll see that the task completes immediately. In addition, (as can be seen in the output example below) there will be a note that a matching cache result was found and therefore the task was not run again. + +```{% command="nx run-many -t test lint e2e" path="myvueapp" %} + + ✔ nx run myvueapp:lint [existing outputs match the cache, left as is] + ✔ nx run e2e:lint [existing outputs match the cache, left as is] + ✔ nx run myvueapp:test [existing outputs match the cache, left as is] + ✔ nx run e2e:e2e [existing outputs match the cache, left as is] + + ——————————————————————————————————————————————————————— + + > NX Successfully ran targets test, lint, e2e for 2 projects (143ms) + + Nx read the output from the cache instead of running the command for 4 out of 4 tasks. +``` + +Not all tasks might be cacheable though. You can mark all targets of a certain type as cacheable by setting `cache` to `true` in the `targetDefaults` of the `nx.json` file. You can also [learn more about how caching works](/core-features/cache-task-results). + +## Nx Plugins? Why? + + + +One thing you might be curious about is the project.json. You may wonder why we define tasks inside the `project.json` file instead of using the `package.json` file with scripts that directly launch Vite. + +Nx understands and supports both approaches, allowing you to define targets either in your `package.json` or `project.json` files. While both serve a similar purpose, the `project.json` file can be seen as an advanced form of `package.json` scripts, providing additional metadata and capabilities. In this tutorial, we utilize the `project.json` approach primarily because we take advantage of Nx Plugins. + +So, what are Nx Plugins? Nx Plugins are optional packages that extend the capabilities of Nx, catering to various specific technologies. For instance, we have plugins tailored to Vue (e.g., `@nx/vue`), Vite (`@nx/vite`), Cypress (`@nx/cypress`), and more. These plugins offer additional features, making your development experience more efficient and enjoyable when working with specific tech stacks. + +[Visit our "Why Nx" page](/getting-started/why-nx) for more details. + +## Creating New Components + + + +You can just create new React components as you normally would. However, Nx plugins usually also ship [generators](/core-features/plugin-features/use-code-generators). They allow you to easily scaffold code, configuration or entire projects. To see what capabilities the `@nx/vue` plugin ships, run the following command and inspect the output: + +```{% command="npx nx list @nx/vue" path="myvueapp" %} + +> NX Capabilities in @nx/vue: + + GENERATORS + + init : Initialize the `@nx/vue` plugin. + application : Create a Vue application. + library : Create a Vue library. + component : Create a Vue component. + setup-tailwind : Set up Tailwind configuration for a project. + storybook-configuration : Set up storybook for a Vue app or library. + stories : Create stories for all components declared in an app or library. +``` + +{% callout type="info" title="Prefer a more visual UI?" %} + +If you prefer a more integrated experience, you can install the "Nx Console" extension for your code editor. It has support for VSCode, IntelliJ and ships a LSP for Vim. Nx Console provides autocompletion support in Nx configuration files and has UIs for browsing and running generators. + +More info can be found in [the integrate with editors article](/core-features/integrate-with-editors). + +{% /callout %} + +Run the following command to generate a new "hello-world" component. Note how we append `--dry-run` to first check the output. + +```{% command="npx nx g @nx/vue:component hello-world --no-export --unit-test-runner=vitest --directory=src/components --dry-run" path="myvueapp" %} +> NX Generating @nx/vue:component + +CREATE src/components/hello-world.spec.ts +CREATE src/components/hello-world.vue + +NOTE: The "dryRun" flag means no changes were made. +``` + +As you can see it generates a new component in the `src/components/` folder. If you want to actually run the generator, remove the `--dry-run` flag. + +```ts {% fileName="src/components/hello-world.vue" %} + + + + + +``` + +## Building the App for Deployment + + + +If you're ready and want to ship your application, you can build it using + +```{% command="npx nx build" path="myvueapp" %} +> nx run myvueapp:build:production + +vite v4.3.9 building for production... +✓ 15 modules transformed. +dist/myvueapp/index.html 0.43 kB │ gzip: 0.29 kB +dist/myvueapp/assets/index-a0201bbf.css 7.90 kB │ gzip: 1.78 kB +dist/myvueapp/assets/index-46a11b5f.js 62.39 kB │ gzip: 24.35 kB +✓ built in 502ms + + ————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————— + + > NX Successfully ran target build for project myvueapp (957ms) +``` + +All the required files will be placed in the `dist/myvueapp` folder and can be deployed to your favorite hosting provider. + +## You're ready to go! + + + +In the previous sections you learned about the basics of using Nx, running tasks and navigating an Nx workspace. You're ready to ship features now! + +But there's more to learn. You have two possibilities here: + +- [Jump to the next steps section](#next-steps) to find where to go from here or +- keep reading and learn some more about what makes Nx unique when working with Vue. + +## Modularizing your Vue App with Local Libraries + + + +When you develop your Vue application, usually all your logic sits in the `app` folder. Ideally separated by various folder names which represent your "domains". As your app grows, this becomes more and more monolithic though. + +The following structure is a common example of this kind of monolithic code organization: + +``` +└─ myvueapp + ├─ ... + ├─ src + │ ├─ app + │ │ ├─ products + │ │ ├─ cart + │ │ ├─ ui + │ │ ├─ ... + │ │ └─ App.vue + │ ├─ ... + │ └─ main.ts + ├─ ... + ├─ package.json + ├─ ... +``` + +Nx allows you to separate this logic into "local libraries". The main benefits include + +- better separation of concerns +- better reusability +- more explicit "APIs" between your "domain areas" +- better scalability in CI by enabling independent test/lint/build commands for each library +- better scalability in your teams by allowing different teams to work on separate libraries + +### Creating Local Libraries + + + +Let's assume our domain areas include `products`, `orders` and some more generic design system components, called `ui`. We can generate a new library for each of these areas using the Vue library generator: + +``` +nx g @nx/vue:library products --directory=modules/products --unit-test-runner=vitest --bundler=vite +nx g @nx/vue:library orders --directory=modules/orders --unit-test-runner=vitest --bundler=vite +nx g @nx/vue:library shared-ui --directory=modules/shared/ui --unit-test-runner=vitest --bundler=vite +``` + +Note how we use the `--directory` flag to place the libraries into a subfolder. You can choose whatever folder structure you like, even keep all of them at the root-level. + +Running the above commands should lead to the following directory structure: + +``` +└─ myvueapp + ├─ ... + ├─ e2e/ + ├─ modules + │ ├─ products + │ │ ├─ .eslintrc.json + │ │ ├─ README.md + │ │ ├─ vite.config.ts + │ │ ├─ package.json + │ │ ├─ project.json + │ │ ├─ src + │ │ │ ├─ index.ts + │ │ │ ├─ components + │ │ │ │ ├─ products.spec.ts + │ │ │ │ └─ products.vue + │ │ │ └─ vue-shims.d.ts + │ │ ├─ tsconfig.json + │ │ ├─ tsconfig.lib.json + │ │ └─ tsconfig.spec.json + │ ├─ orders + │ │ ├─ ... + │ │ ├─ src + │ │ │ ├─ index.ts + │ │ │ ├─ components + │ │ │ │ ├─ ... + │ │ │ │ └─ orders.vue + │ │ ├─ ... + │ └─ shared + │ └─ ui + │ ├─ ... + │ ├─ src + │ │ ├─ index.ts + │ │ └─ components + │ │ └─ shared-ui.vue + │ └─ ... + ├─ ... + ├─ src + │ ├─ app + │ │ ├─ ... + │ │ ├─ App.vue + │ ├─ ... + ├─ ... +``` + +Each of these libraries + +- has its own `project.json` file with corresponding targets you can run (e.g. running tests for just orders: `nx test orders`) +- has a dedicated `index.ts` file which is the "public API" of the library +- is mapped in the `tsconfig.base.json` at the root of the workspace + +### Importing Libraries into the Vue Application + + + +All libraries that we generate automatically have aliases created in the root-level `tsconfig.base.json`. + +```json {% fileName="tsconfig.base.json" %} +{ + "compilerOptions": { + ... + "paths": { + "@myvueapp/orders": ["modules/orders/src/index.ts"], + "@myvueapp/products": ["modules/products/src/index.ts"], + "@myvueapp/shared-ui": ["modules/shared/ui/src/index.ts"] + }, + ... + }, +} +``` + +Hence we can easily import them into other libraries and our Vue application. For example: let's use our existing `Products` component in `modules/products/src/lib/products.vue`: + +```vue {% fileName="modules/products/src/lib/products.vue" %} + + + + + +``` + +Make sure the `Products` component is exported via the `index.ts` file of our `products` library (which it should already be). The `modules/products/src/index.ts` file is the public API for the `products` library with the rest of the workspace. Only export what's really necessary to be usable outside the library itself. + +```ts {% fileName="modules/products/src/index.ts" %} +export { default as Products } from './lib/products.vue'; +``` + +We're ready to import it into our main application now. First, let's set up the Vue Router. + +```shell +npm install vue-router --legacy-peer-deps +``` + +Configure it in the `main.ts` file. + +```ts {% fileName="src/main.ts" %} +import './styles.css'; + +import { createApp } from 'vue'; +import App from './app/App.vue'; +import NxWelcome from './app/NxWelcome.vue'; +import * as VueRouter from 'vue-router'; + +const routes = [ + { path: '/', component: NxWelcome }, + { + path: '/products', + component: () => import('@myvueapp/products').then((m) => m.Products), + }, +]; + +const router = VueRouter.createRouter({ + history: VueRouter.createWebHashHistory(), + routes, +}); + +const app = createApp(App); + +app.use(router); +app.mount('#root'); +``` + +Then we can set up navigation links and the `RouterView` in the main `App` component. + +```vue {% fileName="src/app/App.vue" %} + + + +``` + +If you now navigate to [http://localhost:4200/#/products](http://localhost:4200/#/products) you should see the `Products` component being rendered. + +![Browser screenshot of navigating to the products route](/shared/images/tutorial-vue-standalone/vue-tutorial-products-route.png) + +Let's do the same process for our `orders` library. Import the `Orders` component into the `main.ts` routes: + +```ts {% fileName="src/main.ts" %} +import './styles.css'; + +import { createApp } from 'vue'; +import App from './app/App.vue'; +import NxWelcome from './app/NxWelcome.vue'; +import * as VueRouter from 'vue-router'; + +const routes = [ + { path: '/', component: NxWelcome }, + { + path: '/products', + component: () => import('@myvueapp/products').then((m) => m.Products), + }, + { + path: '/orders', + component: () => import('@myvueapp/orders').then((m) => m.Orders), + }, +]; + +const router = VueRouter.createRouter({ + history: VueRouter.createWebHashHistory(), + routes, +}); + +const app = createApp(App); + +app.use(router); +app.mount('#root'); +``` + +And update the navigation links: + +```vue {% fileName="src/app/App.vue" %} + + + +``` + +Similarly, navigating to [http://localhost:4200/#/orders](http://localhost:4200/#/orders) should now render the `Orders` component. + +Note that both the `Products` component and `Orders` component are lazy loaded so the initial bundle size will be smaller. + +## Visualizing your Project Structure + + + +Nx automatically detects the dependencies between the various parts of your workspace and builds a [project graph](/core-features/explore-graph). This graph is used by Nx to perform various optimizations such as determining the correct order of execution when running tasks like `nx build`, identifying [affected projects](/core-features/run-tasks#run-tasks-affected-by-a-pr) and more. Interestingly you can also visualize it. + +Just run: + +```shell +nx graph +``` + +You should be able to see something similar to the following in your browser (hint: click the "Show all projects" button). + +{% graph height="450px" %} + +```json +{ + "projects": [ + { + "name": "myvueapp", + "type": "app", + "data": { + "tags": [] + } + }, + { + "name": "e2e", + "type": "e2e", + "data": { + "tags": [] + } + }, + { + "name": "shared-ui", + "type": "lib", + "data": { + "tags": [] + } + }, + { + "name": "orders", + "type": "lib", + "data": { + "tags": [] + } + }, + + { + "name": "products", + "type": "lib", + "data": { + "tags": [] + } + } + ], + "dependencies": { + "myvueapp": [ + { "source": "myvueapp", "target": "orders" }, + { "source": "myvueapp", "target": "products" } + ], + "e2e": [{ "source": "e2e", "target": "myvueapp", "type": "implicit" }], + "shared-ui": [], + "orders": [], + "products": [] + }, + "workspaceLayout": { "appsDir": "", "libsDir": "" }, + "affectedProjectIds": [], + "focus": null, + "groupByFolder": false +} +``` + +{% /graph %} + +Notice how `shared-ui` is not yet connected to anything because we didn't import it in any of our projects. Also the arrows to `orders` and `products` are dashed because we're using lazy imports. + +Exercise for you: change the codebase so that `shared-ui` is used by `orders` and `products`. Note: you need to restart the `nx graph` command to update the graph visualization or run the CLI command with the `--watch` flag. + +## Imposing Constraints with Module Boundary Rules + + + +Once you modularize your codebase you want to make sure that the modules are not coupled to each other in an uncontrolled way. Here are some examples of how we might want to guard our small demo workspace: + +- we might want to allow `orders` to import from `shared-ui` but not the other way around +- we might want to allow `orders` to import from `products` but not the other way around +- we might want to allow all libraries to import the `shared-ui` components, but not the other way around + +When building these kinds of constraints you usually have two dimensions: + +- **type of project:** what is the type of your library. Example: "feature" library, "utility" library, "data-access" library, "ui" library (see [library types](/concepts/more-concepts/library-types)) +- **scope (domain) of the project:** what domain area is covered by the project. Example: "orders", "products", "shared" ... this really depends on the type of product you're developing + +Nx comes with a generic mechanism that allows you to assign "tags" to projects. "tags" are arbitrary strings you can assign to a project that can be used later when defining boundaries between projects. For example, go to the `project.json` of your `orders` library and assign the tags `type:feature` and `scope:orders` to it. + +```json {% fileName="modules/orders/project.json" %} +{ + ... + "tags": ["type:feature", "scope:orders"], + ... +} +``` + +Then go to the `project.json` of your `products` library and assign the tags `type:feature` and `scope:products` to it. + +```json {% fileName="modules/products/project.json" %} +{ + ... + "tags": ["type:feature", "scope:products"], + ... +} +``` + +Finally, go to the `project.json` of the `shared-ui` library and assign the tags `type:ui` and `scope:shared` to it. + +```json {% fileName="modules/shared/ui/project.json" %} +{ + ... + "tags": ["type:ui", "scope:shared"], + ... +} +``` + +Notice how we assign `scope:shared` to our UI library because it is intended to be used throughout the workspace. + +Next, let's come up with a set of rules based on these tags: + +- `type:feature` should be able to import from `type:feature` and `type:ui` +- `type:ui` should only be able to import from `type:ui` +- `scope:orders` should be able to import from `scope:orders`, `scope:shared` and `scope:products` +- `scope:products` should be able to import from `scope:products` and `scope:shared` + +To enforce the rules, Nx ships with a custom ESLint rule. Open the `.eslintrc.base.json` at the root of the workspace and add the following `depConstraints` in the `@nx/enforce-module-boundaries` rule configuration: + +```json {% fileName=".eslintrc.base.json" %} +{ + ... + "overrides": [ + { + ... + "rules": { + "@nx/enforce-module-boundaries": [ + "error", + { + "enforceBuildableLibDependency": true, + "allow": [], + "depConstraints": [ + { + "sourceTag": "*", + "onlyDependOnLibsWithTags": ["*"] + }, + { + "sourceTag": "type:feature", + "onlyDependOnLibsWithTags": ["type:feature", "type:ui"] + }, + { + "sourceTag": "type:ui", + "onlyDependOnLibsWithTags": ["type:ui"] + }, + { + "sourceTag": "scope:orders", + "onlyDependOnLibsWithTags": [ + "scope:orders", + "scope:products", + "scope:shared" + ] + }, + { + "sourceTag": "scope:products", + "onlyDependOnLibsWithTags": ["scope:products", "scope:shared"] + }, + { + "sourceTag": "scope:shared", + "onlyDependOnLibsWithTags": ["scope:shared"] + } + ] + } + ] + } + }, + ... + ] +} +``` + +To test it, go to your `modules/products/src/lib/products.vue` file and import the `Orders` component from the `orders` project: + +```tsx {% fileName="modules/products/src/lib/products.vue" %} + + + + + +``` + +If you lint your workspace you'll get an error now: + +```{% command="nx run-many -t lint" %} + > NX Running target lint for 5 projects + ✖ nx run products:lint + Linting "products"... + + /Users/isaac/Documents/code/nx-recipes/vue-standalone/modules/products/src/lib/products.vue + 5:1 error A project tagged with "scope:products" can only depend on libs tagged with "scope:products", "scope:shared" @nx/enforce-module-boundaries + 5:10 warning 'Orders' is defined but never used @typescript-eslint/no-unused-vars + + ✖ 2 problems (1 error, 1 warning) + + Lint warnings found in the listed files. + + Lint errors found in the listed files. + + + ✔ nx run orders:lint (913ms) + ✔ nx run e2e:lint [existing outputs match the cache, left as is] + ✔ nx run myvueapp:lint (870ms) + ✔ nx run shared-ui:lint (688ms) + + —————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————— + + > NX Ran target lint for 5 projects (2s) + + ✔ 4/5 succeeded [1 read from cache] + + ✖ 1/5 targets failed, including the following: + - nx run products:lint + +``` + +Learn more about how to [enforce module boundaries](/core-features/enforce-module-boundaries). + +## Migrating to a Monorepo + +When you are ready to add another application to the repo, you'll probably want to move `myvueapp` to its own folder. To do this, you can run the [`convert-to-monorepo` generator](/nx-api/workspace/generators/convert-to-monorepo) or [manually move the configuration files](/recipes/tips-n-tricks/standalone-to-integrated). + +## Next Steps + +Congrats, you made it!! You now know how to leverage the Nx standalone applications preset to build modular Vue applications. + +Here's some more things you can dive into next: + +- Learn more about the [underlying mental model of Nx](/concepts/mental-model) +- [Speed up CI: Run only tasks for project that got changed](/core-features/run-tasks#run-tasks-affected-by-a-pr) +- [Speed up CI: Share your cache](/core-features/remote-cache) +- [Speed up CI: Distribute your tasks across machines](/core-features/distribute-task-execution) + +Also, make sure you + +- [Join the Official Nx Discord Server](https://go.nx.dev/community) to ask questions and find out the latest news about Nx. +- [Follow Nx on Twitter](https://twitter.com/nxdevtools) to stay up to date with Nx news +- [Read our Nx blog](https://blog.nrwl.io/) +- [Subscribe to our Youtube channel](https://www.youtube.com/@nxdevtools) for demos and Nx insights