How to deploy a pnpm monorepo on Azure App Service when workspace packages are not resolving?

Question

How to deploy a pnpm monorepo on Azure App Service when workspace packages are not resolving?

Deepak Pandey 0

Monorepo (pnpm + turborepo) Azure App Service pe deploy ho raha hai.

Error: ERR_PNPM_WORKSPACE_PKG_NOT_FOUND

"@voice-ai/database@workspace:*" is in dependencies but

no package named "@voice-ai/database" is present in the workspace.

Packages found in the workspace: @voice-ai/web

Golla Venkata Pavani 7,530 Reputation points Microsoft External Staff Moderator

2026-06-01T19:30:43.25+00:00
Hi @Deepak Pandey

Thank you for reaching out regarding the pnpm + Turborepo monorepo deployment on Azure App Service.

The error ERR_PNPM_WORKSPACE_PKG_NOT_FOUND occurs because Azure App Service uses the Oryx build system, which has limited native support for pnpm workspaces. When you deploy only a subfolder (e.g., the web app), Oryx cannot see the full workspace root and other packages like @voice-ai/database.

Recommended Next Steps:
Building the application outside of App Service (locally or in CI/CD) and deploying a fully prepared artifact. This eliminates workspace dependency issues.
Steps:

Build the monorepo (locally or in GitHub Actions/Azure DevOps):
pnpm install --frozen-lockfile pnpm run build # or turbo run build --filter=@voice-ai/web

Create a production-ready bundle using pnpm deploy (strongly recommended):
pnpm --filter=@voice-ai/web deploy --prod ./deploy-web

Deploy the ./deploy-web folder as a ZIP package to Azure App Service using:

ZIP Deploy (via Azure Portal, VS Code, or CLI)

Run from Package

Key Azure Configuration:

