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. 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 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.

Example repository/nrwl/nx-recipes/tree/main/vue-standalone

Creating a new Vue App

Create a new Vue application with the following command:

~❯

npx create-nx-workspace@latest myvueapp --preset=vue-standalone

1  NX   Let's create a new workspace [https://nx.dev/getting-started/intro]
2
3✔ Test runner to use for end to end (E2E) tests · cypress
4✔ Default stylesheet format · css
5✔ Set up CI with caching, distribution and test deflaking · github
6
7  NX   Creating your v17.0.0 workspace.
8
9   To make sure the command works reliably in all environments, and that the preset is applied correctly,
10   Nx will run "npm install" several times. Please wait.
11

You can also choose 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 there are, and configure our task pipeline. More on that soon.
`project.json`	This file is where you can modify the inferred tasks for the `myvueapp` project. More about this later.

Serving the App

The most common tasks are already defined in the package.json file:

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

❯

nx serve

Your application should be served at http://localhost:4200.

Nx uses the following syntax to run tasks:

Syntax for Running Tasks in Nx

Inferred Tasks

Nx identifies available tasks for your project from tooling configuration files, package.json scripts and the targets defined in project.json. To view the tasks that Nx has detected, look in the Nx Console project detail view or run:

❯

nx show project myvueapp --web

Project Details View (Simplified)

myvueapp

Root: .

Type: Application

Targets

build
vite build
Cacheable

If you expand the build task, you can see that it was created by the @nx/vite plugin by analyzing your vite.config.ts file. Notice the outputs are defined as {projectRoot}/dist/myvueapp. This value is being read from the build.outDir defined in your vite.config.ts file. Let's change that value in your vite.config.ts file:

vite.config.ts
export default defineConfig({
  // ...
  build: {
    outDir: './build/myvueapp',
    // ...
  },
});

Now if you look at the project details view, the outputs for the build target will say {projectRoot}/build/myvueapp. This feature ensures that Nx will always cache the correct files.

You can also override the settings for inferred tasks by modifying the targetDefaults in nx.json or setting a value in your project.json file. Nx will merge the values from the inferred tasks with the values you define in targetDefaults and in your specific project's configuration.

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. We can use the same syntax as before to run these tasks:

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:

myvueapp❯

nx run-many -t test lint e2e

1
2    ✔  nx run e2e:lint (1s)
3    ✔  nx run myvueapp:lint (1s)
4    ✔  nx run myvueapp:test (2s)
5    ✔  nx run e2e:e2e (6s)
6
7 ——————————————————————————————————————————————————————
8
9  NX   Successfully ran targets test, lint, e2e for 2 projects (8s)
10

Caching

One thing to highlight is that Nx is able to cache the tasks you run.

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.

myvueapp❯

nx run-many -t test lint e2e

1
2    ✔  nx run myvueapp:lint  [existing outputs match the cache, left as is]
3    ✔  nx run e2e:lint  [existing outputs match the cache, left as is]
4    ✔  nx run myvueapp:test  [existing outputs match the cache, left as is]
5    ✔  nx run e2e:e2e  [existing outputs match the cache, left as is]
6
7 ———————————————————————————————————————————————————————
8
9  NX   Successfully ran targets test, lint, e2e for 2 projects (143ms)
10
11   Nx read the output from the cache instead of running the command for 4 out of 4 tasks.
12

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.

Nx Plugins? Why?

One thing you might be curious about is the inferred tasks. You may wonder why we are detecting tasks from your tooling configuration instead of directly defining them in package.json scripts or in the project.json file.

Nx understands and supports both approaches, allowing you to define tasks in your package.json and project.json files or have Nx plugins automatically detect them. The inferred tasks give you the benefit of automatically setting the Nx cache settings for you based on your tooling configuration. In this tutorial, we take advantage of those inferred tasks to demonstrate the full value 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 for more details.

Creating New Components

You can just create new Vue components as you normally would. However, Nx plugins usually also ship 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:

myvueapp❯

npx nx list @nx/vue

1
2 NX   Capabilities in @nx/vue:
3
4   GENERATORS
5
6   init : Initialize the `@nx/vue` plugin.
7   application : Create a Vue application.
8   library : Create a Vue library.
9   component : Create a Vue component.
10   setup-tailwind : Set up Tailwind configuration for a project.
11   storybook-configuration : Set up storybook for a Vue app or library.
12   stories : Create stories for all components declared in an app or library.
13

Nx 15 and lower use @nrwl/ instead of @nx/

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.

Run the following command to generate a new "hello-world" component. Note how we append --dry-run to first check the output.

myvueapp❯

npx nx g @nx/vue:component hello-world --no-export --unit-test-runner=vitest --directory=src/components --dry-run

1 NX  Generating @nx/vue:component
2
3CREATE src/components/hello-world.spec.ts
4CREATE src/components/hello-world.vue
5
6NOTE: The "dryRun" flag means no changes were made.
7

Nx 15 and lower use @nrwl/ instead of @nx/

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.

src/components/hello-world.vue
<script setup lang="ts">
// defineProps<{}>();
</script>

<template>
  <p>Welcome to HelloWorld!</p>
</template>

<style scoped></style>

Building the App for Deployment

If you're ready and want to ship your application, you can build it using

myvueapp❯

npx nx build

