Build failing during 'mangler' step with 'Overlapping edit' error on Windows #850

Been trying to find a way to use void editor on a machine without admin rights, as no user level installer exists, I tried to compile myself.

Description

When attempting to build the project from source on a fresh Windows installation, the process fails during the final code "mangling" stage. This occurs after successfully resolving earlier C++ build requirements (Spectre-mitigated libs) and NLS generation issues (by modifying the gulpfile). The final error is an [mangler] ERROR: Overlapping edit.

Environment

• OS: Windows 11
• Node.js: v22.17.0
• npm: v10.9.2
• RAM: 64GB
• Build Tools: Visual Studio 2022 with the "Desktop development with C++" workload and "MSVC v143... Spectre-mitigated libs (Latest)" component installed.

Steps to Reproduce

1. Clone the repository:

   git clone [https://github.com/voideditor/void.git](https://github.com/voideditor/void.git) void-main
   

2. Navigate into the directory:

   cd void-main
   

3. Install all dependencies. This completes successfully with the proper Visual Studio components installed.

   npm install
   

4. Build the React components.

   npm run buildreact
   

5. Modify build/gulpfile.js around line 80 to enable NLS generation, changing false to true:
   • From: compileTask('src', 'out', false)
   • To: compileTask('src', 'out', true)
6. In the terminal, set the Node.js memory limit to avoid memory-related hangs during the NLS build step.

   set NODE_OPTIONS=--max-old-space-size=8192
   

7. Run the main compile command.

   npm run compile
   

Expected Behavior

The npm run compile command should complete successfully, generating all necessary build files, including the nls.messages.json file.

Actual Behavior

The compile process runs for over 10 minutes and then fails with a specific error during the mangler stage.

    at Mangler.computeNewFileContents (C:\dev-tools\void-main\build\lib\mangle\index.js:574:35)
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)

Additional Context

This issue appears to be the final step after resolving the problems described in Issue #615. Forcing the NLS generation (by setting the build flag to true) and increasing the Node.js heap size successfully avoids the hang mentioned in that issue, but reveals this new mangler error.