Repository navigation
feat(moonbit): generate moon.mod and moon.pkg manifests - #1741
Merged
alexcrichton merged 1 commit intoOct 12, 2026
Merged
Conversation
alexcrichton
approved these changes
Oct 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Generated MoonBit projects still use the legacy JSON manifests. Emit
moon.modandmoon.pkgfor bindings and the bundled async runtime, and update the test harness and fixture configurations to use the same format.The migration preserves package imports and aliases, warning settings, Wasm target selection, memory and heap settings, and all existing export mappings. The exporting package is explicitly declared as a foreign library. Export annotations remain a separate follow-up.