what is xgecu-web fr?

xgecu-web is a toolkit that lets a web browser talk directly to XGecu T48 and T56 chip programmers, hardware devices used to read and write memory chips like EEPROMs and ROMs, for example the kind found in older car engine control units. It uses a browser technology called WebUSB, which lets JavaScript communicate with USB hardware without installing separate driver software, provided the browser is Chromium based and the page is served over HTTPS or from localhost. Under the hood, the core logic is written in Zig, a low level systems programming language, and compiled to WebAssembly so it can run inside the browser. A TypeScript layer on top provides the actual API that a web application would call, such as listing connected devices, checking that a chip is seated correctly in the programmer, and reading or writing a ROM image with progress updates along the way. The project currently focuses its ready to use device support on T48 hardware. Support for the T56 protocol exists in the code, but there is not yet a validated catalog of T56 chip definitions, so high level T56 operations are not usable until that catalog is filled in. Because writing to a chip is a physically risky operation that can permanently damage hardware if done incorrectly, the README spells out a detailed safety checklist: always back up a chip before writing, verify writes when possible, double check the chip package and adapter, compare image lengths before flashing, and understand that browser permission prompts only grant USB access rather than confirming the correct chip is actually inserted. To use it in a project, you install it directly from a tagged GitHub release since it is not yet published to the npm registry. Building it from source requires specific versions of Node.js, pnpm, and the Zig compiler, after which a set of pnpm scripts build the WebAssembly module, the TypeScript package, and run the test suite. A small example React application is included to demonstrate connecting to a programmer and reading or writing a ROM in the browser. The README does not state a software license.