Mojo Academy · 강의

.mojopkg 만들기

재사용할 수 있도록 패키지를 묶습니다.

.mojopkg 만들기은(는) CoddyKit의 무료 Mojo Academy 강의입니다. 이것은 4개 중 2번째 강의입니다. 아래에서 전체 강의를 무료로 읽을 수 있으며, 내장 코드 에디터와 24/7 AI 튜터와 함께 브라우저에서 직접 실습할 수 있습니다. 이 강의는 Mojo Academy 학습 경로의 일부이며, 진행 상황이 웹과 CoddyKit 앱에 동기화됩니다. Mojo Academy 강의에는 총 4개의 강의가 포함되어 있습니다.

이 강의의 일부는 아직 번역되지 않았으며 영어로 표시됩니다.

From Files to a Package

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

A Package Is a Folder

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

The init Marker

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

Bundle It Up

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

mojo package mypkg -o mypkg.mojopkg

The .mojopkg File

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

Import the Package

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

from mypkg import add

Folder or File, Same Import

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

Why Compile a Package

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

Set the Output Name

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

Finding the Package

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

Share With Confidence

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

Quick Check

Let us nail down how a folder becomes a package.

Recap

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

자주 묻는 질문