b51676a89a
Updates the docs structure, navigation etc to be easier + better suited for showing Nx technology support beyond just TS. **Notes:** - API (`/nx-api`) tab is removed from the navigation (i.e. menu bar), but pages still remain for now until we update references in `*.md` files. - Redirects are set up `/nx-api` to go to their respect new location e.g. `/technologies` or `/reference/core-api` - Old URLs still exist in the sitemap for now, but majority of them will be redirected -- a follow-up PR can remove them. **Preview:** https://nx-dev-git-nx-dev-polyglot-docs-restructure-nrwl.vercel.app/docs --------- Co-authored-by: Jack Hsu <jack.hsu@gmail.com>
92 lines
6.0 KiB
Markdown
92 lines
6.0 KiB
Markdown
---
|
|
title: Inferred Tasks (Project Crystal)
|
|
description: Learn how Nx plugins automatically infer tasks from tool configurations, enabling caching, task dependencies, and optimized execution without manual setup.
|
|
---
|
|
|
|
# Inferred Tasks (Project Crystal)
|
|
|
|
In Nx version 18, Nx plugins can automatically infer tasks for your projects based on the configuration of different tools. Many tools have configuration files which determine what a tool does. Nx is able to cache the results of running the tool. Nx plugins use the same configuration files to infer how Nx should [run the task](/features/run-tasks). This includes [fine-tuned cache settings](/features/cache-task-results) and automatic [task dependencies](/concepts/task-pipeline-configuration).
|
|
|
|
For example, the `@nx/webpack` plugin infers tasks to run webpack through Nx based on your repository's webpack configuration. This configuration already defines the destination of your build files, so Nx reads that value and caches the correct output files.
|
|
|
|
{% youtube
|
|
src="https://youtu.be/wADNsVItnsM"
|
|
title="Project Crystal"
|
|
/%}
|
|
|
|
## How Does a Plugin Infer Tasks?
|
|
|
|
Every plugin has its own custom logic, but in order to infer tasks, they all go through the following steps.
|
|
|
|
### 1. Detect Tooling Configuration in Workspace
|
|
|
|
The plugin will search the workspace for configuration files of the tool. For each configuration file found, the plugin will infer tasks. i.e. The `@nx/webpack` plugin searches for `webpack.config.js` files to infer tasks that run webpack.
|
|
|
|
### 2. Create an Inferred Task
|
|
|
|
The plugin then configures tasks with a name that you specified in the plugin's configuration in `nx.json`. The settings for the task are determined by the tool configuration.
|
|
|
|
The `@nx/webpack` plugin creates tasks named `build`, `serve` and `preview` by default and it automatically sets the task caching settings based on the values in the webpack configuration files.
|
|
|
|
## What Is Inferred
|
|
|
|
Nx plugins infer the following properties by analyzing the tool configuration.
|
|
|
|
- Command - How is the tool invoked
|
|
- [Cacheability](/concepts/how-caching-works) - Whether the task will be cached by Nx. When the Inputs have not changed the Outputs will be restored from the cache.
|
|
- [Inputs](/recipes/running-tasks/configure-inputs) - Inputs are used by the task to produce Outputs. Inputs are used to determine when the Outputs of a task can be restored from the cache.
|
|
- [Outputs](/recipes/running-tasks/configure-outputs) - Outputs are the results of a task. Outputs are restored from the cache when the Inputs are the same as a previous run.
|
|
- [Task Dependencies](/concepts/task-pipeline-configuration) - The list of other tasks which must be completed before running this task.
|
|
|
|
## Nx Uses Plugins to Build the Graph
|
|
|
|
A typical workspace will have many plugins inferring tasks. Nx processes all the plugins registered in `nx.json` to create project configuration for individual projects and a project and task graph that shows the connections between them all.
|
|
|
|
### Plugin Order Matters
|
|
|
|
Plugins are processed in the order that they appear in the `plugins` array in `nx.json`. So, if multiple plugins create a task with the same name, the plugin listed last will win. If, for some reason, you have a project with both a `vite.config.js` file and a `webpack.config.js` file, both the `@nx/vite` plugin and the `@nx/webpack` plugin will try to create a `build` task. The `build` task that is executed will be the task that belongs to the plugin listed lower in the `plugins` array.
|
|
|
|
## View Inferred Tasks
|
|
|
|
To view the task settings for projects in your workspace, [show the project details](/features/explore-graph) either from the command line or using Nx Console.
|
|
|
|
```shell
|
|
nx show project my-project --web
|
|
```
|
|
|
|
{% project-details jsonFile="shared/concepts/myreactapp.json"%}
|
|
{% /project-details %}
|
|
|
|
## Overriding Inferred Task Configuration
|
|
|
|
You can override the task configuration inferred by plugins in several ways.
|
|
If you want to overwrite the task configuration for multiple projects, [use the `targetDefaults` object](/reference/nx-json#target-defaults) in the `nx.json` file.
|
|
If you only want to override the task configuration for a specific project, [update that project's configuration](/reference/project-configuration) in `package.json` or `project.json`.
|
|
This configuration is more specific so it will override both the inferred configuration and the `targetDefaults`.
|
|
|
|
The order of precedence for task configuration is:
|
|
|
|
1. Inferred Task Configurations from plugins in `nx.json`.
|
|
2. `targetDefaults` in `nx.json`.
|
|
3. Project Configuration in `package.json` or `project.json`.
|
|
|
|
More details about how to override task configuration is available in these recipes:
|
|
|
|
- [Configure Inputs for Task Caching](/recipes/running-tasks/configure-inputs)
|
|
- [Configure Outputs for Task Caching](/recipes/running-tasks/configure-outputs)
|
|
- [Defining a Task Pipeline](/recipes/running-tasks/defining-task-pipeline)
|
|
- [Pass Arguments to Commands](/recipes/running-tasks/pass-args-to-commands)
|
|
|
|
## Existing Nx Workspaces
|
|
|
|
If you have an existing Nx Workspace and upgrade to the latest Nx version, a migration will automatically set `useInferencePlugins` to `false` in `nx.json`. This property allows you to continue to use Nx without inferred tasks.
|
|
|
|
When `useInferencePlugins` is `false`:
|
|
|
|
1. A newly generated project will have all targets defined with executors - not with inferred tasks.
|
|
2. Running `nx add @nx/some-plugin` will not create a plugin entry for `@nx/some-plugin` in the `nx.json` file. (So that plugin will not create inferred tasks.)
|
|
|
|
If you want to **migrate** your projects to use inferred tasks, follow the recipe for [migrating to inferred tasks](/recipes/running-tasks/convert-to-inferred).
|
|
|
|
Even once a repository has fully embraced inferred tasks, `project.json` and executors will still be useful. The `project.json` file is needed to modify inferred task options and to define tasks that can not be inferred. Some executors perform tasks that can not be accomplished by running a tool directly from the command line (i.e. [TypeScript batch mode](/technologies/typescript/recipes/enable-tsc-batch-mode)).
|