feat(core): allow executors to specify if they are continuous

[FrozenPandaz]

Current Behavior

The only way to set if a task is continuous is either directly in project.json or via Project Graph Plugins.

Expected Behavior

Executors know if they are definitely continuous or not. Plenty of existing continuous tasks are using executors. Executors are now able to define if they are continuous in their schema.json files. Thus, existing tasks configured with certain executors will automatically become continuous.

Related Issue(s)

Fixes #

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
nx-dev	✅ Ready (Inspect)	Visit Preview	Apr 24, 2025 6:30pm

[nx-cloud]

View your CI Pipeline Execution ↗ for commit 49b3888.

Command	Status	Duration	Result
nx affected --targets=lint,test,build,e2e,e2e-ci	✅ Succeeded	10m 49s	View ↗
nx run-many -t check-imports check-commit check...	✅ Succeeded	21s	View ↗
nx-cloud record -- nx-cloud conformance:check	✅ Succeeded	2s	View ↗
nx-cloud record -- nx format:check	✅ Succeeded	3s	View ↗
nx-cloud record -- nx sync:check	✅ Succeeded	1s	View ↗
nx documentation	✅ Succeeded	<1s	View ↗

---

☁️ Nx Cloud last updated this comment at 2025-04-24 20:28:31 UTC

[Copilot]

Pull Request Overview

This PR introduces support for executors to specify their continuous behavior through the executor schema. Key changes include updating the executor schema normalization to include a "continuous" boolean flag, modifying tests to expect the "continuous" key, and refactoring executor parsing across the codebase.

Reviewed Changes

Copilot reviewed 60 out of 68 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
packages/nx/src/project-graph/utils/project-configuration-utils.spec.ts	Updated test assertions to include “continuous”: false in normalized targets.
packages/nx/src/project-graph/utils/normalize-project-nodes.ts	Removed unused TargetConfiguration import.
packages/nx/src/project-graph/plugins/public-api.ts	Updated documentation for projects configuration.
packages/nx/src/plugins/package-json/create-nodes.ts	Refactored readTargetsFromPackageJson call to use additional parameters.
packages/nx/src/devkit-internals.ts	Updated export to include parseExecutor from executor-utils.
packages/nx/src/config/to-project-name.spec.ts	Updated inline snapshot to include the continuous property.
packages/nx/src/config/misc-interfaces.ts	Added an optional “continuous” flag to the executor schema interface.
packages/nx/src/command-line/run/*	Replaced direct executor string split with parseExecutor for robust parsing.
packages/devkit/src/executors/read-target-options.ts	Aligned executor parsing with new parseExecutor usage.
packages/cypress/src/utils/start-dev-server.ts	Updated executor parsing imports to include parseExecutor.
e2e/angular/src/config.test.ts	Changed e2e builder from Cypress to Playwright with updated options.

Files not reviewed (8)

• packages/angular/src/builders/dev-server/schema.json: Language not supported
• packages/angular/src/executors/module-federation-dev-server/schema.json: Language not supported
• packages/angular/src/executors/module-federation-ssr-dev-server/schema.json: Language not supported
• packages/expo/src/executors/run/schema.json: Language not supported
• packages/expo/src/executors/serve/schema.json: Language not supported
• packages/expo/src/executors/start/schema.json: Language not supported
• packages/js/src/executors/verdaccio/schema.json: Language not supported
• packages/next/src/executors/server/schema.json: Language not supported

Comments suppressed due to low confidence (2)

packages/nx/src/project-graph/utils/project-configuration-utils.spec.ts:1666

• [nitpick] Consider adding an additional test case to verify behavior when the executor schema specifies continuous as true.

"continuous": false,

e2e/angular/src/config.test.ts:138

• [nitpick] Ensure that the updated Playwright configuration fully replaces the previous Cypress logic and that any related test references have been updated accordingly.

"builder": "@nx/playwright:playwright",

[Copilot]

Consider validating that the executorString contains a colon delimiter before splitting, to prevent potential runtime errors if the format is unexpected.

Suggested change

	): [module: string, name: string] {
	return executorString.split(':') as [string, string];
	): [module: string, name: string] {
	if (!executorString.includes(':')) {
	throw new Error(
	`Invalid executor string "${executorString}". Expected format: "module:name".`
	);
	}

[github-actions]

This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request.