nx/overview.md at 8fa7065cf14df6a90896442f90659b00baa1b5b9

docs(misc): update generator examples to use new directory/path positional args (#28144 )

This PR updates examples in `.md` files (both docs and blog posts) to
use positional args. Nx 20 changes the position arg to be either
`directory` for apps/libs or `path` for artifacts (e.g. components).

So before you'd do this:

```
nx g app myapp --directory=apps/myapp
nx g lib mylib --directory=libs/mylib
nx g lib mylib --directory=libs/nested/mylib
nx g lib @acme/foo --directory=libs/@acme/foo --importPath=@acme/foo
nx g component foo --directory=libs/ui/src/foo --pascalCaseFiles
```

Will now be simplified to

```
nx g app apps/myapp
nx g lib libs/mylib
nx g lib libs/nested/mylib
nx g lib libs/@acme/foo # name and import path are both "@acme/foo"
nx g component libs/ui/src/foo/Foo
```

For cases where `name` and `importPath` need to be changed, you can
always manually specify them.

```
nx g lib libs/nested/foo # name is foo
nx g lib libs/nested/foo --name=nested-foo # specify name with prefix
nx g lib libs/@acme/foo --name # use "foo" as name and don't match importPath
nx g lib libs/@internal/foo --importPath=@acme/foo # different importPath from name

<!-- If this is a particularly complex change or feature addition, you can request a dedicated Nx release for this pull request branch. Mention someone from the Nx team or the `@nrwl/nx-pipelines-reviewers` and they will confirm if the PR warrants its own release for testing purposes, and generate it for you if appropriate. -->

## Current Behavior
<!-- This is the behavior we have today -->

## Expected Behavior
<!-- This is the behavior we should expect with the changes in this PR -->

## Related Issue(s)
<!-- Please link the issue being fixed so it gets closed when this is merged. -->

Fixes #

2024-09-30 13:20:10 -04:00

4.5 KiB

Raw Blame History

title	description
Overview of the Nx Vite Plugin	The Nx Plugin for Vite contains executors and generators that support building applications using Vite. This page also explains how to configure Vite on your Nx workspace.

The Nx plugin for Vite and Vitest.

Vite.js is a build tool that aims to provide a faster and leaner development experience for modern web projects.

Why should you use this plugin?

Instant dev server start
Lightning fast Hot-Module Reloading
Fast builds using Vite.
Vite-powered tests with smart and instant watch mode

Read more about Vite and Vitest in the Vite documentation.

Setting up a new Nx workspace with @nx/vite

Here's an example on how to create a new React app with Vite

npx create-nx-workspace@latest --preset=react-standalone --bundler=vite

Installation

{% callout type="note" title="Keep Nx Package Versions In Sync" %} Make sure to install the @nx/vite version that matches the version of nx in your repository. If the version numbers get out of sync, you can encounter some difficult to debug errors. You can fix Nx version mismatches with this recipe. {% /callout %}

In any Nx workspace, you can install @nx/vite by running the following command:

{% tabs %} {% tab label="Nx 18+" %}

nx add @nx/vite

You can also pass the --setupPathsPlugin flag to add nxViteTsPaths plugin, so your projects can use workspace libraries.

nx add @nx/vite --setupPathsPlugin

This will install the correct version of @nx/vite.

How @nx/vite Infers Tasks

The @nx/vite plugin will create a task for any project that has a Vite configuration file present. Any of the following files will be recognized as a Vite configuration file:

vite.config.js
vite.config.ts
vite.config.mjs
vite.config.mts
vite.config.cjs
vite.config.cts
vitest.config.js
vitest.config.ts
vitest.config.mjs
vitest.config.mts
vitest.config.cjs
vitest.config.cts

View Inferred Tasks

To view inferred tasks for a project, open the project details view in Nx Console or run nx show project my-project --web in the command line.

@nx/vite Configuration

The @nx/vite/plugin is configured in the plugins array in nx.json.

{
  "plugins": [
    {
      "plugin": "@nx/vite/plugin",
      "options": {
        "buildTargetName": "build",
        "previewTargetName": "preview",
        "testTargetName": "test",
        "serveTargetName": "serve",
        "serveStaticTargetName": "serve-static"
      }
    }
  ]
}

The buildTargetName, previewTargetName, testTargetName, serveTargetName and serveStaticTargetName options control the names of the inferred Vite tasks. The default names are build, preview, test, serve and serve-static.

{% /tab %} {% tab label="Nx < 18" %}

Install the @nx/vite package with your package manager.

npm add -D @nx/vite

{% /tab %} {% /tabs %}

Using @nx/vite

Generate a new project using Vite

You can generate a React application or library or a Web application that uses Vite.js. The @nx/react:app, @nx/react:lib and @nx/web:app generators accept the bundler option, where you can pass vite. This will generate a new application configured to use Vite.js, and it will also install all the necessary dependencies, including the @nx/vite plugin.

To generate a React application using Vite.js, run the following:

nx g @nx/react:app apps/my-app --bundler=vite

To generate a React library using Vite.js, run the following:

nx g @nx/react:lib libs/my-lib --bundler=vite

To generate a Web application using Vite.js, run the following:

nx g @nx/web:app apps/my-app --bundler=vite

Modify an existing React or Web project to use Vite.js

You can use the @nx/vite:configuration generator to change your React or Web project to use Vite.js. This generator will modify your project's configuration to use Vite.js, and it will also install all the necessary dependencies, including the @nx/vite plugin..

You can read more about this generator on the @nx/vite:configuration generator page.

4.5 KiB Raw Blame History