1> nx run myvueapp:build:production
2
3vite v4.3.9 building for production...
4✓ 15 modules transformed.
5dist/myvueapp/index.html                  0.43 kB │ gzip:  0.29 kB
6dist/myvueapp/assets/index-a0201bbf.css   7.90 kB │ gzip:  1.78 kB
7dist/myvueapp/assets/index-46a11b5f.js   62.39 kB │ gzip: 24.35 kB
8✓ built in 502ms
9
10 —————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————
11
12  NX   Successfully ran target build for project myvueapp (957ms)
13

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 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
Nx 15 and lower use @nrwl/ instead of @nx/

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 a project details view where you can see the available tasks (e.g. running tests for just orders: nx test orders)
has its own project.json file where you can customize targets
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.

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. As an example, let's create and expose a ProductList component from our modules/products library. Either create it by hand or run

❯

nx g @nx/vue:component product-list --directory=modules/products/src/product-list

Nx 15 and lower use @nrwl/ instead of @nx/

We don't need to implement anything fancy as we just want to learn how to import it into our main Vue application.

modules/products/src/product-list/product-list.vue
<script setup lang="ts">
// defineProps<{}>()
</script>

<template>
  <p>Welcome to ProductList!</p>
</template>

<style scoped></style>

Make sure the ProductList is exported via the index.ts file of our products library. This is our public API with the rest of the workspace. Only export what's really necessary to be usable outside the library itself.

modules/products/src/index.ts
export { default as ProductList } from './product-list/product-list.vue';

We're ready to import it into our main application now. First, let's set up the Vue Router.

❯

npm add vue-router

Configure it in the main.ts file.

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.ProductList),
  },
];

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.

src/app/App.vue
<script setup lang="ts">
import { RouterLink, RouterView } from 'vue-router';
</script>

<template>
  <nav>
    <ul>
      <li>
        <RouterLink to="/">Home</RouterLink>
      </li>
      <li>
        <RouterLink to="/products">Products</RouterLink>
      </li>
    </ul>
  </nav>

  <RouterView />
</template>

If you now navigate to http://localhost:4200/#/products you should see the ProductList component being rendered.

Browser screenshot of navigating to the products route

Let's do the same process for our orders library. Create an OrderList component and import it into the main.ts routes:

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.ProductList),
  },
  {
    path: '/orders',
    component: () => import('@myvueapp/orders').then((m) => m.OrderList),
  },
];

const router = VueRouter.createRouter({
  history: VueRouter.createWebHashHistory(),
  routes,
});

const app = createApp(App);

app.use(router);
app.mount('#root');

And update the navigation links:

src/app/App.vue
<script setup lang="ts">
import { RouterLink, RouterView } from 'vue-router';
</script>

<template>
  <nav>
    <ul>
      <li>
        <RouterLink to="/">Home</RouterLink>
      </li>
      <li>
        <RouterLink to="/products">Products</RouterLink>
      </li>
      <li>
        <RouterLink to="/orders">Orders</RouterLink>
      </li>
    </ul>
  </nav>

  <RouterView />
</template>

Similarly, navigating to 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. 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 and more. Interestingly you can also visualize it.

Just run:

❯

nx graph

You should be able to see something similar to the following in your browser (hint: click the "Show all projects" button).

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)
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.

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.

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.

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:

.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"]
              }
            ]
          }
        ]
      }
    },
    ...
  ]
}
Nx 15 and lower use @nrwl/ instead of @nx/

To test it, go to your modules/products/src/lib/products.vue file and import the Orders component from the orders project:

modules/products/src/lib/products.vue
<script setup lang="ts">
defineProps<{}>();

// 👇 this import is not allowed
import { Orders } from 'orders';
</script>

<template>
  <p>Welcome to Products!</p>
</template>

<style scoped></style>

If you lint your workspace you'll get an error now:

~/workspace❯

nx run-many -t lint

1 NX   Running target lint for 5 projects
2    ✖  nx run products:lint
3       Linting "products"...
4
5       /Users/isaac/Documents/code/nx-recipes/vue-standalone/modules/products/src/lib/products.vue
6         5:1   error    A project tagged with "scope:products" can only depend on libs tagged with "scope:products", "scope:shared"  @nx/enforce-module-boundaries
7         5:10  warning  'Orders' is defined but never used                                                                           @typescript-eslint/no-unused-vars
8
9       ✖ 2 problems (1 error, 1 warning)
10
11       Lint warnings found in the listed files.
12
13       Lint errors found in the listed files.
14
15
16    ✔  nx run orders:lint (913ms)
17    ✔  nx run e2e:lint  [existing outputs match the cache, left as is]
18    ✔  nx run myvueapp:lint (870ms)
19    ✔  nx run shared-ui:lint (688ms)
20
21 ——————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————
22
23  NX   Ran target lint for 5 projects (2s)
24
25    ✔    4/5 succeeded [1 read from cache]
26
27    ✖    1/5 targets failed, including the following:
28         - nx run products:lint
29
30

Nx 15 and lower use @nrwl/ instead of @nx/

Learn more about how to 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 or manually move the configuration files.

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:

Also, make sure you

Join the Official Nx Discord Server to ask questions and find out the latest news about Nx.
Follow Nx on Twitter to stay up to date with Nx news
Read our Nx blog
Subscribe to our Youtube channel for demos and Nx insights