edf2csv 0.6.61 → 0.6.63

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/docs/CHANGELOG.md +65 -0
  2. package/package.json +1 -1
package/docs/CHANGELOG.md CHANGED
@@ -3,6 +3,71 @@
3
3
  Notable changes to edf2csv. Versions follow [semantic versioning](https://semver.org); while the
4
4
  major version is 0, a minor bump may contain breaking changes.
5
5
 
6
+ ## 0.6.63
7
+
8
+ ### Fixed: phones could scroll the whole site sideways, and every heading faded in
9
+
10
+ Three grids collapse to a single column on narrow screens, and all three collapsed to `1fr`.
11
+ A plain `1fr` track has `min-width: auto`, so the one child with an unwrappable width — the
12
+ scope readout's 420px minimum on the landing page, a CSV sample's longest line in the docs —
13
+ set the track wider than the phone, and every element on the page shared one clipped right
14
+ edge with 26px of sideways scroll to find it. The two-column desktop layouts already used
15
+ `minmax(0, 1fr)` for exactly this reason; the single-column collapses now match them. The
16
+ code blocks scroll inside their own boxes, which was always the intent.
17
+
18
+ The scroll-reveal animation is gone. Every section's heading, lede and body used to fade
19
+ upward as the reader reached it, which was defended in the README as arriving "in reading
20
+ order" — but a page where every heading rises into place is indistinguishable from every
21
+ other page where every heading rises into place, and the pattern costs something real here:
22
+ the prerendered landing page shipped its text wrapped in inline `opacity: 0` until the bundle
23
+ arrived to animate it. Content is now simply present. Motion stays where it argues something
24
+ — the hero trace turning into rows, the 765 interpolated dots appearing out of nowhere — and
25
+ in interaction feedback. The hero's own entrance became three lines of CSS, which paint with
26
+ the HTML instead of after it.
27
+
28
+ Two smaller things. The documentation grid on the landing page held eleven cards in a
29
+ four-column grid, leaving a permanent empty cell; a twelfth card now points at
30
+ llms-full.txt, the whole documentation as one plain-text file for pasting into a coding
31
+ agent — a real destination this site already served without linking to it. And the footer
32
+ finally links the npm package, which no page on the site did.
33
+
34
+ ## 0.6.62
35
+
36
+ ### Changed: the homepage is real HTML, and a pasted link unfurls into something
37
+
38
+ Two findings from an SEO pass over the website, both the same shape: the site said less about
39
+ itself to machines than it does to people.
40
+
41
+ The documentation pages have been prerendered static HTML from the start, precisely so that
42
+ crawlers that do not run JavaScript — which is most of the AI crawlers the docs were written
43
+ for — get the full text. The landing page never got the same treatment: it was an empty
44
+ `<div id="root">` until the bundle arrived, so the one page that explains what the tool is was
45
+ blank to exactly the readers the prerendering exists for. It is now server-rendered at build
46
+ time through Vite's SSR transform and hydrated in the browser, and the build fails if the
47
+ rendered landing ever comes back as a stub, the same check the documentation pages have.
48
+
49
+ A pasted link had no image at all: `twitter:card` said `summary` and no `og:image` existed, so
50
+ Slack, iMessage and the rest unfurled the URL into two lines of grey text. There is now a
51
+ 1200x630 card in the site's own oscilloscope idiom — the H1, the command, a trace — referenced
52
+ with `summary_large_image` from every page. One committed PNG rather than a per-page generator,
53
+ because eleven near-identical title cards would say less than one good one.
54
+
55
+ The smaller corrections follow the same principle. The sitemap dropped `<priority>`, which
56
+ Google states it ignores, for `<lastmod>` read from each page's commit history — and a page
57
+ whose date git cannot supply gets no tag, because a fabricated date teaches crawlers to
58
+ distrust all of them. The title now leads with the phrase people type ("Convert EDF to CSV
59
+ from the command line") while the H1 keeps the site's own voice. Documentation pages carry
60
+ BreadcrumbList and a `dateModified` from the same commit history; the SoftwareApplication
61
+ entity gained `sameAs` links tying the site, the repository and the npm package into one
62
+ thing, and a `softwareVersion` read from package.json at build. It still carries no
63
+ aggregateRating and no download count: the schema for star ratings is the one piece of SEO
64
+ this site will not do, because inventing social proof is fabricating data on a site whose
65
+ argument is that fabricating data is the problem.
66
+
67
+ Also fixed on the way through: the landing page never inlined the theme-restore script the
68
+ documentation pages have, so a reader who had chosen light mode got a flash of dark on every
69
+ visit to the homepage.
70
+
6
71
  ## 0.6.61
7
72
 
8
73
  ### Added: the pyEDFlib cross-check runs weekly instead of never
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "edf2csv",
3
- "version": "0.6.61",
3
+ "version": "0.6.63",
4
4
  "description": "Convert EDF, EDF+ and BDF biosignal recordings (European Data Format) to CSV from the command line. Local, streaming, and never resamples or alters units.",
5
5
  "keywords": [
6
6
  "edf",