{
  "version": 3,
  "sources": ["../src/index.ts"],
  "sourcesContent": ["/**\n * Yjs should not be considered a public API. It is a third-party library that\n * _will_ experience breaking changes in the future. However, in order to allow\n * third-party plugins to provide their own Yjs providers / sync transport, they\n * must import and consume **our instance** of Yjs due to this bug / feature:\n *\n * https://github.com/yjs/yjs/issues/438\n *\n * In other words, external code must be able to import Yjs from the\n * `@wordpress/sync` package in their code, e.g.:\n *\n * ```ts\n * import { Y } from '@wordpress/sync';\n * ```\n *\n * Additionally, this import must resolve to `wp.sync` via `DependencyExtractionWebpackPlugin`.\n * If you are using an older version of `@wordpress/scripts` that does not treat\n * `@wordpress/sync` as an unbundled package, then you can use Webpack externals\n * to manually resolve the package to the global `wp.sync` variable:\n *\n * ```ts\n * externals: {\n *   ...existingConfig.externals,\n *   // Resolve @wordpress/sync to the global `wp.sync` provided by WordPress.\n *   '@wordpress/sync': 'wp.sync',\n *\n *   // Resolve Yjs to the global `wp.sync.Y` provided by the sync package.\n *   // Since dependencies import 'yjs' directly, we need to avoid importing\n *   // and packaging two different Yjs instances, which would result in this\n *   // conflict:\n *   //\n *   // https://github.com/yjs/yjs/issues/438\n *   yjs: 'wp.sync.Y',\n * },\n * ```\n */\nexport * as Y from 'yjs';\n\n/**\n * The major version of Yjs that is bundled and exported by this package. This\n * can be used by third-party code to ensure that they are targeting a compatible\n * version of Yjs.\n */\nexport const YJS_VERSION = '13';\n\n/**\n * The Awareness protocol should not be considered a public API. It is a\n * third-party library that will experience breaking changes in the future.\n *\n * In general, awareness for core entity types is implemented by the `core-data`\n * package and third-party Yjs providers should not provide their own awareness\n * implementation. However, it may be desirable for custom entities to have a\n * custom awareness implementation.\n */\nexport { Awareness } from 'y-protocols/awareness';\n\n/**\n * Private @wordpress/sync APIs.\n */\nexport { privateApis } from './private-apis';\n\nexport type * from './types';\n"],
  "mappings": ";AAoCA,YAAY,OAAO;AAkBnB,SAAS,iBAAiB;AAK1B,SAAS,mBAAmB;AAhBrB,IAAM,cAAc;",
  "names": []
}