{"version":3,"sources":["jsdelivr-header.js","/npm/@automerge/automerge-repo@2.5.3/dist/index.js"],"names":[],"mappings":"AAAA;AACA;AACA;AACA;AACA;AACA;AACA,OCqBS,cAAiB,wBACjB,oBAAqB,kBAAmB,kBAAmB,sBAAuB,sBAAuB,mBAAoB,qBAAsB,YAAa,gBAAoB,2BACpL,SAAY,mBACZ,aAAgB,gCAChB,kBAAqB,qCACrB,mBAAsB,qCACtB,kBAAqB,+BACrB,mBAAsB,6CACd,cAAiB,kCAEjB,aAAK,0BACb,KAAK,oBACL,OAAQ,QAAS,WAAY,kBAAqB,yBAgBpD,MAAM,QAAU,UAAU,eAC1B,MAAM,UAAY,UAAU,iBAE5B,MAAM,gBAAkB,UAAU,iBAGlC,MAAM,WAAa,UAAU,kBAC7B,MAAM,cAAgB,UAAU,qBAChC,MAAM,aAAe,UAAU,oBAC/B,MAAM,KAAO,UAAU,YACvB,MAAM,aAAe,UAAU,oBAI/B,MAAM,UAAY,UAAU,iBAC5B,MAAM,kBAAoB,UAAU,yBACpC,MAAM,OAAS,UAAU,cACzB,MAAM,WAAa,UAAU,kBAC7B,MAAM,SAAW,UAAU,gBAC3B,MAAM,SAAW,UAAU,gBAC3B,MAAM,KAAO,UAAU,YACvB,MAAM,OAAS,UAAU,cACzB,MAAM,YAAc,UAAU,mBAE9B,MAAM,kBAAoB,UAAU,mBACpC,MAAM,YAAc,UAAU","file":"/npm/@automerge/automerge-repo@2.5.3/dist/index.js","sourceRoot":"","sourcesContent":["/**\n * Minified by jsDelivr using Terser v5.39.0.\n * Original file: /npm/@automerge/automerge-repo@2.5.3/dist/index.js\n *\n * Do NOT use SRI with dynamically generated files! More information: https://www.jsdelivr.com/using-sri-with-dynamic-files\n */\n","/**\n * @packageDocumentation\n *\n * The [`automerge`](https://www.npmjs.com/package/@automerge/automerge) CRDT\n * provides a core CRDT data structure and an implementation of a storage\n * format and sync protocol but doesn't provide the plumbing to use these tools\n * in a JS application. `automerge-repo` provides the plumbing.\n *\n * The main entry point is the {@link Repo} class, which you instantiate with\n * a {@link StorageAdapter} and zero or more {@link NetworkAdapter}s. Once you\n * have a repo you can use it to create {@link DocHandle}s. {@link DocHandle}s\n * are a reference to a document, identified by a {@link AutomergeUrl}, a place to\n * listen for changes to the document, and to make new changes.\n *\n * A typical example of how to use this library then might look like this:\n *\n * ```typescript\n * import { Repo } from \"@automerge/automerge-repo\";\n *\n * const repo = new Repo({\n *   storage: <storage adapter>,\n *   network: [<network adapter>, <network adapter>]\n * })\n *\n * const handle = repo.create\n * ```\n */\nexport { DocHandle } from \"./DocHandle.js\";\nexport { isValidAutomergeUrl, isValidDocumentId, parseAutomergeUrl, stringifyAutomergeUrl, interpretAsDocumentId, documentIdToBinary, generateAutomergeUrl, encodeHeads, decodeHeads, } from \"./AutomergeUrl.js\";\nexport { Repo } from \"./Repo.js\";\nexport { Presence } from \"./presence/Presence.js\";\nexport { PeerStateView } from \"./presence/PeerStateView.js\";\nexport { NetworkAdapter } from \"./network/NetworkAdapter.js\";\nexport { isRepoMessage } from \"./network/messages.js\";\nexport { StorageAdapter } from \"./storage/StorageAdapter.js\";\nimport { next as Automerge } from \"@automerge/automerge/slim\";\n/** @hidden **/\nexport * as cbor from \"./helpers/cbor.js\";\nexport * from \"./types.js\";\nexport { cursor, findRef, refFromUrl, refFromString } from \"./refs/utils.js\";\n// Automerge re-exports\n//\n// Note that we can't use export type { .. } from \"@automerge/automerge\" because we are\n// importing automerge like this:\n//\n// import { next as Automerge } from \"@automerge/automerge\"\n//\n// I.e. we are using the `next` export from Automerge. Not the module itself. This is\n// to maintain compatiblity with Automerge 3.0 and 2.0. In 2.0 we used to have a\n// subpath export at `/next` so the re-exports looked like this:\n//\n// export { type .. } from \"@automerge/automerge/slim/next\"\n//\n// However, we have now removed the subpath export (and deprecated next generally)\n// so we need to explicitly name each type we are re-exporting here.\nexport const Counter = Automerge.Counter;\nexport const RawString = Automerge.RawString;\n// In automerge 3.0 RawString is renamed to ImmutableString\nexport const ImmutableString = Automerge.RawString;\n// export a few utility functions that aren't in automerge-repo\n// NB that these should probably all just be available via the dochandle\nexport const getChanges = Automerge.getChanges;\nexport const getAllChanges = Automerge.getAllChanges;\nexport const applyChanges = Automerge.applyChanges;\nexport const view = Automerge.view;\nexport const getConflicts = Automerge.getConflicts;\n// export type-specific utility functions\n// these mostly can't be on the data-type in question because\n// JS strings can't have methods added to them\nexport const getCursor = Automerge.getCursor;\nexport const getCursorPosition = Automerge.getCursorPosition;\nexport const splice = Automerge.splice;\nexport const updateText = Automerge.updateText;\nexport const insertAt = Automerge.insertAt;\nexport const deleteAt = Automerge.deleteAt;\nexport const mark = Automerge.mark;\nexport const unmark = Automerge.unmark;\nexport const isRawString = Automerge.isRawString;\n// In Automerge 3.0 raw string is renamed to immutable string\nexport const isImmutableString = Automerge.isRawString;\nexport const getObjectId = Automerge.getObjectId;\n"]}