Jack Hsu 8fa7065cf1
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.0 KiB

The Nx Plugin for Web Components contains generators for managing Web Component applications and libraries within an Nx workspace. It provides:

  • Integration with libraries such as Jest, Cypress, and Storybook.
  • Scaffolding for creating buildable libraries that can be published to npm.
  • Utilities for automatic workspace refactoring.

Setting Up @nx/web

Generating a new Workspace

To create a new workspace with React, run npx create-nx-workspace@latest --preset=web-components.

Installation

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

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

nx add @nx/web

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

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

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

npm add -D @nx/web

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

Using the @nx/web Plugin

Creating Applications

You can add a new application with the following:

nx g @nx/web:app apps/my-new-app

The application uses no framework and generates with web components. You can add any framework you want on top of the default setup.

To start the application in development mode, run nx serve my-new-app.

{% callout type="note" title="React" %} If you are looking to add a React application, check out the React plugin. {% /callout %}

Creating Libraries

To create a generic TypeScript library (i.e. non-framework specific), use the @nx/js plugin.

nx g @nx/js:lib libs/my-new-lib

# If you want the library to be publishable to npm
nx g @nx/js:lib libs/my-new-lib \
--publishable \
--importPath=@myorg/my-new-lib

Using Web

Testing Projects

You can run unit tests with:

nx test my-new-app
nx test my-new-lib

Replace my-new-app with the name or your project. This command works for both applications and libraries.

You can also run E2E tests for applications:

nx e2e my-new-app-e2e

Replace my-new-app-e2e with the name or your project with -e2e appended.

Building Projects

React applications can be build with:

nx build my-new-app

And if you generated a library with --buildable, then you can build a library as well:

nx build my-new-lib

The output is in the dist folder. You can customize the output folder by setting outputPath in the project's project.json file.

The application in dist is deployable, and you can try it out locally with:

npx http-server dist/apps/my-new-app

The library in dist is publishable to npm or a private registry.

More Documentation