Unable to find local plugin [] Map(0) {}

[sschneider-ihre-pvs]

Current Behavior

when running things like pnpm nx run frontend:tsc:build --verbose with the nx/js:typescript plugin nx reports

Unable to find local plugin [] Map(0) {}

multiple times. I cannot see what local plugin it tries to find.

#30022

Expected Behavior

Either list the plugin that is not found or don't show at all.

GitHub Repo

No response

Steps to Reproduce

{
	"$schema": "./node_modules/nx/schemas/nx-schema.json",
	"targetDefaults": {},
	"namedInputs": {
		"default": ["{projectRoot}/**/*", "sharedGlobals"],
		"production": [
			"default",
			"!{projectRoot}/.eslintrc.json",
			"!{projectRoot}/eslint.config.js",
			"!{projectRoot}/**/?(*.)+(spec|test).[jt]s?(x)?(.snap)",
			"!{projectRoot}/tsconfig.spec.json",
			"!{projectRoot}/cypress/**/*",
			"!{projectRoot}/**/*.cy.[jt]s?(x)",
			"!{projectRoot}/cypress.config.[jt]s",
			"!{projectRoot}/src/test-setup.[jt]s",
			"!{projectRoot}/test-setup.[jt]s",
			"!{projectRoot}/jest.config.[jt]s"
		],
		"sharedGlobals": []
	},
	"cli": {
		"packageManager": "pnpm"
	},
	"sync": { "applyChanges": true },
	"plugins": [
		{
			"plugin": "@nx/cypress/plugin",
			"options": {
				"targetName": "e2e",
				"ciTargetName": "e2e-ci",
				"componentTestingTargetName": "component-test",
				"openTargetName": "open-cypress"
			}
		},
		{
			"plugin": "@nx/storybook/plugin",
			"options": {
				"serveStorybookTargetName": "serve:storybook",
				"buildStorybookTargetName": "build-storybook",
				"testStorybookTargetName": "test-storybook",
				"staticStorybookTargetName": "static-storybook"
			}
		},
		{
			"plugin": "@nx/js/typescript",
			"options": {
				"typecheck": {
					"targetName": "tsc:typecheck"
				},
				"build": {
					"targetName": "tsc:build",
					"configName": "tsconfig.lib.json",
					"buildDepsName": "tsc:build-deps",
					"watchDepsName": "tsc:watch-deps"
				}
			}
		},
		{
			"plugin": "@nx/js/typescript",
			"options": {
				"typecheck": {
					"targetName": "tsc:typecheck"
				},
				"build": {
					"targetName": "tsc:build",
					"configName": "tsconfig.app.json",
					"buildDepsName": "tsc:build-deps",
					"watchDepsName": "tsc:watch-deps"
				}
			}
		}
	]
}

1.pnpm nx run frontend:tsc:build --verbose

Nx Report

NX   Report complete - copy this into the issue template

Node           : 22.13.1
OS             : win32-x64
Native Target  : x86_64-windows
pnpm           : 10.10.0

nx                 : 21.0.3
@nx/js             : 21.0.3
@nx/jest           : 21.0.3
@nx/eslint         : 21.0.3
@nx/workspace      : 21.0.3
@nx/cypress        : 21.0.3
@nx/devkit         : 21.0.3
@nx/eslint-plugin  : 21.0.3
@nx/nest           : 21.0.3
@nx/node           : 21.0.3
@nx/storybook      : 21.0.3
@nx/web            : 21.0.3
@nx/webpack        : 21.0.3
typescript         : 5.8.2
---------------------------------------
Registered Plugins:
@nx/cypress/plugin
@nx/storybook/plugin
@nx/js/typescript
@nx/js/typescript
---------------------------------------
Community plugins:
@compodoc/compodoc : 1.1.26
@jscutlery/semver  : 5.6.0
---------------------------------------
Cache Usage: 73.18 MB / 47.43 GB

Failure Logs

Package Manager Version

pnpm

Operating System

• macOS
• Linux
• Windows
• Other (Please specify)

Additional Information

No response

[sschneider-ihre-pvs]

I made a logpoint in loadResolvedNxPluginAsync to log the pluginName

[sschneider-ihre-pvs]

