Praise for Learning LARC {.unnumbered}

Copyright {.unnumbered}

Copyright © 2025 LARC Team. All rights reserved.

Printed in the United States of America.

Published by LARC Press.

The LARC logo and name are trademarks of the LARC Project.

While the publisher and authors have used good faith efforts to ensure that the information and instructions contained in this work are accurate, the publisher and authors disclaim all responsibility for errors or omissions, including without limitation responsibility for damages resulting from the use of or reliance on this work.

Use of the information and instructions contained in this work is at your own risk. If any code samples or other technology this work contains or describes is subject to open source licenses or the intellectual property rights of others, it is your responsibility to ensure that your use thereof complies with such licenses and/or rights.

Table of Contents {.unnumbered}

Preface {.unnumbered}

• Who This Book Is For
• What You'll Learn
• Conventions Used in This Book
• Using Code Examples
• How to Contact Us
• Acknowledgments

Part I: Foundations {.unnumbered}

• The Problem with Modern Web Development
• A Return to Fundamentals
• The LARC Philosophy
• Why "No Build" Matters
• When to Use LARC
• What You'll Build

• Web Components Refresher
• The Page Area Network (PAN)
• Event-Driven Architecture
• State Management Philosophy
• Module System
• The Component Lifecycle

• Setting Up Your Development Environment
• Your First LARC Application
• Project Structure
• Import Maps Explained
• Development Workflow
• Common Patterns

Part II: Building Components {.unnumbered}

• Anatomy of a LARC Component
• Shadow DOM Deep Dive
• Attributes and Properties
• Component Styling
• Lifecycle Methods
• Testing Components

• Understanding Pub/Sub Architecture
• Topics and Namespaces
• Publishing Messages
• Subscribing to Events
• Message Patterns
• Debugging PAN Communication

• Component-Local State
• Shared State Patterns
• The pan-store Component
• IndexedDB Integration
• Persistence Strategies
• Offline-First Applications

• Compound Components
• Higher-Order Components
• Component Composition
• Slots and Content Projection
• Dynamic Component Loading
• Performance Optimization

Part III: Building Applications {.unnumbered}

• Client-Side Routing
• The pan-router Component
• Route Parameters
• Nested Routes
• Route Guards
• History Management

• Form Components
• Two-Way Data Binding
• Validation Strategies
• Error Handling
• File Uploads
• Form Submission

• The pan-fetch Component
• REST API Integration
• GraphQL Support
• WebSocket Communication
• Server-Sent Events
• Error Handling and Retry Logic

• Authentication Patterns
• The pan-auth Component
• JWT Token Management
• Protected Routes
• CORS Considerations
• Security Best Practices

Part IV: Advanced Topics {.unnumbered}

• Backend Architecture
• Node.js Integration
• PHP Connector
• Python/Django Integration
• Database Patterns
• Real-Time Communication

• Unit Testing Components
• Integration Testing
• End-to-End Testing
• Visual Regression Testing
• Performance Testing
• Continuous Integration

• Loading Strategies
• Code Splitting
• Lazy Loading Components
• Caching Strategies
• Bundle Size Optimization
• Performance Monitoring

• Static Hosting
• CDN Configuration
• Environment Variables
• CI/CD Pipelines
• Monitoring and Analytics
• Production Best Practices

Part V: Ecosystem {.unnumbered}

• Using the Component Registry
• Contributing Components
• Creating a Component Library
• Documentation Strategies
• Versioning and Releases

• Development Tools
• CLI Tools
• VS Code Integration
• Browser DevTools
• Debugging Techniques

• Case Study: E-Commerce Platform
• Case Study: Dashboard Application
• Case Study: Blog/CMS
• Lessons Learned
• Best Practices

Appendices {.unnumbered}

• Custom Elements
• Shadow DOM
• HTML Templates
• ES Modules

• Core Methods
• Message Formats
• Topic Patterns
• Configuration Options

• Built-in Components
• Component Properties
• Events and Methods

• From React
• From Vue
• From Angular
• From jQuery

• Official Documentation
• Community Resources
• Video Tutorials
• Example Projects

Index {.unnumbered}

About the Author {.unnumbered}

Christopher Robison is a veteran software engineer and architect with nearly three decades of experience building systems that range from biotech and online trading platforms to complex web applications and AI-driven tools. A lifelong maker with a deep appreciation for open standards, he has spent his career exploring the boundaries of what the web can do when you stop fighting the platform and start embracing it.

He is the creator of LARC.js and the PAN message bus, a browser-native architecture inspired by the elegant simplicity of the automotive CAN bus. His work blends engineering pragmatism with a playful curiosity that has led him to design everything from 3D printers and robotics to interactive music systems and decentralized applications.

Christopher currently lives in San Francisco, where he continues to build things that bridge the digital and physical worlds — and occasionally sneaks off to play punk rock shows with his band.

Foreword {.unnumbered}

I didn't set out to build a framework. I set out to escape one — or at least escape the gravitational pull of the endless build pipeline.

After decades of building things for the web, my machine had become a storage exhibit of Node versions, Python versions, shims, wrappers, and dependency folders with the mass of small moons. Not because any of it was bad. Build tools are fine. For big projects, they're downright amazing. But somewhere along the way, we normalized the idea that even the simplest experiment needed a pipeline, a bundler, a transpiler, and a twelve-step hydration ritual before it could say "Hello, World."

That friction bothered me.

I wanted the feeling I had back in the early days: the joy of dropping a