Compiling your Expansion

Why Compile to .NXE?

• Security: Your JavaScript and asset files are encrypted, preventing easy reverse‑engineering.

• Integrity: Bundles include an authentication tag (AES‑GCM), so corrupted or modified packages fail to load.

• Convenience: Distribute a single file per Expansion, rather than a folder of multiple files.

• Expansions Store: Our expansions store only accepts compiled expansions, you won't be able to share through our store without an NXE file.

---

Step-by‑Step: nexomaker.compileNxe()

1. Launch Nexo Maker Make sure the app is running and you can interact with your workspace as usual.

2. Open Developer Tools Press Ctrl + Shift + I

3. Switch to the Console Tab Click the “Console” tab to get a JavaScript REPL where you can call internal functions.

4. Invoke the Compiler In the console prompt, type:

   nexomaker.compileNxe()

   and press Enter.

5. Verify the .nxe Files Open your Documents/NexoMaker/Expansions folder in your file explorer. You’ll see:

   Folder: AwesomeExpansion
   File: MyAwesomeExpansion.nxe
   Folder: AnotherTool
   File: AnotherTool.nxe

   The .nxe files are what Nexo Maker will prefer and recognize as "Production Version".

---

Loading Order & Fallbacks

• Production Mode: Nexo Maker gives priority to .nxe files. If both MyExpansion/ and MyExpansion.nxe exist, only the encrypted bundle is loaded.

• Development Mode: If no .nxe is present, the plain folder loads as before—letting you iterate quickly without re‑packing after every change.

---

Troubleshooting Tips

• No .nxe Appears: Ensure you ran the console command while the app had write permission to your Documents folder.

• Invalid Bundle: If you manually create or rename the .nxe from a zip file, its authentication tag will fail and encryption method won't match — simply run nexomaker.compileNxe().

• Error compiling: To troubleshoot errors, you can run Nexo Maker directly through a CMD to see all backend console logs to find which errors happend through the compilation.

---

With this process, exporting and securing your Expansions becomes a one‑step operation—letting you focus on building great tools without worrying about source protection or distribution complexity.