mirror of
https://github.com/luanslimadev/Wand-Enhancer.git
synced 2026-08-28 23:01:14 +00:00
kitbyte
13759b1db6
- reduce ASAR IO overhead with streamed archive reads, buffered copies, faster relative-path handling and placeholder integrity records - fix in-place app.asar.unpacked packing/extraction self-copy cases that caused locked-file failures - tighten JS patch discovery with candidate bundle filters and search hints - require prebuilt remote-panel dist artifacts and clean up embedded bridge/script packaging - add unified build entrypoints for PowerShell, cmd and bash and move native CMake output under .tmp - add release metadata validation, changelog section extraction, pre-commit hook and GitHub Actions validation/release pipelines - make CHANGELOG the source of truth for release notes and document the tag-driven release flow - add updater release notes UI with latest/full changelog loading and localize the new update strings - modularize bridge renderer scripts, add installed apps and game status sync, and support remote launch/stop commands - centralize bridge protocol, IPC and WebSocket constants and improve LAN IP selection for QR pairing - refactor remote panel controls/state enums, persist accent color, polish library/session UI and refresh assets
Custom Renderer Scripts
Place user scripts here as plain .js files before running the Wand patch.
During patching, Wand Enhancer copies generated default scripts from web-panel/dist/renderer-scripts and user scripts from this folder into remote-panel/renderer-scripts inside app.asar. Default script sources live under web-panel/bridge/scripts/default and are generated by pnpm run build:bridge. Scripts are loaded in filename order on every Wand renderer startup.
Each script runs in the Wand renderer and receives a small global API:
;(function (WandEnhancer) {
WandEnhancer.log("custom script loaded", WandEnhancer.remoteUrl)
})(globalThis.WandEnhancer)
Use unique global guards for repeat-safe scripts because the renderer can be reinjected after navigation.