# Motoko Dependecy Hell

**URL:** <https://forum.dfinity.org/t/motoko-dependecy-hell/56932>\
**Category:** Motoko\
**Created:** [September 6, 2025, 7:20pm UTC](https://forum.dfinity.org/t/motoko-dependecy-hell/56932 "2025-09-06T19:20:15Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![Gekctek](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/gekctek/32/6863_2.png) [@Gekctek](https://forum.dfinity.org/u/Gekctek)\
**Post date:** [October 8, 2025, 9:13pm UTC](https://forum.dfinity.org/t/motoko-dependecy-hell/56932/10 "2025-10-08T21:13:31Z")

</div>

> [@Motoko WASM size diagnosing - Part 2](https://forum.dfinity.org/t/motoko-wasm-size-diagnosing-part-2/58694):
>
> Im looking for some help/tips for figuring out what takes up so much space in my Motoko WASM output. The main issue is that I am going over the 2MB cap and I have many MOPS packages referenced and can’t seem to figure out the specific dependencies/code that are the issue or can be slimmed down. Manual inspection has been no luck and inspecting the WASM hasn’t been fruitful, except for one thing that I will mention below I can cut my WASM size from 2.6 MB to 1.8 MB with ‘trimming’ the WASM of …

---

_[View the full topic](https://forum.dfinity.org/t/motoko-dependecy-hell/56932)._