5e4bd22609
A .docx editor is a megabyte of vendored library. Bundling it would charge that to everyone who wanted a browser, including the people who will never open a Word document in it. So it leaves the build: out of bundled-addons/, out of extraResources, absent from a fresh profile. It arrives the way anyone else's extension does — Settings › Extensions › Community, from the catalogue the gateway builds, and listed on theseus.x/extensions alongside everything else published there. That also means it is signed by the owner of a BNS name rather than by the operator key, which is the right trust story for something that isn't part of the browser. `npm run pack` produces the tarball the publish page takes; the signature needs the publisher name's wallet, so it isn't something the repo can do. The end-to-end test now installs the extension into a throwaway profile the way the community installer would, and asserts up front that a fresh profile doesn't already have it — the bundling is what was being removed, so it is worth a test that would notice it coming back.
10 lines
326 B
Text
10 lines
326 B
Text
# The patched copy of mammoth is regenerated by `npm run build`; the patches
|
|
# themselves (patches.mjs) are the source of truth and are checked in.
|
|
.patched/
|
|
|
|
# Test scratch — regenerate with test/fixture.mjs and test/roundtrip.mjs.
|
|
test/fixture.docx
|
|
test/roundtrip-out.docx
|
|
test/roundtrip-a.json
|
|
test/roundtrip-b.json
|
|
out/
|