Azure App Service (Linux): Kudu absoluteTar.sh excludes .prisma (any folder starting with ".") from node_modules during Zip Deploy

Question

Azure App Service (Linux): Kudu absoluteTar.sh excludes .prisma (any folder starting with ".") from node_modules during Zip Deploy

Syed Junaid 0

I'm deploying a Next.js app using Prisma ORM to Azure App Service (Linux) using Zip Deploy via the Azure CLI:

az webapp deployment source config-zip --resource-group <your-resource-group> --name <your-app-name> --src ./package.zip

🔍 Issue

After deployment, the Prisma client fails to run because the .prisma/ folder is missing from node_modules/. This causes runtime errors when Prisma tries to load the client.

In the App Service Linux environment (via Kudu debug console), I found that the issue stems from this deployment step: /opt/Kudu/Scripts/absoluteTar.sh Which contains this command: cd node_modules tar -zcf ../node_modules.tar.gz *

Since * excludes hidden files like .prisma/, this results in Prisma client code being omitted from the deployed app — even though it exists before deployment.

✅ What I’ve Verified

.prisma/ is present inside node_modules/ before packaging
The issue occurs only after deployment to App Service (Linux)
The problem is directly caused by the use of * in absoluteTar.sh, which excludes dotfolders
This behavior did not occur in earlier deployments — so it seems like a recent change

📦 Environment Details

App Service OS: Linux (Node.js)
Kudu Version: 20250502.11
Kudu Commit: e32687b96fdab5e2f321f98f33b917df6606e460
Deploy Method: Zip Deploy via az webapp deployment source config-zip

❓My Questions

When was this change introduced to use tar -zcf ... * in absoluteTar.sh?
Why was * used, knowing it excludes dotfiles like .prisma/?
Is this an intentional change to Kudu or the App Service Linux deployment container?
Where can I find release notes or a changelog that tracks these internal container/Kudu updates?
What is the recommended solution? Should I:
- Add a startup.sh that manually extracts a correct tarball?
- Run npx prisma generate at container start?

Thanks in advance for clarification — this behavior change has broken previously working deployments and seems undocumented.

Alekhya Vaddepally 1,670 Reputation points Microsoft External Staff Moderator

