Mostlylucid.StyloExtract.Core
1.7.1
See the version list below for details.
dotnet add package Mostlylucid.StyloExtract.Core --version 1.7.1
NuGet\Install-Package Mostlylucid.StyloExtract.Core -Version 1.7.1
<PackageReference Include="Mostlylucid.StyloExtract.Core" Version="1.7.1" />
<PackageVersion Include="Mostlylucid.StyloExtract.Core" Version="1.7.1" />
<PackageReference Include="Mostlylucid.StyloExtract.Core" />
paket add Mostlylucid.StyloExtract.Core --version 1.7.1
#r "nuget: Mostlylucid.StyloExtract.Core, 1.7.1"
#:package Mostlylucid.StyloExtract.Core@1.7.1
#addin nuget:?package=Mostlylucid.StyloExtract.Core&version=1.7.1
#tool nuget:?package=Mostlylucid.StyloExtract.Core&version=1.7.1
Mostlylucid.StyloExtract.Core
Extraction orchestration: wires parse, fingerprint, match, induce, apply, and render into ILayoutExtractor.ExtractAsync.
What this package is
LayoutExtractor (implements ILayoutExtractor) is the single entry point for extraction. It coordinates the full pipeline:
- Parse HTML via
IHtmlDomParser - Clean DOM via
IDomCleaner - Fingerprint via
IStructuralFingerprinter(MinHash + LSH + anchor-path + pq-grams) - Fast-path LSH match against
ITemplateIndex(< 1 ms for known templates) - If miss: slow-path pq-gram cosine match
- If novel: segment + classify + induce extractor via
IExtractorInducer - Apply extractor via
IExtractorApplicator(or heuristic classification on novel) - Render to Markdown via
IMarkdownRenderer - Record observation; trigger refit if drift threshold exceeded
- Emit
StyloExtractSignalevents viaTypedSignalSink
When to depend on this directly
Consumed transitively by Mostlylucid.StyloExtract.AspNetCore. Take a direct dependency only if you are wiring the DI registrations manually (e.g. in a non-ASP.NET host) or adding the LayoutExtractor to a custom container.
Usage
// Standard wiring via AddStyloExtract (preferred)
builder.Services.AddStyloExtract(o => { o.StorePath = "store.db"; });
// Inject and call
var extractor = sp.GetRequiredService<ILayoutExtractor>();
var result = await extractor.ExtractAsync(
html,
new Uri("https://example.com/article"),
new ExtractionOptions { Profile = ExtractionProfile.RagFull });
Console.WriteLine(result.Markdown);
Console.WriteLine(result.Match.Status); // FastPathHit on repeat visits
Console.WriteLine(result.Match.TemplateVersion);
AOT
This package is IsAotCompatible=true.
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net10.0 is compatible. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
-
net10.0
- Microsoft.Extensions.Logging.Abstractions (>= 10.0.1)
- Mostlylucid.StyloExtract.Abstractions (>= 1.7.1)
- Mostlylucid.StyloExtract.Fingerprint (>= 1.7.1)
- Mostlylucid.StyloExtract.Heuristics (>= 1.7.1)
- Mostlylucid.StyloExtract.Html (>= 1.7.1)
- Mostlylucid.StyloExtract.Markdown (>= 1.7.1)
- Mostlylucid.StyloExtract.Templates (>= 1.7.1)
NuGet packages (1)
Showing the top 1 NuGet packages that depend on Mostlylucid.StyloExtract.Core:
| Package | Downloads |
|---|---|
|
Mostlylucid.StyloExtract.AspNetCore
AddStyloExtract() DI extensions for ASP.NET Core. The response-policy framework (IResponsePolicy) is the canonical response-transformation primitive: Markdown content negotiation and cache-hint emission are the first two built-in instances. Brings in the full StyloExtract stack wired through Microsoft.Extensions.DependencyInjection. Opt-in middleware, per-action attributes, and Minimal API extensions transparently convert HTML responses to Markdown when clients send Accept: text/markdown. Browser-friendly query-string Accept override and opt-in IDistributedCache support included. |
GitHub repositories
This package is not used by any popular GitHub repositories.
| Version | Downloads | Last Updated |
|---|---|---|
| 1.8.0-alpha.9 | 0 | 6/25/2026 |
| 1.8.0-alpha.8 | 0 | 6/25/2026 |
| 1.8.0-alpha.4 | 6 | 6/25/2026 |
| 1.8.0-alpha.3 | 37 | 6/25/2026 |
| 1.8.0-alpha.2 | 36 | 6/25/2026 |
| 1.8.0-alpha.1 | 40 | 6/24/2026 |
| 1.7.1 | 66 | 6/23/2026 |
| 1.7.0 | 63 | 6/23/2026 |
| 1.6.2 | 66 | 6/23/2026 |
| 1.6.1 | 189 | 6/22/2026 |
| 1.6.0 | 73 | 6/22/2026 |
| 1.5.2 | 73 | 6/22/2026 |
| 1.4.0 | 78 | 6/21/2026 |
| 1.3.0 | 74 | 6/21/2026 |
| 1.2.0 | 67 | 6/21/2026 |
| 1.1.0 | 71 | 6/21/2026 |
| 1.0.1 | 74 | 6/21/2026 |
| 1.0.0 | 88 | 6/21/2026 |
StyloExtract 1.7.1 - 2026-06-23
================================
Patch release. One bug fix to DomMarkdownWalker so heavily-indented
source HTML (typical of Tailwind / HTMX / framework-generated markup)
stops producing markdown that CommonMark parses as indented code blocks.
Bug
---
* DomMarkdownWalker.AppendEscapedInline preserved leading whitespace at
line-start, so consecutive text-node visits each emitted a single
space and accumulated to 4+ spaces ahead of links and paragraphs.
CommonMark then parsed those lines as indented code blocks and the
resulting markdown rendered as raw `[text](href)` text instead of
clickable links. Now skipped at line-start; inner-paragraph whitespace
still collapses to single spaces as before.
Real-world repro: lucidVIEW loading mostlylucid.net (HTMX-driven blog
index). Before 1.7.1 every blog-post card after the first collapsed into
a code block; after 1.7.1 each card is a styled link with its summary
as its own paragraph beneath.
----
StyloExtract 1.7.0 - 2026-06-23
================================
Structured markdown output. Previously every classified block flattened
to element.TextContent.Trim() and the renderer emitted a wall of plain
paragraphs with "# " collapsing all six heading levels. This release
makes ExtractedBlock.Markdown carry a real GFM rendition produced by
walking the block's DOM subtree.
Highlights
----------
* Heading levels H1-H6 emit one-through-six "#" characters.
* Inline content preserved: links, **bold**, *italic*, `code`, images,
hard breaks.
* Lists, fenced code blocks (with language hint), blockquotes (single
and multi-paragraph following GFM convention), and figures all render
with their structure intact.
* GFM tables built from a WHATWG slot grid: colspan/rowspan respected,
caption rendered above as bold paragraph, alignment markers derived
from align attribute or style="text-align" via majority-vote, pipes
escaped, newlines converted to <br>. Complex tables (multi-row thead,
nested tables, block content in a cell) fall back to raw HTML which
CommonMark passes through.
* Sidebar and RelatedLinks now use the DOM walker. The classic "on this
page" TOC pattern renders as a proper markdown list with anchor links
instead of flattening to indented text.
Performance
-----------
Walker on Apple M5 / .NET 10, full pipeline numbers in parentheses:
Small article: 1.3 us / 8 KB (full pipeline: 370 us / 925 KB)
Medium doc : 25.2 us / 72 KB (full pipeline: 491 us / 823 KB)
Large doc : 34.1 us / 114 KB (full pipeline: 642 us / 843 KB)
Table-heavy : 69.2 us / 165 KB (full pipeline: 641 us / 688 KB)
Walker share of ExtractAsync total time fell from 25-55% to 5-11% across
the four scenarios. ExtractAsync continues to sit well under the spec's
15ms p99 budget on a cache hit.
Compatibility
-------------
Backwards-compatible. ExtractedBlock.Text continues to project the
flattened plain-text view unchanged; the new markdown rendition is read
via ExtractedBlock.Markdown. Existing extraction profiles behave
identically; the only observable change is that the markdown emitted by
TypedMarkdownRenderer is now reader-grade rather than flat prose.
Tests
-----
329 tests across 7 projects, all green. 51 unit tests on the new walker
cover inline composition, list and code rendering, and the full GFM
table reconstruction path including the complexity-detection fallback
to raw HTML. Four end-to-end pipeline tests exercise the spec's headline
gaps (heading levels, inline links, lists, GFM tables) through
parse -> clean -> segment -> classify -> render -> SQLite.
See CHANGELOG.md for the full record.