@minnovate/shadow-publisher 0.14.0 → 0.14.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.
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "git-publisher",
|
|
3
3
|
"displayName": "Git Publisher",
|
|
4
|
-
"version": "0.14.
|
|
4
|
+
"version": "0.14.1",
|
|
5
5
|
"description": "Publish an app folder's Git history to the serverless Git publishing backend and keep it updated (\"publish my app\", \"update my app\", \"fetch the engineered version\").",
|
|
6
6
|
"author": { "name": "git-publisher project" },
|
|
7
7
|
"keywords": ["git", "publish", "deploy", "serverless"]
|
|
@@ -29,7 +29,7 @@ publisher --version
|
|
|
29
29
|
```
|
|
30
30
|
|
|
31
31
|
If the command is not found, or the version is older than 0.11.0, install it:
|
|
32
|
-
`npm install -g @minnovate/shadow-publisher@latest` (it needs Node.js 22). In a Claude Cowork task
|
|
32
|
+
`npm install -g @minnovate/shadow-publisher@latest` (it needs Node.js 22.12 or a later 22). In a Claude Cowork task
|
|
33
33
|
this is normal: the sandbox starts empty every time, so install it without asking. On the person's
|
|
34
34
|
own computer, say in one line that you are installing the publisher. If `npm` itself is missing,
|
|
35
35
|
tell them Node.js 22 must be installed first, and stop.
|
|
@@ -142,6 +142,13 @@ in its folder. The checks refuse an app that does not (see "When the checks find
|
|
|
142
142
|
Keep it small too: each file at most 4 MB, the whole app at most 10 MB, at most 500 files —
|
|
143
143
|
a larger app is refused before it is checked, and the refusal names the file or the limit it broke.
|
|
144
144
|
|
|
145
|
+
An app is one folder in one of three shapes: static files with `index.html` at the root, a
|
|
146
|
+
standard-library Python `app.py`, or a Node.js `server.mjs` beside a `package.json` of exactly
|
|
147
|
+
`{"type":"module","scripts":{"start":"node server.mjs"}}`. It has no build step and no npm or pip
|
|
148
|
+
dependencies. Only .html .js .mjs .py .css .csv .json .svg .txt files are part of the app: any
|
|
149
|
+
other file, such as an image, an icon or a font, is left out, so draw images as SVG and use system
|
|
150
|
+
font stacks.
|
|
151
|
+
|
|
145
152
|
## 4. Telling them how it goes, step by step
|
|
146
153
|
|
|
147
154
|
After a publish, the app goes through four steps: **received**, **checked**, **going live**,
|
|
@@ -214,8 +221,8 @@ sentence, and `progress.next.action` is `"fix"`. Then:
|
|
|
214
221
|
2. Fix every finding in the app folder, by its `kind`:
|
|
215
222
|
- `external-resource`: the app loads `url` from another site (a CDN script, Google Fonts, an
|
|
216
223
|
image). **Apps may not load anything from other sites.** Download the file into the app
|
|
217
|
-
folder and point to it with a relative path
|
|
218
|
-
|
|
224
|
+
folder and point to it with a relative path, if it is at most 4 MB (a charting library
|
|
225
|
+
such as Chart.js, about 200 KB, fits). Otherwise replace it with code of your own: a
|
|
219
226
|
font falls back to a system font stack, a chart is drawn as inline SVG. Never keep the
|
|
220
227
|
external address.
|
|
221
228
|
- `console-error` / `application-error`: fix the code that logs or throws `message`.
|