this is a list in the format of : . pnpm is version 10.10.0 as you can see

nx/core/project-json: <workspaceRoot>\node_modules\.pnpm\nx@21.0.3_@swc-node+registe_0f94e264b221ff96cd9053cd5414a3fb\node_modules\nx\src\plugins\project-json\build-nodes\project-json.js
load-resolved-plugin.js:8
nx/core/package-json: <workspaceRoot>\node_modules\.pnpm\nx@21.0.3_@swc-node+registe_0f94e264b221ff96cd9053cd5414a3fb\node_modules\nx\src\plugins\package-json\index.js
load-resolved-plugin.js:8
nx/js/dependencies-and-lockfile: <workspaceRoot>\node_modules\.pnpm\nx@21.0.3_@swc-node+registe_0f94e264b221ff96cd9053cd5414a3fb\node_modules\nx\src\plugins\js\index.js
load-resolved-plugin.js:8
10.10.0
pnpm.cjs:220601
@nx/js/typescript: <workspaceRoot>\node_modules\.pnpm\@nx+js@21.0.3_@babel+traver_1a26ade020f338d78ddfb7c27b830a5b\node_modules\@nx\js\typescript.js
load-resolved-plugin.js:8
2
10.10.0
pnpm.cjs:220601
@nx/js/typescript: <workspaceRoot>\node_modules\.pnpm\@nx+js@21.0.3_@babel+traver_1a26ade020f338d78ddfb7c27b830a5b\node_modules\@nx\js\typescript.js
load-resolved-plugin.js:8
10.10.0
pnpm.cjs:220601
@nx/storybook/plugin: <workspaceRoot>\node_modules\.pnpm\@nx+storybook@21.0.3_@babel_9fbb60ed50e2678a08ec639ba286c419\node_modules\@nx\storybook\plugin.js
load-resolved-plugin.js:8
10.10.0
pnpm.cjs:220601
@nx/cypress/plugin: <workspaceRoot>\node_modules\.pnpm\@nx+cypress@21.0.3_@babel+t_1ed4f6d9d2424a1cc6d6ddd5c711726c\node_modules\@nx\cypress\plugin.js
load-resolved-plugin.js:8
10.10.0

[kthom91]

This fixed it for me!
https://stackoverflow.com/questions/76270993/could-not-find-the-nrwl-lintereslint

[FrozenPandaz]

We should improve the error message here so that you can properly see which one Nx is having trouble resolving.

Were you able to find which plugin was causing the issue?

[sschneider-ihre-pvs]

Since pnpm showed up in the plugin lookup process also, I guess it was probably pnpm since it didn't had a pluginpath but I do not know.

[leggomuhgreggo]

EDIT: My issue was resolved by upgrading from Node v20.17 to Node v20.18. Found this Discord post which pointed me in the right direction

Thanks!

Old Report

Overview

We are also seeing "Unable to find local plugin", associated with attempts to upgrade to Nx 21 where the pipeline eventually just "hangs"

Unable to find local plugin [ 'libs/workspace-plugins/my-custom-plugin/src/index.ts' ] Map(2) {
  'apps/project-1' => 'project-1',
  'apps/project-2' => 'project-2'
}

There are hundreds of ^these "Unable to find local plugin" logs — all of them are related to our usage custom plugins.

It's associated with this build command (included some relevant env context)

  pnpm nx affected --target=build,build-storybook --configuration=development \
    --exclude='' \
    --parallel=2
  shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0}
  env:
    PNPM_HOME: /home/ubuntu/setup-pnpm/node_modules/.bin
    GIT_SHA: 1faf1acb4b494b9e9fc1177b0265bac60dc04ca1
    GIT_BRANCH: main
    BUILD_NUM: 15411373217
    NX_BASE: 2d8463b2e7bbf990fc46239e2a3d75397a528b38
    NX_HEAD: 1faf1acb4b494b9e9fc1177b0265bac60dc04ca1
    NX_CLOUD_DISTRIBUTED_EXECUTION: true
    NX_VERBOSE_LOGGING: true

Issue Details

We've attempted the upgrading to Nx v21 a few times, at this point, and each time:

