@ember-data/store 5.6.0-beta.0 → 5.6.0-beta.2

package/README.md

@@ -124,11 +124,11 @@ import RequestManager from '@ember-data/request';
 import { CacheHandler } from '@ember-data/store';
 import Fetch from '@ember-data/request/fetch';
 
-export default class extends RequestManager {
-  constructor(createArgs) {
-    super(createArgs);
-    this.use([Fetch]);
-    this.useCache(CacheHandler);
+export default {
+  create() {
+    return new RequestManager()
+      .use([Fetch])
+      .useCache(CacheHandler);
   }
 }
 ```

package/addon-main.cjs

@@ -1,5 +1,5 @@
 'use strict';
 
-const { addonShim } = require('@warp-drive/build-config/addon-shim.cjs');
+const { addonShim } = require('@warp-drive/core/addon-shim.cjs');
 
 module.exports = addonShim(__dirname);

package/dist/-private.js

@@ -1,2 +1 @@
-export { C as CacheHandler, k as CollectionRecordArray, I as LiveArray, M as MUTATE, R as RecordArrayManager, v as RelatedCollection, l as SOURCE, G as Signals, S as Store, q as StoreMap, _ as _clearCaches, u as _deprecatingNormalize, h as coerceId, g as constructResource, L as consumeInternalSignal, F as defineNonEnumerableSignal, E as defineSignal, j as ensureStringId, D as entangleSignal, m as fastPush, B as gate, N as getOrCreateInternalSignal, y as getPromiseState, z as getRequestState, f as isDocumentIdentifier, i as isStableIdentifier, w as log, x as logGroup, A as memoized, K as notifyInternalSignal, p as peekCache, H as peekInternalSignal, r as recordIdentifierFor, n as removeRecordDataFor, t as setCacheFor, o as setRecordIdentifier, s as storeFor, J as withSignalStore } from "./request-state-uRtpn0Lc.js";
-export { A as ARRAY_SIGNAL, O as OBJECT_SIGNAL, c as createMemo } from "./configure-BfLLW6GY.js";
+export * from '@warp-drive/core/store/-private';

package/dist/configure.js

@@ -1 +1 @@
-export { s as setupSignals } from "./configure-BfLLW6GY.js";
+export { setupSignals } from '@warp-drive/core/configure';

package/dist/index.js

@@ -1,5 +1,208 @@
-export { C as CacheHandler, S as default, r as recordIdentifierFor, c as setIdentifierForgetMethod, a as setIdentifierGenerationMethod, d as setIdentifierResetMethod, b as setIdentifierUpdateMethod, e as setKeyInfoForResource, s as storeFor } from "./request-state-uRtpn0Lc.js";
-import '@ember/debug';
-import '@embroider/macros';
-import '@ember-data/request-utils/string';
-import "./configure-BfLLW6GY.js";
+import { deprecate } from '@ember/debug';
+import { macroCondition, getGlobalConfig, dependencySatisfies, importSync } from '@embroider/macros';
+import { setupSignals } from '@warp-drive/core/configure';
+export { CacheHandler, Store as default, recordIdentifierFor, setIdentifierForgetMethod, setIdentifierGenerationMethod, setIdentifierResetMethod, setIdentifierUpdateMethod, setKeyInfoForResource, storeFor } from '@warp-drive/core';
+
+/**
+ * <p align="center">
+ *   <img
+ *     class="project-logo"
+ *     src="https://raw.githubusercontent.com/emberjs/data/4612c9354e4c54d53327ec2cf21955075ce21294/ember-data-logo-light.svg#gh-light-mode-only"
+ *     alt="EmberData Store"
+ *     width="240px"
+ *     title="EmberData Store"
+ *     />
+ * </p>
+ *
+ * This package provides [*Ember***Data**](https://github.com/emberjs/data/)'s `Store` class.
+ *
+ * A [Store](https://api.emberjs.com/ember-data/release/classes/Store) coordinates interaction between your application, a [Cache](https://api.emberjs.com/ember-data/release/classes/%3CInterface%3E%20Cache),
+ * and sources of data (such as your API or a local persistence layer) accessed via a [RequestManager](https://github.com/emberjs/data/tree/main/packages/request).
+ *
+ * Optionally, a Store can be configured to hydrate the response data into rich presentation classes.
+ *
+ * ## Installation
+ *
+ * If you have installed `ember-data` then you already have this package installed.
+ * Otherwise you can install it using your javascript package manager of choice.
+ * For instance with [pnpm](https://pnpm.io/)
+ *
+ * ```
+ * pnpm add @ember-data/store
+ * ```
+ *
+ * After installing you will want to configure your first `Store`. Read more below
+ * for how to create and configure stores for your application.
+ *
+ *
+ * ## 🔨 Creating A Store
+ *
+ * To use a `Store` we will need to do few things: add a [Cache](https://api.emberjs.com/ember-data/release/classes/%3CInterface%3E%20Cache)
+ * to store data **in-memory**, add a [Handler](https://api.emberjs.com/ember-data/release/classes/%3CInterface%3E%20Cache) 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 [spec](https://api.emberjs.com/ember-data/release/classes/%3CInterface%3E%20Cache).
+ *
+ * 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/emberjs/data/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 hook
+ * [instantiateRecord](https://api.emberjs.com/ember-data/release/classes/Store/methods/instantiateRecord%20(hook)?anchor=instantiateRecord%20(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;
+  if (macroCondition(dependencySatisfies('@ember-data/tracking', '*'))) {
+    hasEmberDataTracking = true;
+    // @ts-expect-error
+    const {
+      buildSignalConfig
+    } = importSync('@ember-data/tracking');
+    // eslint-disable-next-line @typescript-eslint/no-unsafe-argument
+    setupSignals(buildSignalConfig);
+  }
+  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, `- add "@warp-drive/ember" to your project in both your package.json and tsconfig.json`, '- 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'
+  });
+}

package/dist/types.js

@@ -0,0 +1 @@
+

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ember-data/store",
-  "version": "5.6.0-beta.0",
+  "version": "5.6.0-beta.2",
   "description": "The core of EmberData. Provides the Store service which coordinates the cache with the network and presentation layers.",
   "keywords": [
     "ember-addon"
@@ -33,20 +33,17 @@
   },
   "dependencies": {
     "@embroider/macros": "^1.16.12",
-    "@warp-drive/build-config": "5.6.0-beta.0"
+    "@warp-drive/core": "5.6.0-beta.1"
   },
   "peerDependencies": {
-    "ember-source": "3.28.12 || ^4.0.4 || ^5.0.0 || ^6.0.0",
-    "@ember-data/request": "5.6.0-beta.0",
-    "@ember-data/request-utils": "5.6.0-beta.0",
-    "@warp-drive/core-types": "5.6.0-beta.0",
-    "@ember-data/tracking": "5.6.0-beta.0"
+    "@ember-data/tracking": "5.6.0-beta.2",
+    "@ember/test-waiters": "^3.1.0 || ^4.0.0"
   },
   "peerDependenciesMeta": {
     "@ember-data/tracking": {
       "optional": true
     },
-    "ember-source": {
+    "@ember/test-waiters": {
       "optional": true
     }
   },
@@ -55,20 +52,12 @@
     "@babel/plugin-transform-typescript": "^7.27.0",
     "@babel/preset-env": "^7.26.9",
     "@babel/preset-typescript": "^7.27.0",
-    "@ember-data/request": "5.6.0-beta.0",
-    "@ember-data/request-utils": "5.6.0-beta.0",
-    "@glimmer/component": "^2.0.0",
-    "@warp-drive/core-types": "5.6.0-beta.0",
-    "@warp-drive/internal-config": "5.6.0-beta.0",
-    "@ember-data/tracking": "5.6.0-beta.0",
-    "decorator-transforms": "^2.3.0",
+    "@warp-drive/internal-config": "5.6.0-beta.2",
+    "@ember-data/tracking": "5.6.0-beta.2",
+    "@ember/test-waiters": "^4.1.0",
     "ember-source": "~6.3.0",
-    "expect-type": "^1.2.1",
     "typescript": "^5.8.3",
-    "vite": "^5.4.15"
-  },
-  "engines": {
-    "node": ">= 18.20.8"
+    "vite": "^7.0.0"
   },
   "volta": {
     "extends": "../../package.json"

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

@@ -1,33 +1,4 @@
 declare module '@ember-data/store/-private' {
-  /**
-    @module @ember-data/store
-  */
-  export { Store, storeFor } from '@ember-data/store/-private/store-service';
-  export { recordIdentifierFor } from '@ember-data/store/-private/caches/instance-cache';
-  export { CacheHandler, type StoreRequestContext } from '@ember-data/store/-private/cache-handler/handler';
-  export { type CachePolicy } from '@ember-data/store/-private/cache-handler/types';
-  export { isStableIdentifier, isDocumentIdentifier } from '@ember-data/store/-private/caches/identifier-cache';
-  export { constructResource } from '@ember-data/store/-private/utils/construct-resource';
-  export type { ReactiveDocument as Document } from '@ember-data/store/-private/document';
-  export type { InstanceCache } from '@ember-data/store/-private/caches/instance-cache';
-  export type { FindRecordQuery, Request, SaveRecordMutation, RequestCacheRequestState, RequestStateService, } from '@ember-data/store/-private/network/request-cache';
-  export type { CreateRecordProperties } from '@ember-data/store/-private/store-service';
-  export { coerceId, ensureStringId } from '@ember-data/store/-private/utils/coerce-id';
-  export type { NativeProxy } from '@ember-data/store/-private/record-arrays/native-proxy-type-fix';
-  export { IdentifierArray as LiveArray, Collection as CollectionRecordArray, SOURCE, MUTATE, } from '@ember-data/store/-private/record-arrays/identifier-array';
-  export { RecordArrayManager, fastPush } from '@ember-data/store/-private/managers/record-array-manager';
-  export { _clearCaches } from '@ember-data/store/-private/caches/instance-cache';
-  export { peekCache, removeRecordDataFor } from '@ember-data/store/-private/caches/cache-utils';
-  export { setRecordIdentifier, StoreMap } from '@ember-data/store/-private/caches/instance-cache';
-  export { setCacheFor } from '@ember-data/store/-private/caches/cache-utils';
-  export { normalizeModelName as _deprecatingNormalize } from '@ember-data/store/-private/utils/normalize-model-name';
-  export type { StoreRequestInput } from '@ember-data/store/-private/cache-handler/handler';
-  export { RelatedCollection } from '@ember-data/store/-private/record-arrays/many-array';
-  export { log, logGroup } from '@ember-data/store/-private/debug/utils';
-  export { getPromiseState, type PromiseState } from '@ember-data/store/-private/new-core-tmp/promise-state';
-  export { getRequestState, type RequestLoadingState, type RequestCacheRequestState as RequestState, } from '@ember-data/store/-private/new-core-tmp/request-state';
-  export { createMemo, type SignalHooks } from '@ember-data/store/-private/new-core-tmp/reactivity/configure';
-  export { memoized, gate, entangleSignal, defineSignal, defineNonEnumerableSignal, } from '@ember-data/store/-private/new-core-tmp/reactivity/signal';
-  export { ARRAY_SIGNAL, OBJECT_SIGNAL, Signals, type WarpDriveSignal, peekInternalSignal, withSignalStore, notifyInternalSignal, consumeInternalSignal, getOrCreateInternalSignal, } from '@ember-data/store/-private/new-core-tmp/reactivity/internal';
-}
-//# sourceMappingURL=-private.d.ts.map
+  export * from "@warp-drive/core/store/-private";
+  
+}

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

@@ -1,21 +1,17 @@
 declare module '@ember-data/store/configure' {
   /**
-   * Provides a configuration API for the reactivity system
-   * that WarpDrive should use.
-   *
-   * @module @ember-data/store/configure
-   * @main @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.
-   *
-   * @method setupSignals
-   * @static
-   * @for @ember-data/store/configure
-   * @public
-   * @param {function} buildConfig - a function that takes options and returns a configuration object
-   */
-  export { setupSignals } from '@ember-data/store/-private/new-core-tmp/reactivity/configure';
-}
-//# sourceMappingURL=configure.d.ts.map
+  * 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";
+  
+}

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

@@ -1,229 +1,7 @@
-/// <reference path="./types.d.ts" />
 /// <reference path="./configure.d.ts" />
 /// <reference path="./-private.d.ts" />
-/// <reference path="./-types/overview.d.ts" />
-/// <reference path="./-types/q/store.d.ts" />
-/// <reference path="./-types/q/identifier.d.ts" />
-/// <reference path="./-types/q/promise-proxies.d.ts" />
-/// <reference path="./-types/q/schema-service.d.ts" />
-/// <reference path="./-types/q/record-instance.d.ts" />
-/// <reference path="./-types/q/record-data-json-api.d.ts" />
-/// <reference path="./-types/q/cache-capabilities-manager.d.ts" />
-/// <reference path="./-types/q/ds-model.d.ts" />
-/// <reference path="./-private/store-service.d.ts" />
-/// <reference path="./-private/store-service.type-test.d.ts" />
-/// <reference path="./-private/document.d.ts" />
-/// <reference path="./-private/caches/cache-utils.d.ts" />
-/// <reference path="./-private/caches/resource-utils.d.ts" />
-/// <reference path="./-private/caches/instance-cache.d.ts" />
-/// <reference path="./-private/caches/identifier-cache.d.ts" />
-/// <reference path="./-private/legacy-model-support/shim-model-class.d.ts" />
-/// <reference path="./-private/legacy-model-support/record-reference.d.ts" />
-/// <reference path="./-private/managers/notification-manager.d.ts" />
-/// <reference path="./-private/managers/record-array-manager.d.ts" />
-/// <reference path="./-private/managers/cache-capabilities-manager.d.ts" />
-/// <reference path="./-private/managers/cache-manager.d.ts" />
-/// <reference path="./-private/new-core-tmp/request-state.d.ts" />
-/// <reference path="./-private/new-core-tmp/promise-state.d.ts" />
-/// <reference path="./-private/new-core-tmp/reactivity/internal.d.ts" />
-/// <reference path="./-private/new-core-tmp/reactivity/signal.d.ts" />
-/// <reference path="./-private/new-core-tmp/reactivity/configure.d.ts" />
-/// <reference path="./-private/debug/utils.d.ts" />
-/// <reference path="./-private/network/request-cache.d.ts" />
-/// <reference path="./-private/cache-handler/utils.d.ts" />
-/// <reference path="./-private/cache-handler/types.d.ts" />
-/// <reference path="./-private/cache-handler/handler.d.ts" />
-/// <reference path="./-private/utils/normalize-model-name.d.ts" />
-/// <reference path="./-private/utils/uuid-polyfill.d.ts" />
-/// <reference path="./-private/utils/construct-resource.d.ts" />
-/// <reference path="./-private/utils/is-non-empty-string.d.ts" />
-/// <reference path="./-private/utils/coerce-id.d.ts" />
-/// <reference path="./-private/record-arrays/identifier-array.d.ts" />
-/// <reference path="./-private/record-arrays/many-array.d.ts" />
-/// <reference path="./-private/record-arrays/native-proxy-type-fix.d.ts" />
+/// <reference path="./types.d.ts" />
 declare module '@ember-data/store' {
-  /**
-   * <p align="center">
-   *   <img
-   *     class="project-logo"
-   *     src="https://raw.githubusercontent.com/emberjs/data/4612c9354e4c54d53327ec2cf21955075ce21294/ember-data-logo-light.svg#gh-light-mode-only"
-   *     alt="EmberData Store"
-   *     width="240px"
-   *     title="EmberData Store"
-   *     />
-   * </p>
-   *
-   * This package provides [*Ember***Data**](https://github.com/emberjs/data/)'s `Store` class.
-   *
-   * A [Store](https://api.emberjs.com/ember-data/release/classes/Store) coordinates interaction between your application, a [Cache](https://api.emberjs.com/ember-data/release/classes/%3CInterface%3E%20Cache),
-   * and sources of data (such as your API or a local persistence layer) accessed via a [RequestManager](https://github.com/emberjs/data/tree/main/packages/request).
-   *
-   * Optionally, a Store can be configured to hydrate the response data into rich presentation classes.
-   *
-   * ## Installation
-   *
-   * If you have installed `ember-data` then you already have this package installed.
-   * Otherwise you can install it using your javascript package manager of choice.
-   * For instance with [pnpm](https://pnpm.io/)
-   *
-   * ```
-   * pnpm add @ember-data/store
-   * ```
-   *
-   * After installing you will want to configure your first `Store`. Read more below
-   * for how to create and configure stores for your application.
-   *
-   *
-   * ## 🔨 Creating A Store
-   *
-   * To use a `Store` we will need to do few things: add a [Cache](https://api.emberjs.com/ember-data/release/classes/%3CInterface%3E%20Cache)
-   * to store data **in-memory**, add a [Handler](https://api.emberjs.com/ember-data/release/classes/%3CInterface%3E%20Cache) 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 [spec](https://api.emberjs.com/ember-data/release/classes/%3CInterface%3E%20Cache).
-   *
-   * 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/emberjs/data/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 class extends RequestManager {
-   *   constructor(createArgs) {
-   *     super(createArgs);
-   *     this.use([Fetch]);
-   *   }
-   * }
-   * ```
-   *
-   * *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 hook
-   * [instantiateRecord](https://api.emberjs.com/ember-data/release/classes/Store/methods/instantiateRecord%20(hook)?anchor=instantiateRecord%20(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 @ember-data/store
-   * @main @ember-data/store
-   */
-  export { Store as default, type StoreRequestContext, CacheHandler, type Document, type CachePolicy, type StoreRequestInput, recordIdentifierFor, storeFor, } from '@ember-data/store/-private';
-  export type { DocumentCacheOperation, CacheOperation, NotificationType, } from '@ember-data/store/-private/managers/notification-manager';
-  export { setIdentifierGenerationMethod, setIdentifierUpdateMethod, setIdentifierForgetMethod, setIdentifierResetMethod, setKeyInfoForResource, } from '@ember-data/store/-private/caches/identifier-cache';
-}
-//# sourceMappingURL=index.d.ts.map
+  export { Store as default, 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";
+  
+}

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

@@ -1,7 +1,4 @@
 declare module '@ember-data/store/types' {
-  export type { CacheCapabilitiesManager } from '@ember-data/store/-types/q/cache-capabilities-manager';
-  export type { ModelSchema } from '@ember-data/store/-types/q/ds-model';
-  export type { SchemaService } from '@ember-data/store/-types/q/schema-service';
-  export type { BaseFinderOptions, FindRecordOptions, LegacyResourceQuery, QueryOptions, FindAllOptions, } from '@ember-data/store/-types/q/store';
-}
-//# sourceMappingURL=types.d.ts.map
+  export type { CacheCapabilitiesManager, ModelSchema, SchemaService, BaseFinderOptions, FindRecordOptions, LegacyResourceQuery, QueryOptions, FindAllOptions } from "@warp-drive/core/types";
+  
+}

package/dist/-private.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"-private.js","sources":[],"sourcesContent":[],"names":[],"mappings":";"}