@moorage/plugin-site-health 0.1.0 → 0.1.1
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/CHANGELOG.md +7 -0
- package/README.md +2 -0
- package/dist/index.mjs +1 -1
- package/dist/manifest.json +1 -1
- package/listing/faq.md +1 -1
- package/package.json +4 -4
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,12 @@
|
|
|
1
1
|
# @moorage/plugin-site-health
|
|
2
2
|
|
|
3
|
+
## 0.1.1
|
|
4
|
+
|
|
5
|
+
### Patch Changes
|
|
6
|
+
|
|
7
|
+
- dde14f2: Listing FAQ: "My site is not public yet. Does it work?" now says exactly what is checked before the site can open its own pages (links to your pages and posts at once; other addresses on your site, menus, page errors and the Checklist once it has a public address). No code change.
|
|
8
|
+
- 4586179: README: on Cloudflare's Workers free plan a save or publish can now and then fail with "Worker exceeded resource limits" (about 10 ms of CPU per request, which EmDash's own saving already comes close to); trying again works, and Workers Paid does not have this problem. No code change.
|
|
9
|
+
|
|
3
10
|
## 0.1.0
|
|
4
11
|
|
|
5
12
|
### Minor Changes
|
package/README.md
CHANGED
|
@@ -64,6 +64,8 @@ emdash({ sandboxed: [siteHealth] });
|
|
|
64
64
|
|
|
65
65
|
On a site without a sandbox runner (the Workers free plan), list it under `plugins: [siteHealth]` instead. It works the same.
|
|
66
66
|
|
|
67
|
+
**On Cloudflare's Workers free plan** each request gets about 10 ms of CPU. EmDash's own saving and publishing already comes close to that, and every plugin run in the site's process adds a little, so a save or publish can now and then fail with "Worker exceeded resource limits"; trying again works. Workers Paid (30 seconds per request) does not have this problem.
|
|
68
|
+
|
|
67
69
|
Then open **Tools > Site Health** in the admin sidebar.
|
|
68
70
|
|
|
69
71
|
**Permissions it asks for:**
|
package/dist/index.mjs
CHANGED
package/dist/manifest.json
CHANGED
package/listing/faq.md
CHANGED
|
@@ -16,7 +16,7 @@ Not yet. For an address on your own site, "Send visitors to another page" fixes
|
|
|
16
16
|
|
|
17
17
|
### My site is not public yet. Does it work?
|
|
18
18
|
|
|
19
|
-
Links inside your pages
|
|
19
|
+
Partly. Links inside your pages that point to one of your pages or posts are checked straight away, and a link to a page that is not published yet shows as broken. Links to any other address on your own site, the menus, page errors and the Checklist need the site to open its own pages, so they wait until it has a public address; until then those links are listed under "Links we could not check", never as broken.
|
|
20
20
|
|
|
21
21
|
### Who gets the emails?
|
|
22
22
|
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@moorage/plugin-site-health",
|
|
3
|
-
"version": "0.1.
|
|
3
|
+
"version": "0.1.1",
|
|
4
4
|
"description": "Site Health for EmDash: a broken link checker for your pages, menus and links to other sites, with email alerts and a setup checklist.",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"emdash",
|
|
@@ -47,11 +47,11 @@
|
|
|
47
47
|
"emdash": ">=1.3.0"
|
|
48
48
|
},
|
|
49
49
|
"devDependencies": {
|
|
50
|
-
"@emdash-cms/blocks": "1.3.
|
|
50
|
+
"@emdash-cms/blocks": "1.3.1",
|
|
51
51
|
"@emdash-cms/plugin-cli": "0.13.4",
|
|
52
|
-
"@emdash-cms/plugin-test": "0.2.
|
|
52
|
+
"@emdash-cms/plugin-test": "0.2.10",
|
|
53
53
|
"@moorage/typescript-config": "0.0.0",
|
|
54
|
-
"emdash": "1.3.
|
|
54
|
+
"emdash": "1.3.1",
|
|
55
55
|
"typescript": "~6.0.3",
|
|
56
56
|
"vitest": "4.1.10"
|
|
57
57
|
},
|