library-migration-guide

To convert an Arduino library to a Blockly block, you map its functions into a block.json definition and a generator.js file. This migration standardizes hardware libraries for Blockly-based development workflows.

Migrating ESP32 libraries to Blockly involves adapting frontmatter, restructuring files, and defining integration points. It enforces block.json design and generator.js logic for deterministic, board-config aware code generation.

Yes, Blockly can generate code for ESP32 SPI and I2C buses. The migration process includes step-by-step guidelines for bus initialization and board configuration adaptation to ensure safe, deterministic outcomes.

The best way to structure a Blockly-compatible Arduino package is to organize assets into block definitions, generators, and toolbox mappings. This clear structure ensures consistent migration across different boards.

Blockly library migration produces non-deterministic code when board-specific configurations and generator.js logic are not properly enforced. Applying board-config aware generation ensures deterministic outcomes across Arduino and ESP32 ecosystems.