edfcore 0.6.66 → 0.6.68
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.
- package/dist/constants.d.ts +1 -1
- package/dist/constants.js +1 -1
- package/docs/CHANGELOG.md +29 -0
- package/package.json +1 -1
- package/src/constants.ts +1 -1
package/dist/constants.d.ts
CHANGED
|
@@ -109,5 +109,5 @@ export declare const SIGNAL_FIELD_BLOCK_OFFSETS: {
|
|
|
109
109
|
readonly reserved: 224;
|
|
110
110
|
};
|
|
111
111
|
/** Published package version. Kept in sync with package.json by a test. */
|
|
112
|
-
export declare const VERSION = "0.6.
|
|
112
|
+
export declare const VERSION = "0.6.68";
|
|
113
113
|
//# sourceMappingURL=constants.d.ts.map
|
package/dist/constants.js
CHANGED
package/docs/CHANGELOG.md
CHANGED
|
@@ -6,6 +6,35 @@ alone does not tell you whether you were affected.
|
|
|
6
6
|
edfcore is pre-1.0. Patch releases have carried behaviour changes where the old behaviour was a
|
|
7
7
|
defect; those are called out below.
|
|
8
8
|
|
|
9
|
+
## 0.6.68
|
|
10
|
+
|
|
11
|
+
- **Fixed** every docs page describing itself two ways at once. `og:type` said `website` while the
|
|
12
|
+
JSON-LD in the same head said `TechArticle`.
|
|
13
|
+
- `Base.astro` states the rule in its own props: structured data "must restate what is visible on
|
|
14
|
+
the page, never more", because data contradicting the page — schema drift — reads as spam to the
|
|
15
|
+
crawlers it exists for. The two disagreeing blocks were both emitted by that layout.
|
|
16
|
+
- `og:type` is a prop now, defaulting to `website`, and the docs route passes `article`. The
|
|
17
|
+
landing page, the inspector and the 404 keep `website`, which is what they are. The test reads
|
|
18
|
+
both values off the built site and parses the JSON-LD rather than pattern-matching it, so a page
|
|
19
|
+
that claims one kind and declares the other fails whichever half moved.
|
|
20
|
+
|
|
21
|
+
## 0.6.67
|
|
22
|
+
|
|
23
|
+
- **Added** `noindex, follow` to the 404 page, which was reachable as an ordinary indexable URL.
|
|
24
|
+
- The page exists for one reason and its own docblock states it: a crawler that gets a real 404
|
|
25
|
+
treats the URL as gone, while a site with no 404 route serves "a soft-200 that search engines
|
|
26
|
+
index as duplicate junk". Vercel does serve it with a 404 for a miss — and `cleanUrls` also
|
|
27
|
+
serves it at the extensionless `/404`, with a 200 and a canonical pointing at itself. That is a
|
|
28
|
+
soft 404 at a guessable URL, on the page written to avoid one.
|
|
29
|
+
- `follow` rather than `nofollow`: the three links on it are its whole purpose. The tag is an
|
|
30
|
+
opt-in prop on the layout and no other page passes it, which the test checks in both directions
|
|
31
|
+
against the built site — a page that started emitting `robots` by accident fails there.
|
|
32
|
+
|
|
33
|
+
The guard in `crawlability.test.ts` is narrowed rather than relaxed: the two files that may
|
|
34
|
+
mention the word are named, so a `noindex` in a component, in `index.astro`, or defaulted to
|
|
35
|
+
`true` in the layout all still fail it — which is the shape that would quietly de-index the site
|
|
36
|
+
and is what that file exists to catch.
|
|
37
|
+
|
|
9
38
|
## 0.6.66
|
|
10
39
|
|
|
11
40
|
- **Changed** the `Next:` clause of `STARTTIME_UNPARSEABLE` as the PARSER raises it, which left
|
package/package.json
CHANGED
package/src/constants.ts
CHANGED