tscircuit lets you design PCBs in React and TypeScript by writing circuit parts as JSX code instead of using classic CAD tools.
A simple project can fit in just 40 lines of code, and the project already supports live browser preview, 3D view, and Gerber export.
Web developers, electronics hobbyists, and PCB designers can use it because it connects familiar frontend coding with hardware design and makes circuit building more approachable.
Working with tscircuit can take you from code to a real board, since the author showed the full process of creating a board and ordering it from JLC.
Full ERC and DRC support is not included yet, so the platform is functional but not yet a complete replacement for traditional PCB design tools.
An interesting project is gaining popularity on site X tscircuit , which combines frontend web technologies (React + TypeScript) with electronics design. The idea is simple: instead of classic CAD like KiCad or Altium, we write the circuit as JSX code. The electronic components are represented as React elements, such as a resistor or capacitor. The code is processed into a circuit structure (JSON) and then rendered and prepared for further stages. The project has modules for previewing the circuit directly in the browser, also in 3D form. All this is live, with no delays or charges. The current version is fully functional and allows you to create your own tiles, although it does not yet include full systems such as ERC and DRC. Export to Gerber format is supported, however, and the author has already demonstrated the full process of creating a tile including ordering it from JLC. For a simple project, you can fit in just 40 lines of code.
The project is available under the MIT licence and is 100% open source.
tscircuit can be tried for free online:
https://tscircuit.com/editor Just paste in an example of tile code and you can then edit it live along with a 2D/3D preview:
Spoiler:
Code: Javascript
Log in, to see the code
A gallery of screenshots showing the results for the code posted above:
You're a bit right, but not entirely either - I remember, for example, that the formats from the old Eagle were pure XML, I even made a simple parser of its files myself at one time and it pretty much worked, displayed elements, etc. in my own program without external libraries. XML is a text format, it is easy to parse, it would be worse for LLM if it was a binary format. I'll have to try one day out of curiosity to generate .sch and .brd files for Eagle in the biggest LLMs and see if they can create correct ones.
The project is seemingly old, 2 years old, but is only now gaining popularity and visibility thanks to better language models.
Given how many variables, datasheets, differences in elements there are, we are still safe for the time being.
