kiota-dom-export.txt is large and included in the released package

Open Beginner friendly
#1,287 3 comments 2 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@Fryguy is already working on this.

Since May 19, 2026.

  • #1488 by @Fryguy — open

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
62/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
python
Domain
release

Research direction

Start by tracing how lib/python3.13/site-packages/msgraph/generated/kiota-dom-export.txt enters the release package, beginning with the package and distribution configuration. Build the release artifact and verify that kiota-dom-export.txt is absent while the SDK remains usable and the package is reduced by about 30MB.

Written by the indexing model from the issue text.

Description

Needs: Attention :wave: type:bug
Describe the bug

The kiota-dom-export.txt file is very big (>30MB), and is included in the final release package. That file alone is 12% of the final package size. It doesn't appear to be used at runtime, and so I think it's not necessary to be shipped. Would it be possible to exclude this file from the release to save disk space?

Expected behavior

kiota-dom-export.txt not shipped saving 30MB

How to reproduce

N/A

SDK Version

1.37.0

Latest version known to work for scenario above?

No response

Known Workarounds

No response

Debug output

No response

Configuration
  • OS: macOS 15.5
  • architecture: arm64

Do you know whether it is specific to that configuration?

Probably not

Other information
(test-venv) $ du -sh lib/python3.13/site-packages/msgraph/generated/kiota-dom-export.txt
 30M	lib/python3.13/site-packages/msgraph/generated/kiota-dom-export.txt
(test-venv) $ du -sh lib/python3.13/site-packages/msgraph
249M	lib/python3.13/site-packages/msgraph
Dominant language
Python
Stars
634
Forks
100
Avg merge
23h 18m
Merged PRs (30d)
7

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoftgraph/msgraph-sdk-python

All issues in microsoftgraph/msgraph-sdk-python

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.