66eaf2fc74
This PR removes the `/nx-api` pages from `nx-dev`. They are already redirected from `/nx-api` to either `/technologies` or `/reference/core-api` URLs. e.g. `/nx-api/nx` goes to `/reference/core-api/nx` and `/nx-api/react` goes to `/technologies/react/api` **Changes**: - Remove old `nx-api.json` from being generated in `scripts/documentation/generators/generate-manifests.ts` -- this was used to generate the sitemap - Remove `pages/nx-api` from Next.js app since we don't need them - Remove workaround from link checker `scripts/documentation/internal-link-checker.ts` -- the angular rspack/rsbuild and other workarounds are gone now that they are proper docs in `map.json` - Update Powerpack/Remote Cache reference docs to exclude API documents (since they are duplicated in the Intro page) -- `nx-dev/models-document/src/lib/mappings.ts` - All content in `docs` have been updated with new URL structure **Note:** Redirects are already handled, and Claude Code was used to verify the updated `docs/` URLs (see report below). The twelve 404s links were updated by hand. ## Verification Report https://gist.github.com/jaysoo/c7863fe7e091cb77929d1976165c357a
3.0 KiB
| title | description |
|---|---|
| Node.js Plugin for Nx | Learn how to use the @nx/node plugin to create and manage Node.js applications and libraries in your Nx workspace, including setup, building, and testing. |
The Node Plugin contains generators and executors to manage Node applications within an Nx workspace. It provides:
Setting Up @nx/node
Installation
{% callout type="note" title="Keep Nx Package Versions In Sync" %}
Make sure to install the @nx/node 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/node by running the following command:
nx add @nx/node
This will install the correct version of @nx/node.
Using the @nx/node Plugin
Creating Applications
You can add a new application with the following:
nx g @nx/node:application apps/my-new-app
You can run your application with nx serve my-new-app, which starts it in watch mode.
Creating Libraries
Node libraries are a good way to separate features within your organization. To create a Node library run the following command:
nx g @nx/node:lib libs/my-new-lib
# If you want the library to be buildable or publishable to npm
nx g @nx/node:lib libs/my-new-lib --buildable
nx g @nx/node:lib libs/my-new-lib \
--publishable \
--importPath=@myorg/my-new-lib
Using Node
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.
Building Projects
Node 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.
Application Proxies
Generating Node applications has an option to configure other projects in the workspace to proxy API requests. This can be done by passing the --frontendProject with the project name you wish to enable proxy support for.
nx g @nx/node:application apps/my-new-app \
--frontendProject my-react-app
Debugging
Debugging is set to use a random port that is available on the system. The port can be changed by setting the port option in the serve target in the project.json. Or by running the serve command with --port <number>.
For additional information on how to debug Node applications, see the Node.js debugging getting started guide.