@neocompose/cli 0.70.2 → 0.70.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +7 -0
- package/dist/neo.mjs +1569 -679
- package/dist/test-worker.mjs +3322 -1375
- package/package.json +1 -1
- package/skills/neocompose-cli/SKILL.md +22 -1
- package/skills/neocompose-cli/references/cli-development.md +1 -1
- package/skills/neocompose-cli/references/values-identities-and-references.md +6 -0
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,12 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## [0.70.3] - 2026-10-06
|
|
4
|
+
|
|
5
|
+
- `neo export` reads each project file from the path its declaration names. Moving a file to another folder without renaming it changes no record, so nothing is pushed. Before, the export kept reading the old path and failed with "missing". A new file dropped at the old path is now discovered as a new file, and `neo resolve` writes a conflicted file to its moved path.
|
|
6
|
+
- A project file can be declared in any `.neo` file and listed in its registry by name, the way a local value is: `@id("…") NeoAudioClip FISHING_WIN_1 = new("Files/AudioClips/fishingwin1.mp3");` in its own file, and `NeoAudioClip FishingWin1 = FISHING_WIN_1;` in `Files/AudioClips.neo`. The same works for `NeoImage` in `Files/Images.neo`. Push, pull and reset keep the declaration in its file. A declaration no registry lists, or one listed twice, is an error.
|
|
7
|
+
- Initializer runtime errors report the failing expression, including nested functions, getters, constructors, and cached builds. Compiler errors point at invalid argument, return, and nested initializer expressions. Duplicate IDs and initializer assignments produce source diagnostics instead of internal exceptions. Null unwraps, list bounds, and arithmetic errors explain how to correct the failure. Cached `neo test` runtime failures retain their source positions. Fixes [#1203](https://github.com/ryanbliss/neo-compose/issues/1203).
|
|
8
|
+
- Registry updates preserve unchanged image and audio declarations, their order, comments, and annotations. New entries append, deleted entries are removed in place, and emitted `@settings(name: ...)` preserves names that differ from the binary basename. Registry errors identify the affected declaration. Fixes [#1207](https://github.com/ryanbliss/neo-compose/issues/1207).
|
|
9
|
+
|
|
3
10
|
## [0.70.2] - 2026-10-06
|
|
4
11
|
|
|
5
12
|
- After `neo push` creates, replaces or moves a project file, its committed bytes become the file's merge base at its new path, as a pull's would. Before, the re-export after the push failed for every new file with "the pull recorded no bytes for it", and for a moved file with "missing". Either failure left the Unity project marked as a local export.
|