@ember-data/store 5.9.0-alpha.21 → 5.9.0-alpha.22

package/dist/-private.d.ts

@@ -0,0 +1 @@
+export * from "@warp-drive/core/store/-private";

package/dist/-private.js

@@ -1 +1 @@
-export * from '@warp-drive/core/store/-private';
+export * from "@warp-drive/core/store/-private"

package/dist/configure.d.ts

@@ -0,0 +1,2 @@
+import { setupSignals } from "@warp-drive/core/configure";
+export { setupSignals };

package/dist/configure.js

@@ -1 +1,3 @@
-export { setupSignals } from '@warp-drive/core/configure';
+import { setupSignals } from "@warp-drive/core/configure";
+
+export { setupSignals };

package/dist/index.d.ts

@@ -0,0 +1,2 @@
+import { CacheHandler, CacheOperation, CachePolicy, Document, DocumentCacheOperation, NotificationType, Store, StoreRequestContext, StoreRequestInput, recordIdentifierFor, setIdentifierForgetMethod, setIdentifierGenerationMethod, setIdentifierResetMethod, setIdentifierUpdateMethod, setKeyInfoForResource, storeFor } from "@warp-drive/core";
+export { CacheHandler, type CacheOperation, type CachePolicy, type Document, type DocumentCacheOperation, type NotificationType, type StoreRequestContext, type StoreRequestInput, Store as default, recordIdentifierFor, setIdentifierForgetMethod, setIdentifierGenerationMethod, setIdentifierResetMethod, setIdentifierUpdateMethod, setKeyInfoForResource, storeFor };

package/dist/index.js

@@ -1,196 +1,220 @@
-import { deprecate } from '@ember/debug';
-import { macroCondition, getGlobalConfig, dependencySatisfies, importSync } from '@embroider/macros';
-export { CacheHandler, Store as default, recordIdentifierFor, setIdentifierForgetMethod, setIdentifierGenerationMethod, setIdentifierResetMethod, setIdentifierUpdateMethod, setKeyInfoForResource, storeFor } from '@warp-drive/core';
-import { setupSignals } from '@warp-drive/core/configure';
-import { peekTransient } from '@warp-drive/core/types/-private';
+import { deprecate } from "@ember/debug";
+import { dependencySatisfies, getGlobalConfig, importSync, macroCondition } from "@embroider/macros";
+import { CacheHandler, Store, recordIdentifierFor, setIdentifierForgetMethod, setIdentifierGenerationMethod, setIdentifierResetMethod, setIdentifierUpdateMethod, setKeyInfoForResource, storeFor } from "@warp-drive/core";
+import { setupSignals } from "@warp-drive/core/configure";
+import { peekTransient } from "@warp-drive/core/types/-private";
 
