Urgent.News

What's breaking now, across thousands of outlets.

Tech

Code review shouldn't catch import rules: a React Native architecture ESLint enforces

Short answer: Bareship writes its architecture down as lint errors instead of a wiki page. ESLint checks that imports go one way through five layers and that features never import each other, and dependency-cruiser checks the whole graph again in CI. Other rules each came from a real bug: hard-coded text, left / right styles that don't mirror in right-to-left languages, and calls the React…

Bareship enforces its architecture as lint errors using ESLint and dependency-cruiser. ESLint checks import directions through five layers, while dependency-cruiser examines the entire import graph in CI. Each rule originates from a real bug, such as hard-coded text, inconsistent text alignment, and React Compiler caches. Every error message provides a solution and explains the reasoning behind it, enabling teammates or AI agents to fix the code without seeking assistance.

This architecture enforcement is the main focus of this article, which is the third part of Bareship's building process.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Restaurant Menu Retrieval Architecture in 2026: Freshness Windows and Reranking Trade-offs

The least complex design that stays trustworthy is a staged retrieval pipeline: search fresh sources, query a bounded collection, then rerank only the small candidate set.

  • Restaurant menu retrieval uses staged pipeline with fresh sources and reranking.
  • Explicit freshness window and source context maintained throughout process.
  • Architecture divided into fast and slow clocks with 15-minute freshness window.

How to (not) Destroy Your SSD

37 TeraBytes in three weeks In June 2026 a Codex user opened an issue on the openai/codex repository with a set of numbers that did not seem to belong together. The SQLite database in which Codex keeps its feedback logs, ~/.codex/logs_2.sqlite , took up about 1.2 GiB and held 506,149 rows, an unremarkable size for a log, and yet the…

  • Codex user discovered 37TB SSD writes in 3 weeks
  • SQLite database logging causes SSD wear
  • Apple lacks SSD endurance ratings for MacBooks

More from Monday 16 November →