npm bugs @reviseio/sdk opens the
same route.
Response times, escalation paths, and any service commitments are part of your
licence agreement rather than this page — talk to us about your requirements
and we will put them in writing.
What to include
The SDK reports its own identity. Attaching it turns “the editor broke” into something reproducible:- What you did, in the order you did it. “Opened a .docx with tracked changes, accepted the second one, exported” beats “accept is broken”.
- The document, if you can share it. Fidelity bugs are almost always specific to a file, and a redacted copy that still reproduces is worth more than a description.
- Browser and version, and whether it reproduces in another.
- Anything in the console, including warnings before the error.
Before you write
A few problems have well-known causes and a faster fix than a support round trip:Unexpected content type in insert operation
Unexpected content type in insert operation
Two copies of Yjs. It identifies its own types with
instanceof, so a
shared document rejects nodes built by the other copy. npm ls yjs should
show exactly one. See collaboration.Revise document … is still opening
Revise document … is still opening
The handle was used before a document existed.
onReady fires before the
first document opens — subscriptions are safe to place immediately, but
anything that acts on a document needs onDocumentReady or
await editor.whenReady().A move came back as a delete plus an insert
A move came back as a delete plus an insert
Expected. Word records a move as a linked
moveFrom/moveTo pair; we
record the same edit as a deletion and an insertion, which Word reads
correctly but does not label as a move. See tracked
changes for exactly what survives the round trip.404 installing the package
404 installing the package
npm reports private packages you cannot see as 404 rather than 403. The
scope is not routed, or the token is not being read — see
access.