## Current Behavior - Documentation pages under "technologies" and "core-api" sections with "introduction"/"overview" IDs lack H1 titles after front matter - Some remote caching package links point to parent sections instead of overview pages ## Expected Behavior - All affected documentation pages should have H1 titles for consistency - Links should point directly to overview pages ## Related Issue(s) Fixes # ## Changes Made ### 1. Updated Remote Caching Links (commit fae9055f8c) Updated links in 3 files to point directly to overview pages: - `docs/blog/2025-01-06-nx-update-20-3.md` - `docs/shared/deprecated/custom-tasks-runner.md` - `docs/shared/recipes/running-tasks/self-hosted-caching.md` Changed links from: - `/reference/core-api/azure-cache` → `/reference/core-api/azure-cache/overview` - `/reference/core-api/gcs-cache` → `/reference/core-api/gcs-cache/overview` - `/reference/core-api/s3-cache` → `/reference/core-api/s3-cache/overview` - `/reference/core-api/shared-fs-cache` → `/reference/core-api/shared-fs-cache/overview` ### 2. Added H1 Titles to Documentation Pages Added H1 titles to 29 documentation files that were missing them: #### Core API Overview Pages (6 files) - `docs/shared/packages/azure-cache/azure-cache-plugin.md` → `# @nx/azure-cache` - `docs/shared/packages/conformance/conformance-plugin.md` → `# @nx/conformance` - `docs/shared/packages/gcs-cache/gcs-cache-plugin.md` → `# @nx/gcs-cache` - `docs/shared/packages/owners/owners-plugin.md` → `# @nx/owners` - `docs/shared/packages/s3-cache/s3-cache-plugin.md` → `# @nx/s3-cache` - `docs/shared/packages/shared-fs-cache/shared-fs-cache-plugin.md` → `# @nx/shared-fs-cache` #### Technology Introduction Pages (23 files) - `docs/shared/packages/angular/angular-plugin.md` → `# @nx/angular` - `docs/shared/packages/esbuild/esbuild-plugin.md` → `# @nx/esbuild` - `docs/shared/packages/rspack/rspack-plugin.md` → `# @nx/rspack` - `docs/shared/packages/vite/vite-plugin.md` → `# @nx/vite` - `docs/shared/packages/webpack/plugin-overview.md` → `# @nx/webpack` - `docs/shared/packages/eslint/eslint.md` → `# @nx/eslint` - `docs/shared/packages/gradle/gradle-plugin.md` → `# @nx/gradle` - `docs/shared/packages/express/express-plugin.md` → `# @nx/express` - `docs/shared/packages/node/node-plugin.md` → `# @nx/node` - `docs/shared/packages/nest/nest-plugin.md` → `# @nx/nest` - `docs/shared/packages/expo/expo-plugin.md` → `# @nx/expo` - `docs/shared/packages/react/react-plugin.md` → `# @nx/react` - `docs/shared/packages/next/plugin-overview.md` → `# @nx/next` - `docs/shared/packages/react-native/react-native-plugin.md` → `# @nx/react-native` - `docs/shared/packages/remix/remix-plugin.md` → `# @nx/remix` - `docs/shared/packages/cypress/cypress-plugin.md` → `# @nx/cypress` - `docs/shared/packages/detox/detox-plugin.md` → `# @nx/detox` - `docs/shared/packages/jest/jest-plugin.md` → `# @nx/jest` - `docs/shared/packages/playwright/playwright-plugin.md` → `# @nx/playwright` - `docs/shared/packages/storybook/plugin-overview.md` → `# @nx/storybook` - `docs/shared/packages/js/js-plugin.md` → `# @nx/js` - `docs/shared/packages/vue/vue-plugin.md` → `# @nx/vue` - `docs/shared/packages/nuxt/nuxt-plugin.md` → `# @nx/nuxt` Note: The Angular Rspack introduction page (`docs/shared/guides/angular-rspack/introduction.md`) already had an appropriate H1 title "# Introduction" and was left unchanged. All changes improve documentation consistency and navigation by ensuring proper titles and direct links to overview pages.
214 lines
5.4 KiB
Markdown
214 lines
5.4 KiB
Markdown
---
|
|
title: Overview of the Nx JS Plugin
|
|
description: The Nx JS plugin contains executors and generators that are useful for JavaScript/TypeScript projects in an Nx workspace.
|
|
---
|
|
|
|
# @nx/js
|
|
|
|
The JS plugin contains executors and generators that are useful for JavaScript/TypeScript projects in an Nx workspace.
|
|
|
|
## Setting Up @nx/js
|
|
|
|
### Installation
|
|
|
|
{% callout type="note" title="Keep Nx Package Versions In Sync" %}
|
|
Make sure to install the `@nx/js` 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](/recipes/tips-n-tricks/keep-nx-versions-in-sync).
|
|
{% /callout %}
|
|
|
|
In any Nx workspace, you can install `@nx/js` by running the following command:
|
|
|
|
```shell {% skipRescope=true %}
|
|
nx add @nx/js
|
|
```
|
|
|
|
This will install the correct version of `@nx/js`.
|
|
|
|
### `ts` Preset
|
|
|
|
When initializing a new Nx workspace, specifying `--preset=ts` will generate a workspace with `@nx/js` pre-installed.
|
|
|
|
{% tabs %}
|
|
{%tab label="npm"%}
|
|
|
|
```shell
|
|
npx create-nx-workspace my-org --preset=ts
|
|
```
|
|
|
|
{% /tab %}
|
|
{%tab label="yarn"%}
|
|
|
|
```shell
|
|
yarn create nx-workspace my-org --preset=ts
|
|
```
|
|
|
|
{% /tab %}
|
|
{% /tabs %}
|
|
|
|
{% callout type="note" title="Modernized monorepo setup" %}
|
|
Nx 20 updates the TS monorepo setup when using `--preset=ts`. The workspace is set up with [TypeScript Project References](https://www.typescriptlang.org/docs/handbook/project-references.html) along with the Workspaces feature from [npm](https://docs.npmjs.com/cli/using-npm/workspaces), [yarn](https://yarnpkg.com/features/workspaces), [pnpm](https://pnpm.io/workspaces), and [bun](https://bun.sh/docs/install/workspaces).
|
|
|
|
To create with the older setup for TS monorepo with `compilerOptions.paths`, use `create-nx-workspace --preset=apps`.
|
|
{% /callout %}
|
|
|
|
### How @nx/js Infers Tasks
|
|
|
|
The `@nx/js/typescript` plugin will add a `typecheck` task to projects that have a `tsconfig.json`.
|
|
|
|
This plugin adds a `build` task for projects that:
|
|
|
|
1. Have a runtime tsconfig file (defaults to `tsconfig.lib.json`).
|
|
2. Have a `package.json` file containing entry points that are not source files.
|
|
|
|
For example, this project is buildable and will have a `build` task.
|
|
|
|
```json {% fileName="packages/pkg1/package.json" %}
|
|
{
|
|
"name": "@acme/pkg1",
|
|
"exports": {
|
|
"./package.json": "./package.json",
|
|
".": {
|
|
"types": "./dist/index.d.ts",
|
|
"default": "./dist/index.js"
|
|
}
|
|
}
|
|
}
|
|
```
|
|
|
|
Whereas this project points to source files and will not have a `build` task.
|
|
|
|
```json {% fileName="packages/pkg1/package.json" %}
|
|
{
|
|
"name": "@acme/pkg1",
|
|
"exports": {
|
|
"./package.json": "./package.json",
|
|
".": "./src/index.ts"
|
|
}
|
|
}
|
|
```
|
|
|
|
### View Inferred Tasks
|
|
|
|
To view inferred tasks for a project, open the [project details view](/concepts/inferred-tasks) in Nx Console or run `nx show project my-project` in the command line.
|
|
|
|
### @nx/js Configuration
|
|
|
|
The `@nx/js/typescript` plugin is configured in the `plugins` array in `nx.json`.
|
|
|
|
```json {% fileName="nx.json" %}
|
|
{
|
|
"plugins": [
|
|
{
|
|
"plugin": "@nx/js/typescript",
|
|
"options": {
|
|
"typecheck": {
|
|
"targetName": "typecheck"
|
|
},
|
|
"build": {
|
|
"targetName": "build",
|
|
"configName": "tsconfig.lib.json"
|
|
}
|
|
}
|
|
}
|
|
]
|
|
}
|
|
```
|
|
|
|
You can also set `typecheck` and `build` options to `false` to not infer the corresponding tasks.
|
|
|
|
```json {% fileName="nx.json" %}
|
|
{
|
|
"plugins": [
|
|
{
|
|
"plugin": "@nx/js/typescript",
|
|
"options": {
|
|
"build": false
|
|
}
|
|
}
|
|
]
|
|
}
|
|
```
|
|
|
|
### Disable Typechecking
|
|
|
|
To disable `typecheck` task for a specific project, set the `nx.addTypecheckTarget` property to `false` in `tsconfig.json`.
|
|
|
|
```json {% fileName="packages/pkg1/tsconfig.json" highlightLines=["10-12"] %}
|
|
{
|
|
"extends": "../../tsconfig.base.json",
|
|
"files": [],
|
|
"include": [],
|
|
"references": [
|
|
{
|
|
"path": "./tsconfig.lib.json"
|
|
}
|
|
],
|
|
"nx": {
|
|
"addTypecheckTarget": false
|
|
}
|
|
}
|
|
```
|
|
|
|
## Create Libraries
|
|
|
|
You can add a new JS/TS library with the following command:
|
|
|
|
```shell
|
|
nx g @nx/js:lib libs/my-lib
|
|
```
|
|
|
|
## Build
|
|
|
|
You can `build` libraries that are generated with a bundler specified.
|
|
|
|
```shell
|
|
nx g @nx/js:lib libs/my-buildable-lib --bundler=rollup
|
|
```
|
|
|
|
Generating a library with `--bundler` specified will add a `build` target to the library's `project.json` file allows the library to be built.
|
|
|
|
```shell
|
|
nx build my-buildable-lib
|
|
```
|
|
|
|
## Test
|
|
|
|
You can test a library with the following command:
|
|
|
|
```shell
|
|
nx test my-lib
|
|
```
|
|
|
|
## Lint
|
|
|
|
You can lint a library with the following command:
|
|
|
|
```shell
|
|
nx lint my-lib
|
|
```
|
|
|
|
## Compiler
|
|
|
|
By default, `@nx/js` uses [TypeScript Compiler (TSC)](https://www.typescriptlang.org/docs/handbook/2/basic-types.html#tsc-the-typescript-compiler), via `@nx/js:tsc` executor, to compile your libraries. Optionally, you can switch `tsc` out for a different compiler with `--compiler` flag when executing the generators.
|
|
|
|
Currently, `@nx/js` supports the following compilers:
|
|
|
|
- [Speedy Web Compiler (SWC)](https://swc.rs)
|
|
|
|
### SWC
|
|
|
|
- Create a buildable library with `swc`
|
|
|
|
```shell
|
|
nx g @nx/js:lib libs/my-swc-lib --bundler=swc
|
|
```
|
|
|
|
- Convert a `tsc` library to use `swc`
|
|
|
|
```shell
|
|
nx g @nx/js:convert-to-swc my-buildable-lib
|
|
```
|
|
|
|
Now the `build` command will use `@nx/js:swc` executor to compile your libraries.
|
|
|
|
> The first time you generate a `swc` library or convert a `tsc` library over to `swc`, `@nx/js` will install the necessary dependencies to use `swc`.
|