theseus/addon-build/docx-editor/package.json
Local Dev 4af11d28fb chore(docx-editor): first-party update channel, not the community catalogue
This is our own extension, so it belongs on the channel the operator key
signs — theseus.x/extensions/docx-editor/ — alongside screenshot, aegis and
pdf-editor. The community catalogue is for extensions published by whoever
owns a BNS name, and routing ours through it would have meant asking a name
owner to vouch for code we wrote.

Drops the community packing script: with one channel there is one publish
path, and it is the one already written down in docs/ADDON-UPDATES.md.

Worth stating plainly, because it is currently true and awkward: Settings
can only *install* from the community catalogue. An extension that is
neither bundled nor catalogued has a working update channel and no way for
anyone to get the first copy. Either it goes back into the build or it needs
a first-party entry point.
2026-09-21 22:28:30 +02:00

30 lines
928 B
JSON

{
"name": "docx-editor-vendor-build",
"private": true,
"version": "0.0.0",
"description": "Build-time only: bundles mammoth + ProseMirror + docx into extensions/docx-editor/vendor/, and rasterises the icon.",
"type": "module",
"scripts": {
"build": "node build.mjs",
"icons": "node make-icons.mjs"
},
"devDependencies": {
"docx": "^9.5.1",
"esbuild": "^0.28.2",
"jsdom": "^29.1.1",
"jszip": "^3.10.1",
"mammoth": "^1.12.3",
"prosemirror-commands": "^1.7.1",
"prosemirror-dropcursor": "^1.8.2",
"prosemirror-gapcursor": "^1.3.2",
"prosemirror-history": "^1.4.1",
"prosemirror-inputrules": "^1.5.0",
"prosemirror-keymap": "^1.2.3",
"prosemirror-model": "^1.25.0",
"prosemirror-schema-basic": "^1.2.4",
"prosemirror-schema-list": "^1.5.1",
"prosemirror-state": "^1.4.3",
"prosemirror-tables": "^1.7.1",
"prosemirror-view": "^1.40.0"
}
}