+//#region src/index.ts
 /**
- * This package provides [*Ember***Data**](https://github.com/warp-drive-data/warp-drive/)'s `Store` class.
- *
- * A {@link Store} coordinates interaction between your application, a {@link Cache},
- * and sources of data (such as your API or a local persistence layer) accessed via a {@link RequestManager}.
- *
- * Optionally, a Store can be configured to hydrate the response data into rich presentation classes.
- *
- * ## 🔨 Creating A Store
- *
- * To use a `Store` we will need to do few things: add a {@link Cache}
- * to store data **in-memory**, add a {@link Handler} to fetch data from a source,
- * and implement `instantiateRecord` to tell the store how to display the data for individual resources.
- *
- * > **Note**
- * > If you are using the package `ember-data` then a JSON:API cache, RequestManager, LegacyNetworkHandler,
- * > and `instantiateRecord` are configured for you by default.
- *
- * ### Configuring A Cache
- *
- * To start, let's install a [JSON:API](https://jsonapi.org/) cache. If your app uses `GraphQL` or `REST` other
- * caches may better fit your data. You can author your own cache by creating one that
- * conforms to the {@link Cache | spec}.
- *
- * The package `@ember-data/json-api` provides a [JSON:API](https://jsonapi.org/) cache we can use.
- * After installing it, we can configure the store to use this cache.
- *
- * ```js
- * import Store from '@ember-data/store';
- * import Cache from '@ember-data/json-api';
- *
- * class extends Store {
- *   createCache(storeWrapper) {
- *     return new Cache(storeWrapper);
- *   }
- * }
- * ```
- *
- * Now that we have a `cache` let's setup something to handle fetching
- * and saving data via our API.
- *
- * > **Note**
- * > The `ember-data` package automatically includes and configures
- * > the `@ember-data/json-api` cache for you.
- *
- * ### Handling Requests
- *
- * When *Ember***Data** needs to fetch or save data it will pass that request to your application's `RequestManager` for fulfillment. How this fulfillment occurs (in-memory, device storage, via single or multiple API requests, etc.) is then up to the registered request handlers.
- *
- * To start, let's install the `RequestManager` from `@ember-data/request` and the basic `Fetch` handler from ``@ember-data/request/fetch`.
- *
- * > **Note**
- * > If your app uses `GraphQL`, `REST` or different conventions for `JSON:API` than your cache expects, other handlers may better fit your data. You can author your own handler by creating one that conforms to the [handler interface](https://github.com/warp-drive-data/warp-drive/tree/main/packages/request#handling-requests).
- *
- * ```ts
- * import Store from '@ember-data/store';
- * import RequestManager from '@ember-data/request';
- * import Fetch from '@ember-data/request/fetch';
- *
- * export default class extends Store {
- *   requestManager = new RequestManager()
- *    .use([Fetch]);
- * }
- * ```
- *
- * **Using RequestManager as a Service**
- *
- * Alternatively if you have configured the `RequestManager` to be a service you may re-use it.
- *
- * *app/services/request.js*
- * ```ts
- * import RequestManager from '@ember-data/request';
- * import Fetch from '@ember-data/request/fetch';
- *
- * export default {
- *   create() {
- *     return new RequestManager()
- *       .use([Fetch])
- *       .useCache(CacheHandler);
- *   }
- * }
- * ```
- *
- * *app/services/store.js*
- * ```ts
- * import Store from '@ember-data/store';
- * import { service } from '@ember/service';
- *
- * export default class extends Store {
- *   @service('request') requestManager
- * }
- * ```
- *
- *
- * ### Presenting Data from the Cache
- *
- * Now that we have a source and a cache for our data, we need to configure how
- * the Store delivers that data back to our application. We do this via the {@link Store.instantiateRecord | instantiateRecord hook}
- * which allows us to transform the data for a resource before handing it to the application.
- *
- * A naive way to present the data would be to return it as JSON. Typically instead
- * this hook will be used to add reactivity and make each unique resource a singleton,
- * ensuring that if the cache updates our presented data will reflect the new state.
- *
- * Below is an example of using the hooks `instantiateRecord` and a `teardownRecord`
- * to provide minimal read-only reactive state for simple resources.
- *
- * ```ts
- * import Store, { recordIdentifierFor } from '@ember-data/store';
- * import { TrackedObject } from 'tracked-built-ins';
- *
- * class extends Store {
- *   instantiateRecord(identifier) {
- *     const { cache, notifications } = this;
- *
- *     // create a TrackedObject with our attributes, id and type
- *     const record = new TrackedObject(Object.assign({}, cache.peek(identifier)));
- *     record.type = identifier.type;
- *     record.id = identifier.id;
- *
- *     notifications.subscribe(identifier, (_, change) => {
- *       if (change === 'attributes') {
- *         Object.assign(record, cache.peek(identifier));
- *       }
- *     });
- *
- *     return record;
- *   }
- * }
- * ```
- *
- * Because `instantiateRecord` is opaque to the nature of the record, an implementation
- * can be anything from a fairly simple object to a robust proxy that intelligently links
- * together associated records through relationships.
- *
- * This also enables creating a record that separates `edit` flows from `create` flows
- * entirely. A record class might choose to implement a `checkout`method that gives access
- * to an editable instance while the primary record continues to be read-only and reflect
- * only persisted (non-mutated) state.
- *
- * Typically you will choose an existing record implementation such as `@ember-data/model`
- * for your application.
- *
- * Because of the boundaries around instantiation and the cache, record implementations
- * should be capable of interop both with each other and with any `Cache`. Due to this,
- * if needed an application can utilize multiple record implementations and multiple cache
- * implementations either to support enhanced features for only a subset of records or to
- * be able to incrementally migrate from one record/cache to another record or cache.
- *
- * > **Note**
- * > The `ember-data` package automatically includes the `@ember-data/model`
- * > package and configures it for you.
- *
- * @module
- */
+* This package provides [*Ember***Data**](https://github.com/warp-drive-data/warp-drive/)'s `Store` class.
+*
+* A {@link Store} coordinates interaction between your application, a {@link Cache},
+* and sources of data (such as your API or a local persistence layer) accessed via a {@link RequestManager}.
+*
+* Optionally, a Store can be configured to hydrate the response data into rich presentation classes.
+*
+* ## 🔨 Creating A Store
+*
+* To use a `Store` we will need to do few things: add a {@link Cache}
+* to store data **in-memory**, add a {@link Handler} to fetch data from a source,
+* and implement `instantiateRecord` to tell the store how to display the data for individual resources.
+*
+* > **Note**
+* > If you are using the package `ember-data` then a JSON:API cache, RequestManager, LegacyNetworkHandler,
+* > and `instantiateRecord` are configured for you by default.
+*
+* ### Configuring A Cache
+*
+* To start, let's install a [JSON:API](https://jsonapi.org/) cache. If your app uses `GraphQL` or `REST` other
+* caches may better fit your data. You can author your own cache by creating one that
+* conforms to the {@link Cache | spec}.
+*
+* The package `@ember-data/json-api` provides a [JSON:API](https://jsonapi.org/) cache we can use.
+* After installing it, we can configure the store to use this cache.
+*
+* ```js
+* import Store from '@ember-data/store';
+* import Cache from '@ember-data/json-api';
+*
+* class extends Store {
+*   createCache(storeWrapper) {
+*     return new Cache(storeWrapper);
+*   }
+* }
+* ```
+*
+* Now that we have a `cache` let's setup something to handle fetching
+* and saving data via our API.
+*
+* > **Note**
+* > The `ember-data` package automatically includes and configures
+* > the `@ember-data/json-api` cache for you.
+*
+* ### Handling Requests
+*
+* When *Ember***Data** needs to fetch or save data it will pass that request to your application's `RequestManager` for fulfillment. How this fulfillment occurs (in-memory, device storage, via single or multiple API requests, etc.) is then up to the registered request handlers.
+*
+* To start, let's install the `RequestManager` from `@ember-data/request` and the basic `Fetch` handler from ``@ember-data/request/fetch`.
+*
+* > **Note**
+* > If your app uses `GraphQL`, `REST` or different conventions for `JSON:API` than your cache expects, other handlers may better fit your data. You can author your own handler by creating one that conforms to the [handler interface](https://github.com/warp-drive-data/warp-drive/tree/main/packages/request#handling-requests).
+*
+* ```ts
+* import Store from '@ember-data/store';
+* import RequestManager from '@ember-data/request';
+* import Fetch from '@ember-data/request/fetch';
+*
+* export default class extends Store {
+*   requestManager = new RequestManager()
+*    .use([Fetch]);
+* }
+* ```
+*
+* **Using RequestManager as a Service**
+*
+* Alternatively if you have configured the `RequestManager` to be a service you may re-use it.
+*
+* *app/services/request.js*
+* ```ts
+* import RequestManager from '@ember-data/request';
+* import Fetch from '@ember-data/request/fetch';
+*
+* export default {
+*   create() {
+*     return new RequestManager()
+*       .use([Fetch])
+*       .useCache(CacheHandler);
+*   }
+* }
+* ```
+*
+* *app/services/store.js*
+* ```ts
+* import Store from '@ember-data/store';
+* import { service } from '@ember/service';
+*
+* export default class extends Store {
+*   @service('request') requestManager
+* }
+* ```
+*
+*
+* ### Presenting Data from the Cache
+*
+* Now that we have a source and a cache for our data, we need to configure how
+* the Store delivers that data back to our application. We do this via the {@link Store.instantiateRecord | instantiateRecord hook}
+* which allows us to transform the data for a resource before handing it to the application.
+*
+* A naive way to present the data would be to return it as JSON. Typically instead
+* this hook will be used to add reactivity and make each unique resource a singleton,
+* ensuring that if the cache updates our presented data will reflect the new state.
+*
+* Below is an example of using the hooks `instantiateRecord` and a `teardownRecord`
+* to provide minimal read-only reactive state for simple resources.
+*
+* ```ts
+* import Store, { recordIdentifierFor } from '@ember-data/store';
+* import { TrackedObject } from 'tracked-built-ins';
+*
+* class extends Store {
+*   instantiateRecord(identifier) {
+*     const { cache, notifications } = this;
+*
+*     // create a TrackedObject with our attributes, id and type
+*     const record = new TrackedObject(Object.assign({}, cache.peek(identifier)));
+*     record.type = identifier.type;
+*     record.id = identifier.id;
+*
+*     notifications.subscribe(identifier, (_, change) => {
+*       if (change === 'attributes') {
+*         Object.assign(record, cache.peek(identifier));
+*       }
+*     });
+*
+*     return record;
+*   }
+* }
+* ```
+*
+* Because `instantiateRecord` is opaque to the nature of the record, an implementation
+* can be anything from a fairly simple object to a robust proxy that intelligently links
+* together associated records through relationships.
+*
+* This also enables creating a record that separates `edit` flows from `create` flows
+* entirely. A record class might choose to implement a `checkout`method that gives access
+* to an editable instance while the primary record continues to be read-only and reflect
+* only persisted (non-mutated) state.
+*
+* Typically you will choose an existing record implementation such as `@ember-data/model`
+* for your application.
+*
+* Because of the boundaries around instantiation and the cache, record implementations
+* should be capable of interop both with each other and with any `Cache`. Due to this,
+* if needed an application can utilize multiple record implementations and multiple cache
+* implementations either to support enhanced features for only a subset of records or to
+* be able to incrementally migrate from one record/cache to another record or cache.
+*
+* > **Note**
+* > The `ember-data` package automatically includes the `@ember-data/model`
+* > package and configures it for you.
+*
+* @module
+*/
 if (macroCondition(getGlobalConfig().WarpDrive.deprecations.DEPRECATE_TRACKING_PACKAGE)) {
-  let hasEmberDataTracking = false;
-  let hasWarpDriveEmber = false;
-  let hasRegisteredFromEmberPackage = false;
-  if (macroCondition(dependencySatisfies('@warp-drive/ember', '*'))) {
-    hasWarpDriveEmber = true;
-    hasRegisteredFromEmberPackage = peekTransient('signalHooks') !== null;
-  }
-  if (macroCondition(dependencySatisfies('@ember-data/tracking', '*'))) {
-    hasEmberDataTracking = true;
-    if (!hasRegisteredFromEmberPackage) {
-      // @ts-expect-error
-      const {
-        buildSignalConfig
-      } = importSync('@ember-data/tracking');
-      // eslint-disable-next-line @typescript-eslint/no-unsafe-argument
-      setupSignals(buildSignalConfig);
-    }
-  }
-
-  // we should probably still print here if @ember-data/tracking is present
-  if (!hasRegisteredFromEmberPackage) {
-    const message = [`Using WarpDrive with EmberJS requires configuring it to use Ember's reactivity system.`, `Previously this was provided by installing the package '@ember-data/tracking', but this package is now deprecated.`, ``, `To resolve this deprecation, follow these steps:`, hasEmberDataTracking ? `- remove "@ember-data/tracking" and (if needed) "@ember-data-types/tracking" from your project in both your package.json and tsconfig.json` : false, hasWarpDriveEmber ? false : `- add "@warp-drive/ember" to your project in your package.json (and run install)`, '- add the following import to your app.js file:', '', '\t```', `\timport '@warp-drive/ember/install';`, '\t```', ``, '- mark this deprecation as resolved in your project by adding the following to your WarpDrive config in ember-cli-build.js:', '', '\t```', '\tconst { setConfig } = await import("@warp-drive/build-config");', '\tsetConfig(app, __dirname, {', '\t  deprecations: {', '\t    DEPRECATE_TRACKING_PACKAGE: false,', '\t  },', '\t});', '\t```', ``, `For more information, see the Package Unification RFC: https://rfcs.emberjs.com/id/1075-warp-drive-package-unification/`].filter(l => l !== false).join('\n');
-    deprecate(message, false, {
-      id: 'warp-drive.deprecate-tracking-package',
-      until: '6.0.0',
-      for: 'warp-drive',
-      since: {
-        enabled: '5.3.4',
-        available: '4.13'
-      },
-      url: 'https://deprecations.emberjs.com/id/warp-drive.deprecate-tracking-package'
-    });
-  }
+	let hasEmberDataTracking = false;
+	let hasWarpDriveEmber = false;
+	let hasRegisteredFromEmberPackage = false;
+	if (macroCondition(dependencySatisfies("@warp-drive/ember", "*"))) {
+		hasWarpDriveEmber = true;
+		hasRegisteredFromEmberPackage = peekTransient("signalHooks") !== null;
+	}
+	if (macroCondition(dependencySatisfies("@ember-data/tracking", "*"))) {
+		hasEmberDataTracking = true;
+		if (!hasRegisteredFromEmberPackage) {
+			const { buildSignalConfig } = importSync("@ember-data/tracking");
+			setupSignals(buildSignalConfig);
+		}
+	}
+	if (!hasRegisteredFromEmberPackage) {
+		const message = [
+			`Using WarpDrive with EmberJS requires configuring it to use Ember's reactivity system.`,
+			`Previously this was provided by installing the package '@ember-data/tracking', but this package is now deprecated.`,
+			``,
+			`To resolve this deprecation, follow these steps:`,
+			hasEmberDataTracking ? `- remove "@ember-data/tracking" and (if needed) "@ember-data-types/tracking" from your project in both your package.json and tsconfig.json` : false,
+			hasWarpDriveEmber ? false : `- add "@warp-drive/ember" to your project in your package.json (and run install)`,
+			"- add the following import to your app.js file:",
+			"",
+			"	```",
+			`\timport '@warp-drive/ember/install';`,
+			"	```",
+			``,
+			"- mark this deprecation as resolved in your project by adding the following to your WarpDrive config in ember-cli-build.js:",
+			"",
+			"	```",
+			"	const { setConfig } = await import(\"@warp-drive/build-config\");",
+			"	setConfig(app, __dirname, {",
+			"	  deprecations: {",
+			"	    DEPRECATE_TRACKING_PACKAGE: false,",
+			"	  },",
+			"	});",
+			"	```",
+			``,
+			`For more information, see the Package Unification RFC: https://rfcs.emberjs.com/id/1075-warp-drive-package-unification/`
+		].filter((l) => l !== false).join("\n");
+		deprecate(message, false, {
+			id: "warp-drive.deprecate-tracking-package",
+			until: "6.0.0",
+			for: "warp-drive",
+			since: {
+				enabled: "5.3.4",
+				available: "4.13"
+			},
+			url: "https://deprecations.emberjs.com/id/warp-drive.deprecate-tracking-package"
+		});
+	}
 }
+
+//#endregion
+export { CacheHandler, Store as default, recordIdentifierFor, setIdentifierForgetMethod, setIdentifierGenerationMethod, setIdentifierResetMethod, setIdentifierUpdateMethod, setKeyInfoForResource, storeFor };
+//# sourceMappingURL=index.js.map

package/dist/index.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.js","names":["deprecate","dependencySatisfies","importSync","macroCondition","getGlobalConfig","Store","setupSignals","peekTransient","default","CacheHandler","recordIdentifierFor","storeFor","setIdentifierGenerationMethod","setIdentifierUpdateMethod","setIdentifierForgetMethod","setIdentifierResetMethod","setKeyInfoForResource","WarpDrive","deprecations","DEPRECATE_TRACKING_PACKAGE","hasEmberDataTracking","hasWarpDriveEmber","hasRegisteredFromEmberPackage","buildSignalConfig","message","filter","l","join","id","until","for","since","enabled","available","url"],"sources":["../src/index.ts"],"sourcesContent":["/**\n * This package provides [*Ember***Data**](https://github.com/warp-drive-data/warp-drive/)'s `Store` class.\n *\n * A {@link Store} coordinates interaction between your application, a {@link Cache},\n * and sources of data (such as your API or a local persistence layer) accessed via a {@link RequestManager}.\n *\n * Optionally, a Store can be configured to hydrate the response data into rich presentation classes.\n *\n * ## 🔨 Creating A Store\n *\n * To use a `Store` we will need to do few things: add a {@link Cache}\n * to store data **in-memory**, add a {@link Handler} to fetch data from a source,\n * and implement `instantiateRecord` to tell the store how to display the data for individual resources.\n *\n * > **Note**\n * > If you are using the package `ember-data` then a JSON:API cache, RequestManager, LegacyNetworkHandler,\n * > and `instantiateRecord` are configured for you by default.\n *\n * ### Configuring A Cache\n *\n * To start, let's install a [JSON:API](https://jsonapi.org/) cache. If your app uses `GraphQL` or `REST` other\n * caches may better fit your data. You can author your own cache by creating one that\n * conforms to the {@link Cache | spec}.\n *\n * The package `@ember-data/json-api` provides a [JSON:API](https://jsonapi.org/) cache we can use.\n * After installing it, we can configure the store to use this cache.\n *\n * ```js\n * import Store from '@ember-data/store';\n * import Cache from '@ember-data/json-api';\n *\n * class extends Store {\n *   createCache(storeWrapper) {\n *     return new Cache(storeWrapper);\n *   }\n * }\n * ```\n *\n * Now that we have a `cache` let's setup something to handle fetching\n * and saving data via our API.\n *\n * > **Note**\n * > The `ember-data` package automatically includes and configures\n * > the `@ember-data/json-api` cache for you.\n *\n * ### Handling Requests\n *\n * When *Ember***Data** needs to fetch or save data it will pass that request to your application's `RequestManager` for fulfillment. How this fulfillment occurs (in-memory, device storage, via single or multiple API requests, etc.) is then up to the registered request handlers.\n *\n * To start, let's install the `RequestManager` from `@ember-data/request` and the basic `Fetch` handler from ``@ember-data/request/fetch`.\n *\n * > **Note**\n * > If your app uses `GraphQL`, `REST` or different conventions for `JSON:API` than your cache expects, other handlers may better fit your data. You can author your own handler by creating one that conforms to the [handler interface](https://github.com/warp-drive-data/warp-drive/tree/main/packages/request#handling-requests).\n *\n * ```ts\n * import Store from '@ember-data/store';\n * import RequestManager from '@ember-data/request';\n * import Fetch from '@ember-data/request/fetch';\n *\n * export default class extends Store {\n *   requestManager = new RequestManager()\n *    .use([Fetch]);\n * }\n * ```\n *\n * **Using RequestManager as a Service**\n *\n * Alternatively if you have configured the `RequestManager` to be a service you may re-use it.\n *\n * *app/services/request.js*\n * ```ts\n * import RequestManager from '@ember-data/request';\n * import Fetch from '@ember-data/request/fetch';\n *\n * export default {\n *   create() {\n *     return new RequestManager()\n *       .use([Fetch])\n *       .useCache(CacheHandler);\n *   }\n * }\n * ```\n *\n * *app/services/store.js*\n * ```ts\n * import Store from '@ember-data/store';\n * import { service } from '@ember/service';\n *\n * export default class extends Store {\n *   @service('request') requestManager\n * }\n * ```\n *\n *\n * ### Presenting Data from the Cache\n *\n * Now that we have a source and a cache for our data, we need to configure how\n * the Store delivers that data back to our application. We do this via the {@link Store.instantiateRecord | instantiateRecord hook}\n * which allows us to transform the data for a resource before handing it to the application.\n *\n * A naive way to present the data would be to return it as JSON. Typically instead\n * this hook will be used to add reactivity and make each unique resource a singleton,\n * ensuring that if the cache updates our presented data will reflect the new state.\n *\n * Below is an example of using the hooks `instantiateRecord` and a `teardownRecord`\n * to provide minimal read-only reactive state for simple resources.\n *\n * ```ts\n * import Store, { recordIdentifierFor } from '@ember-data/store';\n * import { TrackedObject } from 'tracked-built-ins';\n *\n * class extends Store {\n *   instantiateRecord(identifier) {\n *     const { cache, notifications } = this;\n *\n *     // create a TrackedObject with our attributes, id and type\n *     const record = new TrackedObject(Object.assign({}, cache.peek(identifier)));\n *     record.type = identifier.type;\n *     record.id = identifier.id;\n *\n *     notifications.subscribe(identifier, (_, change) => {\n *       if (change === 'attributes') {\n *         Object.assign(record, cache.peek(identifier));\n *       }\n *     });\n *\n *     return record;\n *   }\n * }\n * ```\n *\n * Because `instantiateRecord` is opaque to the nature of the record, an implementation\n * can be anything from a fairly simple object to a robust proxy that intelligently links\n * together associated records through relationships.\n *\n * This also enables creating a record that separates `edit` flows from `create` flows\n * entirely. A record class might choose to implement a `checkout`method that gives access\n * to an editable instance while the primary record continues to be read-only and reflect\n * only persisted (non-mutated) state.\n *\n * Typically you will choose an existing record implementation such as `@ember-data/model`\n * for your application.\n *\n * Because of the boundaries around instantiation and the cache, record implementations\n * should be capable of interop both with each other and with any `Cache`. Due to this,\n * if needed an application can utilize multiple record implementations and multiple cache\n * implementations either to support enhanced features for only a subset of records or to\n * be able to incrementally migrate from one record/cache to another record or cache.\n *\n * > **Note**\n * > The `ember-data` package automatically includes the `@ember-data/model`\n * > package and configures it for you.\n *\n * @module\n */\nimport { deprecate } from '@ember/debug';\n\nimport { dependencySatisfies, importSync, macroCondition } from '@embroider/macros';\n\n// eslint-disable-next-line @typescript-eslint/no-unused-vars\nimport { type RequestManager, Store } from '@warp-drive/core';\nimport { DEPRECATE_TRACKING_PACKAGE } from '@warp-drive/core/build-config/deprecations';\nimport { setupSignals } from '@warp-drive/core/configure';\n// eslint-disable-next-line @typescript-eslint/no-unused-vars\nimport type { Handler } from '@warp-drive/core/request';\nimport { peekTransient } from '@warp-drive/core/types/-private';\n// eslint-disable-next-line @typescript-eslint/no-unused-vars\nimport type { Cache } from '@warp-drive/core/types/cache';\n\nexport { Store as default };\n\nexport {\n  type StoreRequestContext,\n  CacheHandler,\n  type Document,\n  type CachePolicy,\n  type StoreRequestInput,\n  recordIdentifierFor,\n  storeFor,\n  type DocumentCacheOperation,\n  type CacheOperation,\n  type NotificationType,\n  setIdentifierGenerationMethod,\n  setIdentifierUpdateMethod,\n  setIdentifierForgetMethod,\n  setIdentifierResetMethod,\n  setKeyInfoForResource,\n} from '@warp-drive/core';\n\nif (DEPRECATE_TRACKING_PACKAGE) {\n  let hasEmberDataTracking = false;\n  let hasWarpDriveEmber = false;\n  let hasRegisteredFromEmberPackage = false;\n\n  if (macroCondition(dependencySatisfies('@warp-drive/ember', '*'))) {\n    hasWarpDriveEmber = true;\n    hasRegisteredFromEmberPackage = peekTransient('signalHooks') !== null;\n  }\n\n  if (macroCondition(dependencySatisfies('@ember-data/tracking', '*'))) {\n    hasEmberDataTracking = true;\n\n    if (!hasRegisteredFromEmberPackage) {\n      // @ts-expect-error\n      const { buildSignalConfig } = importSync('@ember-data/tracking');\n      // eslint-disable-next-line @typescript-eslint/no-unsafe-argument\n      setupSignals(buildSignalConfig);\n    }\n  }\n\n  // we should probably still print here if @ember-data/tracking is present\n  if (!hasRegisteredFromEmberPackage) {\n    const message = [\n      `Using WarpDrive with EmberJS requires configuring it to use Ember's reactivity system.`,\n      `Previously this was provided by installing the package '@ember-data/tracking', but this package is now deprecated.`,\n      ``,\n      `To resolve this deprecation, follow these steps:`,\n      hasEmberDataTracking\n        ? `- remove \"@ember-data/tracking\" and (if needed) \"@ember-data-types/tracking\" from your project in both your package.json and tsconfig.json`\n        : false,\n      hasWarpDriveEmber ? false : `- add \"@warp-drive/ember\" to your project in your package.json (and run install)`,\n      '- add the following import to your app.js file:',\n      '',\n      '\\t```',\n      `\\timport '@warp-drive/ember/install';`,\n      '\\t```',\n      ``,\n      '- mark this deprecation as resolved in your project by adding the following to your WarpDrive config in ember-cli-build.js:',\n      '',\n      '\\t```',\n      '\\tconst { setConfig } = await import(\"@warp-drive/build-config\");',\n      '\\tsetConfig(app, __dirname, {',\n      '\\t  deprecations: {',\n      '\\t    DEPRECATE_TRACKING_PACKAGE: false,',\n      '\\t  },',\n      '\\t});',\n      '\\t```',\n      ``,\n      `For more information, see the Package Unification RFC: https://rfcs.emberjs.com/id/1075-warp-drive-package-unification/`,\n    ]\n      .filter((l) => l !== false)\n      .join('\\n');\n\n    deprecate(message, false, {\n      id: 'warp-drive.deprecate-tracking-package',\n      until: '6.0.0',\n      for: 'warp-drive',\n      since: {\n        enabled: '5.3.4',\n        available: '4.13',\n      },\n      url: 'https://deprecations.emberjs.com/id/warp-drive.deprecate-tracking-package',\n    });\n  }\n}\n"],"mappings":";;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;AA6LA,IAAAG,eAAAC,gBAAA,CAAA,CAAAa,UAAAC,aAAAC,0BAAA,GAAgC;CAC9B,IAAIC,uBAAuB;CAC3B,IAAIC,oBAAoB;CACxB,IAAIC,gCAAgC;CAEpC,IAAInB,eAAeF,oBAAoB,qBAAqB,GAAG,CAAC,GAAG;EACjEoB,oBAAoB;EACpBC,gCAAgCf,cAAc,aAAa,MAAM;CACnE;CAEA,IAAIJ,eAAeF,oBAAoB,wBAAwB,GAAG,CAAC,GAAG;EACpEmB,uBAAuB;EAEvB,IAAI,CAACE,+BAA+B;GAElC,MAAM,EAAEC,sBAAsBrB,WAAW,sBAAsB;GAE/DI,aAAaiB,iBAAiB;EAChC;CACF;CAGA,IAAI,CAACD,+BAA+B;EAClC,MAAME,UAAU;GACd;GACA;GACA;GACA;GACAJ,uBACI,+IACA;GACJC,oBAAoB,QAAQ;GAC5B;GACA;GACA;GACA;GACA;GACA;GACA;GACA;GACA;GACA;GACA;GACA;GACA;GACA;GACA;GACA;GACA;GACA;EAAyH,CAC1H,CACEI,QAAQC,MAAMA,MAAM,KAAK,CAAC,CAC1BC,KAAK,IAAI;EAEZ3B,UAAUwB,SAAS,OAAO;GACxBI,IAAI;GACJC,OAAO;GACPC,KAAK;GACLC,OAAO;IACLC,SAAS;IACTC,WAAW;GACb;GACAC,KAAK;EACP,CAAC;CACH;AACF"}

package/dist/types.d.ts

@@ -0,0 +1,2 @@
+import { BaseFinderOptions, CacheCapabilitiesManager, FindAllOptions, FindRecordOptions, LegacyResourceQuery, ModelSchema, QueryOptions, SchemaService } from "@warp-drive/core/types";
+export type { BaseFinderOptions, CacheCapabilitiesManager, FindAllOptions, FindRecordOptions, LegacyResourceQuery, ModelSchema, QueryOptions, SchemaService };

package/dist/types.js

@@ -1 +0,0 @@
-

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ember-data/store",
-  "version": "5.9.0-alpha.21",
+  "version": "5.9.0-alpha.22",
   "description": "(Legacy) EmberData Store service which coordinates the cache with the network and presentation layers.",
   "keywords": [
     "ember-addon"
@@ -13,12 +13,12 @@
   "license": "MIT",
   "author": "Chris Thoburn <runspired@users.noreply.github.com>",
   "files": [
-    "unstable-preview-types",
     "addon-main.cjs",
     "dist",
     "README.md",
     "LICENSE.md",
-    "logos"
+    "logos",
+    "unstable-preview-types"
   ],
   "exports": {
     ".": {
@@ -33,10 +33,10 @@
   },
   "dependencies": {
     "@embroider/macros": "^1.20.6",
-    "@warp-drive/core": "5.9.0-alpha.21"
+    "@warp-drive/core": "5.9.0-alpha.22"
   },
   "peerDependencies": {
-    "@ember-data/tracking": "5.9.0-alpha.21",
+    "@ember-data/tracking": "5.9.0-alpha.22",
     "@ember/test-waiters": "^3.1.0 || ^4.0.0"
   },
   "peerDependenciesMeta": {
@@ -52,12 +52,12 @@
     "@babel/plugin-transform-typescript": "^7.28.0",
     "@babel/preset-env": "^7.28.3",
     "@babel/preset-typescript": "^7.27.1",
-    "@ember-data/tracking": "5.9.0-alpha.21",
+    "@ember-data/tracking": "5.9.0-alpha.22",
     "@ember/test-waiters": "^4.1.1",
-    "@warp-drive/internal-config": "5.9.0-alpha.21",
+    "@warp-drive/internal-config": "5.9.0-alpha.22",
     "ember-source": "~6.12.0",
-    "typescript": "^5.9.3",
-    "vite": "^7.3.1"
+    "tsdown": "^0.22.14",
+    "typescript": "^5.9.3"
   },
   "volta": {
     "extends": "../../package.json"
@@ -79,8 +79,9 @@
   },
   "scripts": {
     "lint": "eslint . --quiet --cache --cache-strategy=content",
-    "build:pkg": "vite build",
+    "check:types": "tsc --noEmit",
+    "build:pkg": "node node_modules/tsdown/dist/run.mjs",
     "sync": "echo \"syncing\"",
-    "start": "vite"
+    "start": "node node_modules/tsdown/dist/run.mjs --watch"
   }
 }

package/unstable-preview-types/-private.d.ts

@@ -1,4 +1,3 @@
 declare module '@ember-data/store/-private' {
   export * from "@warp-drive/core/store/-private";
-  
 }

package/unstable-preview-types/configure.d.ts

@@ -1,17 +1,4 @@
 declare module '@ember-data/store/configure' {
-  /**
-  * Provides a configuration API for the reactivity system
-  * that WarpDrive should use.
-  *
-  * @module
-  */
-  /**
-  * Configures the signals implementation to use. Supports multiple
-  * implementations simultaneously.
-  *
-  * @public
-  * @param {function} buildConfig - a function that takes options and returns a configuration object
-  */
-  export { setupSignals } from "@warp-drive/core/configure";
-  
+  import { setupSignals } from "@warp-drive/core/configure";
+  export { setupSignals };
 }

package/unstable-preview-types/index.d.ts

@@ -2,8 +2,6 @@
 /// <reference path="./types.d.ts" />
 /// <reference path="./-private.d.ts" />
 declare module '@ember-data/store' {
-  import { Store } from "@warp-drive/core";
-  export { Store as default };
-  export { type StoreRequestContext, CacheHandler, type Document, type CachePolicy, type StoreRequestInput, recordIdentifierFor, storeFor, type DocumentCacheOperation, type CacheOperation, type NotificationType, setIdentifierGenerationMethod, setIdentifierUpdateMethod, setIdentifierForgetMethod, setIdentifierResetMethod, setKeyInfoForResource } from "@warp-drive/core";
-  
+  import { CacheHandler, CacheOperation, CachePolicy, Document, DocumentCacheOperation, NotificationType, Store, StoreRequestContext, StoreRequestInput, recordIdentifierFor, setIdentifierForgetMethod, setIdentifierGenerationMethod, setIdentifierResetMethod, setIdentifierUpdateMethod, setKeyInfoForResource, storeFor } from "@warp-drive/core";
+  export { CacheHandler, type CacheOperation, type CachePolicy, type Document, type DocumentCacheOperation, type NotificationType, type StoreRequestContext, type StoreRequestInput, Store as default, recordIdentifierFor, setIdentifierForgetMethod, setIdentifierGenerationMethod, setIdentifierResetMethod, setIdentifierUpdateMethod, setKeyInfoForResource, storeFor };
 }

package/unstable-preview-types/types.d.ts

@@ -1,4 +1,4 @@
 declare module '@ember-data/store/types' {
-  export type { CacheCapabilitiesManager, ModelSchema, SchemaService, BaseFinderOptions, FindRecordOptions, LegacyResourceQuery, QueryOptions, FindAllOptions } from "@warp-drive/core/types";
-  
+  import { BaseFinderOptions, CacheCapabilitiesManager, FindAllOptions, FindRecordOptions, LegacyResourceQuery, ModelSchema, QueryOptions, SchemaService } from "@warp-drive/core/types";
+  export type { BaseFinderOptions, CacheCapabilitiesManager, FindAllOptions, FindRecordOptions, LegacyResourceQuery, ModelSchema, QueryOptions, SchemaService };
 }