SShortSingh.
TopTechnologyAI & MLStartupsProgrammingScienceBusinessFinanceCrypto & Web3World
Back to feed
Programming

Claude Code 2.1.113 drops cli.js, breaking Android installs; 2.1.112 pinned as workaround

0
·3 views

Starting with version 2.1.113, the @anthropic-ai/claude-code package's bin entry points to a native binary rather than cli.js, which stops Claude Code from running on Android. The Shelly project therefore pinned version 2.1.112, the last release shipping cli.js as a pure JavaScript entry point. The native build fails on Android's bionic libc because of package-platform checks, an incompatible loader that rejects the musl linker's ELF layout, and SELinux restrictions on direct execution. Pinning the older version alone was not enough, and authentication also required transplanting credential files from a working Termux install. The packaging details come from tarball inspection and an on-device trace rather than official Anthropic documentation.

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 ·

Shopify equipment calculator compares unit costs and payback for store products

A case study describes building a cost and payback calculator for a Shopify equipment store, using a Webflow mortgage-broker site as its design and routing inspiration. The article notes that high-ticket products like home batteries and coffee machines need pages that explain both upfront price and long-term operating cost. It works through examples across categories such as home energy storage, coffee equipment, packaging and water-filter refills, with simple payback figures that are explicitly labelled as arithmetic illustrations rather than proven performance. The author cautions that scenario selectors only route visitors and do not establish compatibility, financing approval, or real customer returns. It also advises against copying placeholder review counts or certifications from design artwork, showing only genuine reviews and payment methods a store can actually offer.

0 comments Read more at DEV Community
0
ProgrammingDEV Community ·

ariaNotify() Arrives as Baseline, Offering Script-Driven Screen Reader Announcements

A new web API method, ariaNotify(), was introduced in September 2026 as a way to trigger screen reader announcements programmatically. It was first proposed in the WAI-ARIA 1.3 draft in 2024 and now has full support in Chrome, Firefox, Edge, and Safari. Unlike live regions, which require a hidden DOM element and announce only when its content structurally changes, ariaNotify() queues text for announcement directly through JavaScript. The author stresses that live regions are not being fully replaced, despite the title's suggestion. The piece also reviews how live regions currently work, covering roles like status and alert and attributes such as aria-live, aria-atomic, aria-busy, and aria-relevant.

0 comments Read more at DEV Community
0
ProgrammingDEV Community ·

Developer launches WandFX photo-to-video tool and ShopCutout product background remover

A developer has released two narrow web tools and shared them with the DEV Community for feedback. WandFX turns a single uploaded photo, such as a pet or consenting adult portrait, into a 4-8 second video using ready-made effects powered by MiniMax models, with some effects including AI-generated sound. ShopCutout removes product photo backgrounds in the browser, letting sellers export transparent PNGs or white-background JPGs sized for Amazon, Etsy, and Shopify, with batch processing of up to 20 photos. Eligible new WandFX users can try one free pet video, followed by non-expiring pay-as-you-go credits, while ShopCutout's basic local processing is free with no watermark or signup. The developer is asking users to report what works and what doesn't.

0 comments Read more at DEV Community
0
ProgrammingDEV Community ·

Valkey and Redis 2026: Same Core Speed, but Licensing and a Stream Key Trap Matter

A benchmark-based comparison finds Valkey and Redis performing nearly identically for caching and job queues, with throughput within a few percent of each other. The main differences lie in licensing, since Redis now offers RSALv2, SSPLv1 or AGPLv3 while Valkey uses BSD-3-Clause under Linux Foundation governance. Redis 8 also adds built-in features such as the Query Engine, Time Series, vector sets and extra probabilistic types that Valkey handles through modules or lacks. Migrating from Redis 8.10 carries a risk, because a stream key written by that version prevents Valkey from loading the snapshot or replicating from it. The author suggests choosing Valkey for open governance or Redis for its extra features, and reading the migration guidance first if moving off Redis 8.

0 comments Read more at DEV Community