# Serverless package size inconsistent when project is inside a GUID-named folder (50MB vs 1MB)

**URL:** <https://forum.serverless.com/t/serverless-package-size-inconsistent-when-project-is-inside-a-guid-named-folder-50mb-vs-1mb/21525>\
**Category:** Serverless Framework\
**Tags:** aws, lambda, cloudformation\
**Created:** [December 18, 2025, 7:14am UTC](https://forum.serverless.com/t/serverless-package-size-inconsistent-when-project-is-inside-a-guid-named-folder-50mb-vs-1mb/21525 "2025-12-18T07:14:34Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![knaresh](https://avatars.discourse-cdn.com/v4/letter/k/67e7ee/32.png) [@knaresh](https://forum.serverless.com/u/knaresh)\
**Post date:** [December 18, 2025, 7:14am UTC](https://forum.serverless.com/t/serverless-package-size-inconsistent-when-project-is-inside-a-guid-named-folder-50mb-vs-1mb/21525/1 "2025-12-18T07:14:34Z")

</div>

**Environment:**

- Serverless Framework version: 3.39.0

- Node.js version: 22.x

- OS: Windows Server

- npm version: 10.8.3

**Setup:** We’re deploying Lambda functions using Octopus Deploy + TeamCity. Octopus automatically creates a temporary working directory with a GUID as the folder name for each deployment.

**Example paths:**

- GUID folder: `C:\Octopus\Work\`2b046a8c-de00-4177-96b1-aff635522059`\auth-lambda`

- Normal folder: `C:\Projects\auth-lambda`

**Commands:**

bash

```auto
npm i --omit=dev
npm i serverless
serverless deploy -s stageName

```

**Issue:** The same project with identical code produces vastly different package sizes depending on the parent folder name:

| Folder Type | Package Size |
| --- | --- |
| GUID-named folder | ~50MB |
| Normal folder | ~1MB |

No changes to code, dependencies, or configuration — only the folder name differs.

**Steps to reproduce:**

1. Create a simple Serverless project

2. Copy it into two locations — one with a GUID folder name, one without

3. Run `npm i --omit=dev && npm i serverless && serverless package` in both

4. Compare `.serverless/*.zip` sizes

**Workaround:** Using `npx serverless package` Instead of installing serverless locally, it avoids the issue.

**Question:** Is this a known issue with how Serverless Framework resolves paths or package dependencies? Could the hyphens, length, or alphanumeric pattern in the GUID folder names be triggering unexpected behavior?

Any insights or suggestions would be appreciated.

---

<div class="post-metadata">

**Author:** ![beenmeckel](https://avatars.discourse-cdn.com/v4/letter/b/8dc957/32.png) [@beenmeckel](https://forum.serverless.com/u/beenmeckel)\
**Post date:** [April 21, 2026, 10:53pm UTC](https://forum.serverless.com/t/serverless-package-size-inconsistent-when-project-is-inside-a-guid-named-folder-50mb-vs-1mb/21525/2 "2026-04-21T22:53:10Z")

</div>

Inconsistent Serverless package sizes, often reported on Reddit, typically stem from dynamic dependency inclusion, non-deterministic node\_modules bundling, or fluctuating package.json resolutions in monorepos. To stabilize size, use esbuild to tree-shake code

[192.168.100.1](https://1921681001.id/) [192.168.1.1](https://19216811.cam/)