Q: How does HyperLive Pro compile React in the browser without Node.js?
A: The system utilizes standard ES modules (ESM) supported natively by modern web browsers. When code is edited, the integrated Babel Standalone engine reads the Abstract Syntax Tree (AST), transpiles the JSX markup into React element declarations (React.createElement), and bundles them dynamically into a transient in-memory Javascript Blob URL mapping scheme.
Q: Can I use third-party packages from NPM in my JSX files?
A: Absolutely! HyperLive Pro is equipped with a dynamic ESM import plugin. When you define an import statement like import confetti from 'canvas-confetti', our Babel hook automatically intercepts the request and rewrites the source pathway to load directly from a high-performance CDN registry (such as esm.sh), resolving and preparing the package client-side.
Q: Why are external redirects blocked inside the live canvas?
A: To protect your active development session and prevent "frame-busting" scripts from hijacking the browser workspace. The live canvas runs within a secure, sandboxed iframe. If an executed script attempts to overwrite the parent window's location (e.g. window.top.location = url), the system catches the transition mask instantly and blocks the operation to preserve your unsaved code.
Q: How does the Console Redirection Bridge capture errors?
A: The sandbox frame overrides standard console.log, console.warn, and console.error functions. When your transpiled application emits a log or encounters a runtime error, a custom listener intercepts the call, wraps the payload context, and transmits it via window.parent.postMessage directly to the IDE panel for immediate diagnostic viewing.
Q: Does HyperLive Pro upload my workspace code to any backend servers?
A: No. HyperLive Pro is designed on a static, fully server-free serverless architecture. All compilation, file traversal, syntax formatting, and virtualization occurs 100% locally within your browser tab. Your files never leave your system, offering absolute privacy and high compilation speeds.
Q: How do I export my virtual workspace folder as a standard ZIP file?
A: The environment features an in-browser ZIP packer module (powered by JSZip). By selecting the 'Export Workspace' action, the virtual file system compresses the active directories, formats the file indices, and packages them into a single downloadable ZIP file natively in your browser.