Use this before sharing a GalAssetBox build with other people.
Run:
npm ci
npm run release:checkThe release check verifies:
- required app, docs, Electron, plugin, and workflow files exist
- Electron dependency versions are pinned
- Electron renderer isolation and sandbox settings are present
- desktop bridge access stays limited to selected folders
- plugin safety wording and policy markers are present
- Windows packaging scripts and workflow are present
- help summary and category-rule features are present
- text files do not contain obvious local paths, private emails, old project names, or assistant transcript wording
- generated folders such as
node_modules/anddist/are ignored - dependency audit passes at
moderateor higher, excluding optional packages
Run:
python3 -m http.server 4174 --bind 127.0.0.1Open:
http://127.0.0.1:4174/
Check:
新手模式hides advanced actions高级功能shows plugin, manifest, sample, and help-summary actionsnpm run gateway:checkpasses before packaging载入样例works整理前预检appears after sample data loads分类page can add and delete a simple classification rule导出求助摘要downloads a Markdown file
Stop the server after testing.
Run:
npm startCheck:
- the desktop window opens
- source and output folder pickers open native dialogs
- the app does not ask for unrelated folders
For a local macOS directory package:
npm run packThen launch:
dist/mac-arm64/GalAssetBox.app
Use GitHub Actions:
Build Desktop Packages
Download:
GalAssetBox-windows
Windows runtime behavior is not considered verified until someone opens the Windows build on a real Windows machine and completes a small copied-folder test.
Do not share:
- game files
- extracted copyrighted assets
- third-party keys
- protected archive decryption steps
- DRM or authorization bypass instructions
It is fine to share:
- the GalAssetBox source code
- the desktop app package
- local-only demo plugin files
- help summaries that contain only metadata and sanitized logs