Construir un .mojopkg

Sharing loose files is fragile. Mojo lets you bundle a folder of modules into one tidy package artifact. 📦

A package is a directory of related modules treated as a single importable unit, much like a folder of files.

A folder becomes a package when it holds an __init__.mojo file. That file marks the directory as importable.

The mojo package command compiles that folder into one distributable file you can hand to others.

The result is a .mojopkg file. It is a compiled bundle of your modules, ready to share or ship.

Anyone with your .mojopkg on the import path can use it just like a normal module they wrote themselves.

The same import works whether the package is a source folder or a compiled .mojopkg. You can switch freely.

A packaged build is one compiled file instead of many sources, so it loads fast and is simpler to distribute.

The -o flag picks the output filename. Without it, the package keeps its directory name with a .mojopkg suffix.

Mojo looks for imports on its import path. Place the .mojopkg where your project searches and the import resolves.

A single .mojopkg is the clean way to give your library to a teammate or another project. 🚀

Let us nail down how a folder becomes a package.

A package is a folder of modules with __init__.mojo. Run mojo package to compile it into one shareable .mojopkg. 🎯