feat: implement aggressive WASM bundle size optimization (6.20% reduction)

[devin-ai-integration]

WASM Bundle Size Optimization

This PR implements aggressive WASM bundle size optimization for libpg-query-node, achieving a 6.20% total bundle size reduction (131.09 KB reduction from 2.07 MB to 1.94 MB) while maintaining full API compatibility.

🎯 Optimization Results

Metric	Before	After	Reduction
Total Bundle Size	2.07 MB	1.94 MB	131.09 KB (6.20%)
WASM File	1.99 MB	1.91 MB	80.97 KB (3.88%)
JavaScript Wrapper	58.66 KB	6.64 KB	52.02 KB (89%)
All Tests Passing	✅ 53/53	✅ 53/53	Maintained

🚀 Optimization Strategies Implemented

1. Aggressive Compilation Flags

• -Oz: Replaced -O3 with size-focused optimization
• --closure 1: Enabled Google Closure Compiler for advanced JavaScript minification
• -Wl,--gc-sections,--strip-all: Dead code elimination and symbol stripping
• -sFILESYSTEM=0: Removed filesystem support for additional size reduction

2. Build Configuration Updates

• New optimized build targets: build-optimized and build-optimized-no-fs
• Separate optimization flags: Isolated optimization settings from standard build
• Enhanced Makefile: Proper LDFLAGS integration for optimization flags

3. Size Tracking Tooling

• Automated size reporting: scripts/size-report.js for detailed bundle analysis
• Before/after comparison: scripts/size-compare.js with baseline tracking
• New npm scripts: Easy access to optimized builds and size monitoring

📊 Detailed Size Breakdown

The optimization achieved significant reductions across multiple areas:

1. WASM Binary Optimization (3.88% reduction)

   • -Oz flag optimized for size over speed
   • wasm-opt post-processing with aggressive size settings

2. JavaScript Wrapper Optimization (89% reduction)

   • Google Closure Compiler with ADVANCED_OPTIMIZATIONS
   • Filesystem removal eliminated unnecessary Node.js compatibility code
   • Dead code elimination removed unused runtime methods

3. Build Process Enhancements

   • Incremental optimization testing to measure individual flag impact
   • Comprehensive test validation after each optimization step

🛠 New Build Commands

# Standard build (unchanged)
npm run wasm:build

# Optimized builds (new)
npm run wasm:build-optimized           # Full optimization
npm run wasm:build-optimized-no-fs     # + filesystem removal
npm run build:optimized                # Complete optimized build with JS

# Size tracking (new)
npm run size-baseline                  # Save current as baseline
npm run size-report                    # Show current bundle sizes
npm run size-compare                   # Compare with baseline

✅ Verification & Testing

• Full test suite: All 53 tests continue to pass with optimized builds
• API compatibility: No breaking changes to public API
• Build validation: Tested incremental optimization flags individually
• Cross-platform: Docker-based Emscripten build ensures consistency

📈 Performance Impact

• Build time: ~20 seconds (optimized) vs ~15 seconds (standard)
• Runtime performance: Size optimization may have minimal performance trade-offs
• Memory usage: Reduced bundle size improves loading and memory footprint

🔧 Implementation Details

The optimization maintains backward compatibility by:

• Preserving existing build target unchanged
• Adding separate optimized build targets
• Maintaining all exported functions and runtime methods
• Keeping full test coverage and validation

📋 Files Changed

• Makefile: Added optimized build targets and compilation flags
• package.json: New build scripts for optimized builds and size tracking
• scripts/size-report.js: Automated bundle size reporting tool
• scripts/size-compare.js: Before/after size comparison utility
• OPTIMIZATION_PROGRESS.md: Detailed optimization documentation and results

---

Link to Devin run: https://app.devin.ai/sessions/c47cb00752b24deda9d86e51b99c9b95

Requested by: Dan Lynch ([email protected])

This optimization provides significant bundle size reduction while maintaining full functionality, making libpg-query-node more efficient for web and Node.js applications.

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment and CI monitoring