Set SCM_DO_BUILD_DURING_DEPLOYMENT = false (since you're pre-building)

Enable Run from Package in Application Settings

Reference:
https://learn.microsoft.com/en-us/azure/app-service/configure-language-nodejs?pivots=platform-linux
https://learn.microsoft.com/en-us/azure/app-service/deploy-zip?tabs=cli

Kindly let us know if the above helps or you need further assistance on this issue.

Please "accept" if the information helped you. This will help us and others in the community as well.
Praneeth Maddali 12,670 Reputation points Microsoft External Staff Moderator

2026-06-02T01:04:49.8733333+00:00
Hi @Deepak Pandey

Thanks for reaching out with the details — I understand you're hitting the ERR_PNPM_WORKSPACE_PKG_NOT_FOUND error when deploying your pnpm + Turborepo monorepo to Azure App Service. This is a fairly common issue with workspace dependencies

Azure App Service’s build system (Oryx) often only sees the folder you deploy. When it runs pnpm install, it can’t resolve workspace packages like @voice-ai/database@workspace:* because the full monorepo structure isn’t present.

Recommended Solution

The cleanest approach is to pre-build your app and use pnpm deploy to create a self-contained production folder. This resolves all workspace dependencies into regular ones and gives you a clean node_modules ready for deployment

Steps:

In your CI pipeline (or locally), run.
pnpm install --frozen-lockfile pnpm run build --filter=@voice-ai/web # or turbo run build

Create a production-ready package
pnpm --filter=@voice-ai/web deploy --prod ./deploy-web

Zip the contents of the ./deploy-web folder (make sure there’s no extra top-level folder inside the zip) and deploy it using ZIP Deploy.

In your App Service Configuration > Application settings, add:

SCM_DO_BUILD_DURING_DEPLOYMENT = false

WEBSITE_RUN_FROM_PACKAGE = 1 (recommended for better performance)

This method avoids most workspace and Oryx-related issues.

Reference:

https://learn.microsoft.com/en-us/azure/app-service/deploy-zip?tabs=cli

https://learn.microsoft.com/en-us/azure/app-service/configure-language-nodejs?pivots=platform-linux

https://learn.microsoft.com/en-us/azure/app-service/deploy-run-package

Kindly let us know if the above helps or you need further assistance on this issue.

Please "upvote" if the information helped you. This will help us and others in the community as well.
Golla Venkata Pavani 7,530 Reputation points Microsoft External Staff Moderator

2026-06-02T19:22:18.4833333+00:00

Hi @Deepak Pandey

I'm just reaching out to see if your issue has been resolved or if you've had a chance to review my previous comment?

1 answer

Your answer

Golla Venkata Pavani 7,530 Reputation points Microsoft External Staff Moderator

2026-06-01T19:30:43.25+00:00

Hi @Deepak Pandey

Thank you for reaching out regarding the pnpm + Turborepo monorepo deployment on Azure App Service.

The error ERR_PNPM_WORKSPACE_PKG_NOT_FOUND occurs because Azure App Service uses the Oryx build system, which has limited native support for pnpm workspaces. When you deploy only a subfolder (e.g., the web app), Oryx cannot see the full workspace root and other packages like @voice-ai/database.

Recommended Next Steps:
Building the application outside of App Service (locally or in CI/CD) and deploying a fully prepared artifact. This eliminates workspace dependency issues.
Steps:

Build the monorepo (locally or in GitHub Actions/Azure DevOps):
pnpm install --frozen-lockfile pnpm run build # or turbo run build --filter=@voice-ai/web

Create a production-ready bundle using pnpm deploy (strongly recommended):
pnpm --filter=@voice-ai/web deploy --prod ./deploy-web

Deploy the ./deploy-web folder as a ZIP package to Azure App Service using:

ZIP Deploy (via Azure Portal, VS Code, or CLI)

Run from Package

Key Azure Configuration:

Set SCM_DO_BUILD_DURING_DEPLOYMENT = false (since you're pre-building)

Enable Run from Package in Application Settings

Reference:
https://learn.microsoft.com/en-us/azure/app-service/configure-language-nodejs?pivots=platform-linux
https://learn.microsoft.com/en-us/azure/app-service/deploy-zip?tabs=cli

Kindly let us know if the above helps or you need further assistance on this issue.

Please "accept" if the information helped you. This will help us and others in the community as well.
Praneeth Maddali 12,670 Reputation points Microsoft External Staff Moderator

2026-06-02T01:04:49.8733333+00:00

Hi @Deepak Pandey

Thanks for reaching out with the details — I understand you're hitting the ERR_PNPM_WORKSPACE_PKG_NOT_FOUND error when deploying your pnpm + Turborepo monorepo to Azure App Service. This is a fairly common issue with workspace dependencies

Azure App Service’s build system (Oryx) often only sees the folder you deploy. When it runs pnpm install, it can’t resolve workspace packages like @voice-ai/database@workspace:* because the full monorepo structure isn’t present.

Recommended Solution

The cleanest approach is to pre-build your app and use pnpm deploy to create a self-contained production folder. This resolves all workspace dependencies into regular ones and gives you a clean node_modules ready for deployment

Steps:

In your CI pipeline (or locally), run.
pnpm install --frozen-lockfile pnpm run build --filter=@voice-ai/web # or turbo run build

Create a production-ready package
pnpm --filter=@voice-ai/web deploy --prod ./deploy-web

Zip the contents of the ./deploy-web folder (make sure there’s no extra top-level folder inside the zip) and deploy it using ZIP Deploy.

In your App Service Configuration > Application settings, add:

SCM_DO_BUILD_DURING_DEPLOYMENT = false

WEBSITE_RUN_FROM_PACKAGE = 1 (recommended for better performance)

This method avoids most workspace and Oryx-related issues.

Reference:

https://learn.microsoft.com/en-us/azure/app-service/deploy-zip?tabs=cli

https://learn.microsoft.com/en-us/azure/app-service/configure-language-nodejs?pivots=platform-linux

https://learn.microsoft.com/en-us/azure/app-service/deploy-run-package

Kindly let us know if the above helps or you need further assistance on this issue.

Please "upvote" if the information helped you. This will help us and others in the community as well.
Golla Venkata Pavani 7,530 Reputation points Microsoft External Staff Moderator

2026-06-02T19:22:18.4833333+00:00

Hi @Deepak Pandey

I'm just reaching out to see if your issue has been resolved or if you've had a chance to review my previous comment?

Answer 1

The error indicates that the deployment environment is building the app in a way that doesn’t correctly include or resolve all workspace packages in the pnpm monorepo. On Azure App Service, this typically happens when using ZIP or package-based deployment and the build output or package structure doesn’t match what the platform expects.

To make the workspace packages resolve correctly on Azure App Service:

Build the app before packaging
- Run the full build locally or in CI (for example with Turborepo) so that the deployable output contains all necessary files.
- For Node.js apps, ensure all npm/pnpm build steps are completed and the final output is self-contained.
- When creating the ZIP package for deployment, include only the built output and required runtime files, not the raw monorepo source.
Create a valid ZIP package for App Service
- From the root of the built app (the folder that contains the entry file such as index.js or the built web assets), create a ZIP without nesting an extra top-level folder.
- For example:
```
     zip -r app.zip .
```
- Ensure that the ZIP structure matches what App Service expects: the entry point and package.json (if needed) are at the root of the ZIP, not inside additional nested directories.
Avoid unsupported package layouts
- If using a build system that produces nested or MSBuild-style packages, adjust it to output a folder-based structure that can be zipped directly.
- If the package format is incompatible with ZIP deploy, use the Azure App Service deploy task with Web Deploy or restructure the build to produce a flat folder output.
Use Azure Pipelines deployment tasks correctly (if using CI/CD)
- In Azure Pipelines, ensure the build stage publishes the correct artifact (the built app folder or ZIP) and the release/deploy stage points to that artifact.
- If using AzureWebApp@1 or AzureRmWebAppDeployment, set the package input to the correct path of the built app.
Troubleshoot dependency issues
- If the build fails due to dependency resolution, inspect the Node/npm output logs to identify malformed package.json or incompatible packages.
- Fix any package.json issues locally, rebuild, and redeploy.

These steps ensure that the deployed package contains a consistent, self-contained build where pnpm workspace packages are already resolved, avoiding runtime workspace resolution errors on Azure App Service.

References: