XLauncher

Imported from Stefano299/XLauncher (AGENTS.md). Install upstream with npx skills add Stefano299/XLauncher. Copyright stays with the author.

XLauncher

Commands

• Use npm with the committed package-lock.json; npm ci is the clean install command.
• npm run dev starts Vite and the Electron process through vite-plugin-electron. For testing changes, run npm run dev; do not build the executable installer.
• npm run lint runs Oxlint using .oxlintrc.json.
• npm run build runs the Vite build and then electron-builder; it regenerates dist/ and dist-electron/.
• npm run preview only serves the Vite renderer and does not launch the Electron shell.
• There is no automated test runner or npm test script. The root test_*.mjs/test_*.cjs files are manual download/archive diagnostics; URL-based diagnostics use node test_download_diag.mjs <URL> or node test_multipart.mjs <URL> and can create ignored download artifacts.

Architecture

• The user-facing interface must be in English (all labels, messages, and text shown in the UI).
• src/App.jsx is the React renderer. It must use the narrow window.electronAPI bridge rather than Node or Electron APIs directly.
• electron/main.js creates the BrowserWindow and owns the small top-level IPC handlers; electron/preload.cjs defines the exposed bridge; electron/gameManager.js registers the main download, game, persistence, and cloud-save handlers.
• When adding an IPC operation, update both electron/preload.cjs and its ipcMain.handle implementation. Keep the renderer and main-process payload names aligned.
• App data is persisted outside the repository under Electron's app.getPath('userData') as settings.json and games.json; the default download directory is <Downloads>/XLauncherGames.
• vite.config.js copies electron/preload.cjs into dist-electron/preload.cjs during build/startup. Edit the source preload file, not the copied artifact.

Operational Notes

• Game downloads support single-stream or ranged multi-part HTTP downloads, then optional ZIP/7Z/RAR extraction. RAR extraction invokes the Windows unrar-binaries executable, so archive behavior is platform-dependent.
• Cloud authentication uses a localhost OAuth callback on port 8888; connecting Google Drive or Dropbox requires that port to be available and opens an external browser.