2025-05-15T23:17:06.1166667+00:00
Hi Syed Junaid,
In the current version of the deployment script, this line It uses command *, which unfortunately excludes hidden files and folders (ie, which starts with a dot like. PRISMA/. As a result, the internal. Prisma/ folder of your Prisma client is missing after deployment - when the prisma tries to reach the client, leads to the runtime failures.

This Kudu or built -in app service Linux container seems to have a change recently, and wisely, it is a braking workflow that previously worked without any problem.

At this time, the most reliable solution is to re -run the Prince Client generation in the runtime inside the app service container. Here's how you can do it:

Generate NPX Prisma in Startup, You can add a post install script to your package. Json:

"scripts": { "postinstall": "prisma generate" }

Or, if you are using a custom startup. sh script for your app, you can include:

npx prisma generate

This ensures that the Prisma client is re -generated on the container start, using the skim and binaries already exist in your app.
npx prisma generate
Custom startup command for Linux Web Apps
if you have any further concerns or queries, please feel free to reach out to us.
Alekhya Vaddepally 1,670 Reputation points Microsoft External Staff Moderator

2025-05-16T16:10:07.0533333+00:00

Hi Syed Junaid,
We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution, please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Syed Junaid 0 Reputation points

2025-05-17T13:55:26.6766667+00:00

Hi, I'm just going to switch to Container Apps instead rather than having a custom startup script.
Syed Junaid 0 Reputation points

2025-05-17T14:14:20.3566667+00:00
Just to add, this can be solved (if you stick with app service), by creating a custom startup script where you run the command which adds certain hidden folders to node_modules.

For example, create a startup.sh file and add the following if you're using Prisma ORM.

# Generate Prisma client npx --yes prisma generate --schema database/prisma/schema.prisma # Start the server node server.js

Then in your app service change the startup command to 'startup.sh', via Portal or any other means.

This solves the issue.

2 answers

Your answer

Alekhya Vaddepally 1,670 Reputation points Microsoft External Staff Moderator

2025-05-15T23:17:06.1166667+00:00

Hi Syed Junaid,
In the current version of the deployment script, this line It uses command *, which unfortunately excludes hidden files and folders (ie, which starts with a dot like. PRISMA/. As a result, the internal. Prisma/ folder of your Prisma client is missing after deployment - when the prisma tries to reach the client, leads to the runtime failures.

This Kudu or built -in app service Linux container seems to have a change recently, and wisely, it is a braking workflow that previously worked without any problem.

At this time, the most reliable solution is to re -run the Prince Client generation in the runtime inside the app service container. Here's how you can do it:

Generate NPX Prisma in Startup, You can add a post install script to your package. Json:

"scripts": { "postinstall": "prisma generate" }

Or, if you are using a custom startup. sh script for your app, you can include:

npx prisma generate

This ensures that the Prisma client is re -generated on the container start, using the skim and binaries already exist in your app.
npx prisma generate
Custom startup command for Linux Web Apps
if you have any further concerns or queries, please feel free to reach out to us.
Alekhya Vaddepally 1,670 Reputation points Microsoft External Staff Moderator

2025-05-16T16:10:07.0533333+00:00

Hi Syed Junaid,
We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution, please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Syed Junaid 0 Reputation points

2025-05-17T13:55:26.6766667+00:00

Hi, I'm just going to switch to Container Apps instead rather than having a custom startup script.
Syed Junaid 0 Reputation points

2025-05-17T14:14:20.3566667+00:00

Just to add, this can be solved (if you stick with app service), by creating a custom startup script where you run the command which adds certain hidden folders to node_modules.

For example, create a startup.sh file and add the following if you're using Prisma ORM.

# Generate Prisma client npx --yes prisma generate --schema database/prisma/schema.prisma # Start the server node server.js

Then in your app service change the startup command to 'startup.sh', via Portal or any other means.

This solves the issue.

Answer 1

Just to add, this can be solved (if you stick with app service), by creating a custom startup script where you run the command which adds certain hidden folders to node_modules.

For example, create a startup.sh file and add the following if you're using Prisma ORM.

BashCopy


# Generate Prisma client
npx --yes prisma generate --schema database/prisma/schema.prisma

# Start the server
node server.js

Then in your app service change the startup command to 'startup.sh', via Portal or any other means.

This solves the issue.

Answer 2

Hi Syed Junaid,

I'm glad that you were able to resolve your issue and thank you for posting your solution so that others experiencing the same thing can easily reference this!

Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others ", I'll repost your solution in case you'd like to "Accept " the answer.

**
Issue:
Azure App Service (Linux): Kudu absoluteTar.sh excludes .prisma (any folder starting with ".") from node_modules during Zip Deploy

Solution:

Just to add, this can be solved (if you stick with app service), by creating a custom startup script where you run the command which adds certain hidden folders to node_modules.

For example, create a startup.sh file and add the following if you're using Prisma ORM.


# Generate Prisma client
npx --yes prisma generate --schema database/prisma/schema.prisma

# Start the server
node server.js

Then in your app service change the startup command to 'startup.sh', via Portal or any other means.

This solves the issue.

If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.

Alekhya Vaddepally 1,670 Reputation points Microsoft External Staff Moderator

2025-05-28T20:55:21.32+00:00

Hi Syed Junaid,
If this answer was helpful and pointed you in the right direction, please consider clicking "Accept Answer"—it may benefit other community members reading this thread. If you have any further questions, feel free to let us know.

Share via

Azure App Service (Linux): Kudu absoluteTar.sh excludes .prisma (any folder starting with ".") from node_modules during Zip Deploy

🔍 Issue

✅ What I’ve Verified

📦 Environment Details

❓My Questions

2 answers

Your answer