nx/plugin-overview.md at 24bae0ddb22a6fa3ab94b9971543886459f99786

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

3.9 KiB

Raw Blame History

title	description
Overview of the Nx Webpack Plugin	The Nx Plugin for Webpack contains executors and generators that support building applications using Webpack.

The Nx plugin for webpack.

Webpack is a static module bundler for modern JavaScript applications. The @nx/webpack plugin provides executors that allow you to build and serve your projects using webpack, plus an executor for SSR.

Nx now allows you to customize your webpack configuration for your projects. And we also offer a number of webpack plugins for supporting Nx and other frameworks.

Setting up a new Nx workspace with Webpack

You can create a new workspace that uses Webpack with one of the following commands:

Generate a new standalone React app set up with Webpack

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

Generate a new React monorepo set up with Webpack

npx create-nx-workspace@latest --preset=react-monorepo --bundler=webpack

Installation

{% callout type="note" title="Keep Nx Package Versions In Sync" %} Make sure to install the @nx/webpack 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/webpack by running the following command:

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

nx add @nx/webpack

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

How @nx/webpack Infers Tasks

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

webpack.config.js
webpack.config.ts
webpack.config.mjs
webpack.config.cjs

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/webpack Configuration

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

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

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

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

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

npm add -D @nx/webpack

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

Generate a new project using Webpack

You can generate a React application or a Web application that uses Webpack in an existing Nx workspace. The @nx/react:app, @nx/node:app and @nx/web:app generators accept the bundler option, where you can pass webpack. This will generate a new application configured to use Webpack, and it will also install all the necessary dependencies, including the @nx/webpack plugin.

To generate a React application using Webpack, run the following:

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

To generate a Node application using Webpack, run the following:

nx g @nx/node:app apps/my-app --bundler=webpack

To generate a Web application using Webpack, run the following:

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

3.9 KiB Raw Blame History