JLCSearch

Why it's ranked here

The combination of a browsable catalogue, direct JSON output, stock data, pricing, and footprint lookup makes JLCSearch useful during part selection and automation. Its focused database should be faster to handle than the upstream source, but the supplied generated records expose enough classification and completeness problems to require verification.

What's good

The web interface doubles as an API query builder: users configure filters, then select JSON to obtain the corresponding request. Results include practical procurement fields such as manufacturer part number, package, stock, and minimum quantity price. Nightly stock synchronization updates changed quantities and explicitly zeros recently removed parts.

Tradeoffs

Coverage is selective because only categories with defined schemas enter the optimized database, and stale components are removed. Generated documentation contains blank category headings, missing attributes, and clearly misplaced components, including microcontrollers under relays and filters. Footprint strings also require a copper overlap above 95 percent; processed parts below that threshold return no match.

How to use it well

Use it when choosing stocked JLCPCB parts interactively, scripting repeatable catalogue queries, or retrieving a generated footprint string for an LCSC number. Treat returned category data as a shortlist and verify suspicious records. It does not replace the complete upstream catalogue, since unsupported component types and unimported attributes remain unavailable.

Observed

Primary language

TypeScript

Runtime and installation

Bun is required; dependencies are installed for the root project and Cloudflare worker

Interfaces

Browsable web search, URL-derived JSON API, and footprint-string HTTP endpoint

Production platform

Cloudflare Worker with D1; no separate origin web server

Data pipeline

Rebuilds an upstream SQLite catalogue into an optimized SQLite database

License

No license is stated in the supplied repository text