Until now, I have been able to manage and get around issues with Motoko package dependency versions because I have been creating libraries without many dependencies and versions haven’t changed that much. Now that I have been working at a high level, like building HTTP framework libraries, the story…

Yep, I’m going through some of this pain - I’m using a MOPS package that has a dependency on core@0.6.0 and there are breaking changes in core@1.0.0 that affect it (function name changes!). You’re right, version pinning can help but not if the package I’m dependent on doesn’t use it. It is a concer…

[image] Gekctek: @rvanasa i see that there was this experiment: --override flag to support multiple package versions by rvanasa · Pull Request #5124 · dfinity/motoko · GitHub but im not sure if its being worked on anymore since base library changed to core which fixes that issue That is corre…

Also now i have discovered that I am blowing up the size of my output wasm files because now I get 2 packages instead of one, like core@1 and core might or might not be the same version, but since i use core@1 and someone else uses core it uses 2 ‘packages’ I have been having a hell of a time tryin…

Also @rvanasa , question: if i have a mops sources of --package core@1 .mops/core@1.0.0/src --package core .mops/core@1.0.0/src Will this include the source module twice and make the resulting WASM larger than if it was just --package core .mops/core@1.0.0/src

Does the Motoko compiler use tree shaking for files and symbols? So if I import only core/Int and use only Int.abs the build will not include other files from core package and other functions from Nat module.

[image] Gekctek: Will this include the source module twice and make the resulting WASM larger than if it was just … The files would only be included once. Behind the scenes, the --package flag simply maps the mo:* import to a file system directory, so both packages would point to the same mod…

[image] Gekctek: are there any good ways to see what specific modules the compiler is using, so i can evaluate the worst offenders and try to have the 3rd party library updated or something. @rvanasa any thoughts on this? I think i can slim things down a bit by specifying package and package…

I’m not aware of a simple way to do this but will mention this thread internally just in case.

[image] Motoko WASM size diagnosing - Part 2 Motoko 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 t…

Motoko Dependecy Hell

Developers Motoko

Gekctek October 8, 2025, 9:13pm 10

Topic		Replies	Views
Mops - on-chain package manager for Motoko! Programs & Applications	105	6390	July 1, 2025
[Developer Feedback Opportunity]: Motoko Package Manager Improvements/Redesign Language Support Motoko	10	929	May 13, 2023
🚀 Mops v3 is out: pinned Motoko toolchain, one lockfile model, faster installs (and no dfx) Motoko	1	187	August 20, 2026
Motoko WASM size diagnosing - Part 2 Motoko	14	197	October 10, 2025
Motoko WASM size diagnosing tips? Motoko	4	381	October 8, 2025

Motoko Dependecy Hell

Related topics