PowerApps CLI script not found during pac code init execution

[megel]

Describe the bug
The pac code init command fails with a System.IO.FileNotFoundException stating "Could not find the PowerApps CLI script". The error occurs after successful authentication when the CLI attempts to locate and execute the PowerApps CLI script file.

To Reproduce
Steps to reproduce the behavior:

1. Navigate to a directory (e.g., /workspaces/my-app-2)
2. Run command: pac code init --displayName "My new App"
3. Wait for authentication to complete successfully
4. See error: "Could not find the PowerApps CLI script"

Expected behavior
The pac code init command should successfully initialize a new code project after authentication completes. The CLI should be able to locate and execute the required PowerApps CLI script to create the project structure.

Screenshots
N/A - Error captured in log file (pac-log.txt) see pac-log-sanitized.txt

Desktop (please complete the following information):

• OS: Linux (Ubuntu 24.04.4 LTS in dev container)
• CLI Tool: PowerApps CLI (pac)
• Version: 2.5.1+gab954cf

Additional context

• Environment: GitHub Codespace
• Error Location: bolt.module.code.NodeCliManager.GetPowerAppsCliScript() at line 133
• Authentication: Successfully completes using UNIVERSAL auth profile (User type)
• Environment: Connected to [DEV] US Preview environment (https://....crm.dynamics.com/)
• Timestamp: 2026-04-08 11:28:47-48 (first occurrence), 11:33:48-49 (second occurrence)
• Exit Code: 1
• Additional Note: libsecret keyring is not installed, falling back to plaintext cache (multiple warnings throughout log)
• Stack Trace Summary: Error propagates through:
  • NodeCliManager.GetPowerAppsCliScript() → line 133
  • NodeCliManager.ExecuteNodeCommand() → line 29
  • InitVerb.ExecuteAsync() → line 124

The issue appears to be missing Node.js CLI script files required by the PAC tool's code module.

pac-log-sanitized.txt

[thuemmercnf]

I was experiencing a similar issue with pac code add-data-source on 2.5.1. I had to roll back to 2.4.1

[eschavez]

Thanks for the detailed report, Michael! We've reproduced this — it's a regression in PAC CLI 2.5.1 where the bundled Node.js script files aren't being found by NodeCliManager.GetPowerAppsCliScript().

Confirmed behavior:

• Affects pac code init (and based on a comment above, also pac code add-data-source) on PAC CLI 2.5.1 in Linux/GitHub Codespace environments
• Error: System.IO.FileNotFoundException — "Could not find the PowerApps CLI script"

Workaround:
Roll back to PAC CLI 2.4.1 while we investigate. This appears to be a packaging regression in 2.5.1.

We're investigating and will update this issue once we have more information.

[eschavez]

Update: We've published a known issue for this: Known issue: pac code commands fail in PAC CLI v2.5.1

We've identified the root cause as a packaging regression in v2.5.1 — NodeCliManager.GetPowerAppsCliScript() cannot locate bundled Node.js scripts. We're actively investigating a fix.

Workaround: Downgrade to PAC CLI v2.4.1 as noted above. See the linked discussion for updates as we work through this.

[eschavez]

The issue has been resolved. Please upgrade to the latest version of PAC CLI (v2.6.3)

[megel]

@eschavez also with the newest version, the pac code init fails with "Could not find the PowerApps CLI script" when Using Globally Installed PAC CLI
Here is what I did:

Describe the bug

When pac is installed as a global .NET tool (Microsoft.PowerApps.CLI.Tool) rather than via the Power Platform Tools VS Code extension, the pac code init command fails immediately with a FileNotFoundException. The globally installed tool does not bundle the Node.js-based PowerApps CLI script (powerapps-cli.js) that bolt.module.code.NodeCliManager requires to execute code-first app operations.

This is the same root cause as the pac code push failure — the entire pac code * command family is affected.

Steps to Reproduce

1. Install PAC CLI as a global .NET tool:

   dotnet tool install --global Microsoft.PowerApps.CLI.Tool

2. Ensure ~/.dotnet/tools is on $PATH ahead of any extension-provided pac:

   export PATH="$HOME/.dotnet/tools:$PATH"

3. Create an auth profile:

   pac auth create --name DEV ...
   pac auth select -n DEV

4. Navigate to an empty directory intended for a new code-first Power App
5. Run:

   pac code init --displayName "My App"

6. Command fails with Could not find the PowerApps CLI script

Expected behavior

pac code init should scaffold a new code-first Power App project, or emit a clear actionable error if the required companion package (microsoft.powerapps.cli) is missing from the installation.

Actual behavior

Command fails with a fatal System.IO.FileNotFoundException:

Could not find the PowerApps CLI script
System.IO.FileNotFoundException: Could not find the PowerApps CLI script
   at bolt.module.code.NodeCliManager.GetPowerAppsCliScript()
   at bolt.module.code.NodeCliManager.ExecuteNodeCommand(...)
   at bolt.module.code.InitVerb.ExecuteAsync(...)

Authentication and environment resolution succeed. The failure occurs inside InitVerb at the point where the Node CLI script is looked up.

Screenshots or Error Messages

See attached sanitized log: pac-log-sanitized-code-init-missing-script.txt

Key log entry:

2026-04-14 09:34:22.2162 | FTL | bolt.Session :: Could not find the PowerApps CLI script|EXCEPTION: System.IO.FileNotFoundException: Could not find the PowerApps CLI script
   at bolt.module.code.NodeCliManager.GetPowerAppsCliScript() in NodeCliManager.cs:line 136
   at bolt.module.code.InitVerb.ExecuteAsync(...) in InitVerb.cs:line 124

Environment information

• PAC CLI version: 2.6.3+gfc7e1f3 (global .NET tool Microsoft.PowerApps.CLI.Tool)
• Installation method: dotnet tool install --global Microsoft.PowerApps.CLI.Tool
• Runtime: .NET 10.0.4
• OS: Ubuntu 24.04.4 LTS (dev container)
• Auth profile type: Application (Service Principal)
• Command used: pac code init --displayName "My 3rd app"

Additional context

The microsoft.powerapps.cli NuGet package (distinct from microsoft.powerapps.cli.tool) contains the Node.js CLI script required by all pac code * sub-commands. This package is bundled inside the VS Code Power Platform Tools extension at:

/home/codespace/.vscode-remote/extensions/microsoft-isvexptools.powerplatform-vscode-2.0.139/dist/pac/
  microsoft.powerapps.cli.2.5.1.nupkg
  microsoft.powerapps.cli.tool.2.5.1.nupkg

The global .NET tool installation does not include or reference microsoft.powerapps.cli, so the script lookup in NodeCliManager.GetPowerAppsCliScript() (line 136) fails for all pac code verbs (init, push, and likely others).

Related bug: bug-report-code-push-missing-script.md — identical root cause, pac code push / PushVerb.

[eschavez]

@megel - Unfortunately, shortly after I posted my reply above, we found that we had only fixed the issue for the MSI install version. The .Net tool install is still broken. See the known issue here for the latest.

[nlvraghavendra]

I've the PAC CLI installed using VS Code extension. Any timeline on when the extension version is getting fixed?