Files

root 77b4d10af8 Refactor filename naming system and apply convention-based renames

Standardize settings file naming and relocate documentation files
Fix code quality violations from rsx:check
Reorganize user_management directory into logical subdirectories
Move Quill Bundle to core and align with Tom Select pattern
Simplify Site Settings page to focus on core site information
Complete Phase 5: Multi-tenant authentication with login flow and site selection
Add route query parameter rule and synchronize filename validation logic
Fix critical bug in UpdateNpmCommand causing missing JavaScript stubs
Implement filename convention rule and resolve VS Code auto-rename conflict
Implement js-sanitizer RPC server to eliminate 900+ Node.js process spawns
Implement RPC server architecture for JavaScript parsing
WIP: Add RPC server infrastructure for JS parsing (partial implementation)
Update jqhtml terminology from destroy to stop, fix datagrid DOM preservation
Add JQHTML-CLASS-01 rule and fix redundant class names
Improve code quality rules and resolve violations
Remove legacy fatal error format in favor of unified 'fatal' error type
Filter internal keys from window.rsxapp output
Update button styling and comprehensive form/modal documentation
Add conditional fly-in animation for modals
Fix non-deterministic bundle compilation

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

2025-11-13 19:10:02 +00:00

2.5 KiB

Executable File

Raw Blame History

JQHTML Integration - RPC Server Architecture

Overview

JQHTML template compilation uses long-running Node.js RPC server via Unix socket to avoid spawning Node.js processes for each .jqhtml file during bundle builds.

Components

JqhtmlWebpackCompiler.php - PHP client, manages compiler server lifecycle
jqhtml-compile-server.js - Node.js RPC server (ES module), uses @jqhtml/parser API directly
jqhtml-compile (legacy) - CLI from @jqhtml/parser npm package (no longer called)

Server Lifecycle

Lazy start: Server spawns on first JQHTML compilation during bundle build
Startup: Checks for stale socket, force-kills if found, starts fresh server
Wait: Polls socket with ping (50ms intervals, 10s max), fatal error if timeout
Usage: All JQHTML compilations during bundle builds go through RPC
Shutdown: Graceful shutdown when bundle compilation completes (registered shutdown handler)

Socket

Path: storage/rsx-tmp/jqhtml-compile-server.sock
Protocol: Line-delimited JSON over Unix domain socket

RPC Methods

ping → "pong" - Health check
compile → {file: {status, result}, ...} - Batch compile multiple templates
shutdown → Graceful server termination

PHP API

JqhtmlWebpackCompiler::start_rpc_server();        // Lazy init, auto-called
JqhtmlWebpackCompiler::stop_rpc_server($force);   // Clean shutdown
JqhtmlWebpackCompiler::_compile_via_rpc(...);     // Internal RPC compilation

Compilation Details

Uses compileTemplate from @jqhtml/parser directly (not CLI)
Always compiles in IIFE format with sourcemap support
Maintains existing cache strategy (mtime-based)
Throws Jqhtml_Exception_ViewException for template errors with line/column info

Cache Integration

Cache checked before RPC call - only uncached or stale templates sent to server for compilation. Cache directory: storage/rsx-tmp/jqhtml-cache/

Error Handling

Server failure → fatal error (no fallback). Server must start or bundle compilation fails. Template errors include line/column information for precise error reporting.

Performance Impact

Before RPC: N Node.js process spawns (one per .jqhtml file needing compilation) After RPC: Single persistent Node.js process, reused across all compilations (~1-2s startup overhead)

ES Module Support

The RPC server is an ES module (uses import syntax) to directly use @jqhtml/parser's ES module exports. This provides direct API access without CLI wrapper overhead.

2.5 KiB Executable File Raw Blame History