• it passes all my feature branch CI (without any "Unable to find local plugin" logging that I can tell)
• when I merge to main, the pipeline "hangs" during the "deploy to development" phase
• eventually we "cancel" and git revert the upgrade change

Where does it hang?

• The GHA reporting hangs about 20 min into the pipeline, always after a webpack build for storybook
• The Nx Cloud reporting continues further, showing additional completed tasks, the last one is always our docker build
• It should be continuing to the deploy target, but we see no reporting associated with that.

*Note: The GHA interface sometimes chokes, when there are too many logs — so this isn't without precedent
**Note: We don't use DTE with our deploy tasks.

Additional Context

• We're using self-hosted GHA runners
  • After cancelling, we are seeing the usual cleanup steps from the GHA runner, so there's some ~proof of life from that part of the equation
• We're using pnpm@9.3.0 and node@20.17.0

Comments

I am planning to try again with a higher ubuntu-2xlarge resource class, for our ci runners, in case that might be a factor.

Would welcome any suggested troubleshooting. (We're all stoked for the v21 features!) 🙏

Thanks!

[lppedd]

I'm getting A LOT of those with local plugins, on Windows.

[NX v21.3.11 Daemon Server] - 2025-08-30T10:35:23.590Z - Time taken for 'loadDefaultNxPlugins' 1131.7754ms
Time for 'nx/core/project-json:createNodes' 32.671800000000076
Time for 'nx/core/project-json:createNodes' 26.963600000000042
Time for 'nx/core/package-json:createNodes' 154.0938
Time for 'nx/js/dependencies-and-lockfile:createNodes' 219.42740000000003
Unable to find local plugin [ 'nx-plugins/release/src/index.ts' ] Map(1) { 'client-extensions/common-component' => 'cc-vscode' }
Unable to find local plugin [ 'nx-plugins/vscode-l10n/src/index.ts' ] Map(1) { 'client-extensions/common-component' => 'cc-vscode' }
Unable to find local plugin [ 'nx-plugins/vsce/src/index.ts' ] Map(1) { 'client-extensions/common-component' => 'cc-vscode' }
Unable to find local plugin [ 'nx-plugins/extester/src/index.ts' ] Map(1) { 'client-extensions/common-component' => 'cc-vscode' }

Tho @FrozenPandaz, I see our local plugins are running correctly anyway. So I don't get what's going wrong.
I'm on a tsconfig path aliases setup.

[lppedd]

This problem has probably been introduced with commit 4254c4b.

[lppedd]

This code - and specifically the normalizeTargets() call at the end - doesn't make a lot of sense imo.

nx/packages/nx/src/project-graph/utils/project-configuration-utils.ts

Lines 666 to 696 in 0645648

	for (const root in projectRootMap) {
	const project = projectRootMap[root];
	// We're setting `// targets` as a comment `targets` is empty due to Project Crystal.
	// Strip it before returning configuration for usage.
	if (project['// targets']) delete project['// targets'];
	try {
	validateProject(project, projects);
	projects[project.name] = project;
	} catch (e) {
	if (isProjectWithNoNameError(e)) {
	projectRootsWithNoName.push(e.projectRoot);
	} else if (isProjectWithExistingNameError(e)) {
	const rootErrors = conflicts.get(e.projectName) ?? [
	projects[e.projectName].root,
	];
	rootErrors.push(e.projectRoot);
	conflicts.set(e.projectName, rootErrors);
	} else {
	throw e;
	}
	}
	normalizeTargets(
	project,
	sourceMaps,
	nxJsonConfiguration,
	workspaceRoot,
	projects
	);
	}

You're calling normalizeTargets with a projects dictionary that is not fully initialized yet, so once findNxProjectForImportPath is reached, there might be even 1 project only in that dictionary, then 2, then 3, and so on. Which is why we get that warning.

Instead, there should probably be a second loop just before returning:

for (const root in projectRootMap) {
  const project = projectRootMap[root];
  normalizeTargets(project, sourceMaps, nxJsonConfiguration, workspaceRoot, projects);
}

return projectRootMap;

[jdugas]

Is there any workaround for this? I've recently created an executor plugin locally that I want to use, but It's not working and appears to be because of this bug.
local executor example doc