SShortSingh.
TopTechnologyAI & MLStartupsProgrammingScienceBusinessFinanceCrypto & Web3World
Back to feed
Programming

How to Fetch LCSC Component Prices and Stock as JSON Without Login or API Key

0
·1 views

Hardware developers working with bills of materials (BOMs) often need structured price and stock data for LCSC part codes, but common methods like search API scraping and headless browsers are unreliable or high-maintenance. A more stable approach involves querying LCSC's public product-detail pages, which are not restricted by robots.txt and return full data including price tiers, stock levels, and package details. Each part requires only a single lightweight HTTP request, producing clean JSON output that can be stored and refreshed on a schedule to track price changes. For larger BOMs, a hosted tool called LCSC Parts Scraper on Apify accepts a list of part codes and returns results as JSON or CSV via a simple API call. This method is considered more durable than search-API scrapers because it reads publicly accessible pages at low volume, avoiding anti-bot systems.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

Seven-point self-check every Solidity developer should run before mainnet launch

A security reviewer who audits small crypto protocols has published a 20-minute self-check list aimed at developers preparing to deploy Solidity smart contracts to mainnet. The checklist covers seven common vulnerability categories, including unguarded functions, the ERC-4626 first-depositor inflation attack, reentrancy risks, and insecure fund-rescue functions. It also flags the need for Chainlink oracle staleness checks and proper initializer guards in upgradeable proxy contracts. The author notes that most exploits targeting small protocols involve these straightforward, well-known issues shipped under time pressure. The guide is positioned as a lightweight alternative to skipping security altogether, while acknowledging it cannot replace a full human audit for protocol-specific logic bugs.

0 comments Read more at DEV Community
0
ProgrammingDEV Community ·

Developer Builds AI-Assisted Self-Healing Wrapper for Playwright Test Locators

A QA engineer transitioning away from hands-on coding used Claude AI to brainstorm technical side projects and developed a self-healing wrapper for Playwright end-to-end tests. The tool addresses a common problem where test locators break during active software development as UI elements change. When an original selector fails, a custom HealingEngine automatically tries seven fallback strategies in order, ranging from semantic data-testid attributes to relative screen position. Every healing attempt, successful or not, is logged by a HealingLog class that generates a recovery-rate report for the full test suite. The project, built in TypeScript, is published as Part 1, with further development planned.

0 comments Read more at DEV Community
0
ProgrammingDEV Community ·

Anthropic Adds Voice Mode to Claude Opus and Sonnet; Open-Weight Tool Cuts AI Costs

Anthropic has expanded its voice mode feature to its more powerful Claude Opus and Sonnet models, which previously was only available on the lighter Haiku model. The update enables developers to build real-time voice applications that leverage the deeper reasoning capabilities of the two advanced models. Separately, an open-source project called Echo, highlighted on Hacker News, claims to deliver AI results comparable to leading proprietary models at roughly one-third the cost. The project focuses on the strategic use of open-weight models, potentially through techniques such as fine-tuning, quantization, or efficient inference methods. Together, these developments reflect a broader push in the AI space toward both richer multimodal experiences and more cost-effective deployment strategies.

0 comments Read more at DEV Community
0
ProgrammingDEV Community ·

How PostgreSQL Automatically Reduces B+Tree Index Height After Deletions

B+tree indexes, used widely in databases, grow in height as data is inserted and pages split, with each additional level increasing lookup cost by one page read. In traditional implementations like Oracle Database, the index height never decreases after deletions unless the index is fully rebuilt. PostgreSQL, however, is capable of reducing the effective height of a B+tree index automatically when data is deleted, without requiring a manual rebuild. A test using a five-million-row table with UUID primary keys demonstrated a tree height of three levels, requiring three page reads per key lookup. This behavior distinguishes PostgreSQL from other database engines and has practical implications for query performance after large-scale deletions.

0 comments Read more at DEV Community
How to Fetch LCSC Component Prices and Stock as JSON Without Login or API Key · ShortSingh