This PR implements native Windows resource editing in Zig, replacing the previous
rescle C++ implementation. Users can now customize Windows executables when using
'bun build --compile' with the following new options:
- --windows-icon <path> Set custom executable icon
- --windows-title <str> Set executable title/product name
- --windows-publisher <str> Set company/publisher name
- --windows-version <str> Set version (e.g. "1.2.3.4")
- --windows-description <str> Set executable description
- --windows-hide-console Hide console window (already existed)
Example:
```bash
bun build --compile \
--target=bun-windows-x64 \
--windows-icon=app.ico \
--windows-title="My Application" \
--windows-publisher="My Company" \
--windows-version="2.1.0.0" \
--windows-description="A powerful application built with Bun" \
index.ts
```
Implementation details:
- Pure Zig implementation in windows_resources.zig
- Removes C++ rescle dependency
- Creates WindowsSettings struct to organize all Windows options
- Supports cross-platform compilation (build Windows exe from Linux/macOS)
- Fixed alignment issues using safe memory operations
- Comprehensive test coverage in test/bundler/windows-resources-compile.test.ts
This allows full customization of Windows executable metadata without external dependencies.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
The install script was incorrectly setting $env:PATH by assigning an
array directly, which PowerShell converts to a space-separated string
instead of the required semicolon-separated format.
This caused the Windows PATH environment variable to be malformed,
making installed programs inaccessible.
Fixes#16811
### What does this PR do?
Fixes a bug in the Windows PowerShell install script where `$env:PATH`
was being set incorrectly, causing the PATH environment variable to be
malformed.
**The Problem:**
- The script assigns an array directly to `$env:PATH`
- PowerShell converts this to a space-separated string instead of
semicolon-separated
- This breaks the Windows PATH, making installed programs inaccessible
**The Fix:**
- Changed `$env:PATH = $Path;` to `$env:PATH = $Path -join ';'`
- Now properly creates semicolon-separated PATH entries as required by
Windows
### How did you verify your code works?
✅ **Tested the bug reproduction:**
```powershell
$Path = @('C:\Windows', 'C:\Windows\System32', 'C:\test')
$env:PATH = $Path # WRONG: Results in "C:\Windows C:\Windows\System32 C:\test"
## Summary
- Fixed buffer overflow in env_loader when parsing large environment
variables with escape sequences
- Replaced fixed 4096-byte buffer with a stack fallback allocator that
automatically switches to heap allocation for larger values
- Added comprehensive tests to prevent regression
## Background
The env_loader previously used a fixed threadlocal buffer that could
overflow when parsing environment variables containing escape sequences.
This caused crashes when the parsed value exceeded 4KB.
## Changes
- Replaced fixed buffer with `StackFallbackAllocator` that uses 4KB
stack buffer for common cases and falls back to heap for larger values
- Updated all env parsing functions to accept a reusable buffer
parameter
- Added proper memory cleanup with defer statements
## Test plan
- [x] Added test cases for large environment variables with escape
sequences
- [x] Added test for values larger than 4KB
- [x] Added edge case tests (empty quotes, escape at EOF)
- [x] All existing env tests continue to pass
fixes#11627
fixes BAPI-1274
🤖 Generated with [Claude Code](https://claude.ai/code)
---------
Co-authored-by: Claude <noreply@anthropic.com>
Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
