no-cycle finds 0 cycles in next.js (and other lies caches tell you)
The article discusses the discrepancies found in cycle detection algorithms used in linting tools for Next.js. It highlights how different tools can yield varying results due to caching mechanisms that may incorrectly mark files as acyclic. The author identifies a specific bug in the caching logic that leads to false positives in cycle detection.
- ▪Benchmarking revealed that two ESLint plugins found 0 cycles, while a different tool identified 17 cycles in the same codebase.
- ▪The bug in the caching layer caused files with cycles at greater depths to be incorrectly marked as acyclic.
- ▪The issue is exacerbated in larger codebases where a single incorrect cache entry can affect multiple files.
DEV.to (Top) files mainly under programming. We currently carry 4,924 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | DEV.to (Top) |
| Canonical URL | https://dev.to/ofri-peretz/no-cycle-finds-0-cycles-in-nextjs-and-other-lies-caches-tell-you-3ld8 |
| Publication time | Sun, 24 May 2026 03:07:43 +0000 |
| Retrieval time | 2026-05-24T03:37:30.269Z |
| Last seen | 2026-05-24T03:37:30.269Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | VdumAMH3qQzC |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3669992) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Ofri Peretz Posted on May 24 • Originally published at ofriperetz.dev no-cycle finds 0 cycles in next.js (and other lies caches tell you) #eslint #staticanalysis #performance #algorithms Inside our linter benchmarks (2 Part Series) 1 What ground truth caught that unit tests missed: 3 real bugs in 9 flagship lint rules 2 no-cycle finds 0 cycles in next.js (and other lies caches tell you) We benchmark import-next/no-cycle against eslint-plugin-import/no-cycle and oxlint's native Rust…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
