@warp-drive/build-config 5.9.0-alpha.13 → 5.9.0-alpha.15

package/declarations/debugging.d.ts

@@ -1,55 +1,8 @@
 /**
-* # Log Instrumentation <Badge type="tip" text="debug only" />
+* While build-config is its own package, it should always be
+* used via `@warp-drive/core`.
 *
-* Many portions of the internals are helpfully instrumented with logging.
-* This instrumentation is always removed from production builds.
-*
-* Log instrumentation is "regionalized" to specific concepts and concerns
-* to enable you to enable/disable just the areas you are interested in.
-*
-* To activate a particular group of logs set the appropriate flag to `true`
-* either in your build config or via the runtime helper.
-*
-*
-* ## Runtime Activation
-*
-* ::: tip 💡 Just Works in browser Dev Tools!
-* No import is needed, and the logging config is preserved when the page is refreshed
-* :::
-*
-* ```ts
-* setWarpDriveLogging({
-*   LOG_CACHE: true,
-*   LOG_REQUESTS: true,
-* })
-* ```
-*
-* A runtime helper is attached to `globalThis` to enable activation of the logs
-* from anywhere in your application including from the devtools panel.
-*
-* The runtime helper overrides any build config settings for the given flag
-* for the current browser tab. It stores the configuration you give it in
-* `sessionStorage` so that it persists across page reloads of the current tab,
-* but not across browser tabs or windows.
-*
-* If you need to deactivate the logging, you can call the helper again with the
-* same flag set to `false` or just open a new tab/window.
-*
-* ## Buildtime Activation
-*
-* ```ts
-* setConfig(__dirname, app, {
-*   debug: {
-*     LOG_CACHE: true,
-*     LOG_REQUESTS: false,
-*     LOG_NOTIFICATIONS: true,
-*   }
-* });
-* ```
-*
-* The build config settings are used to set the default values for the
-* logging flags. Any logging flag that is not set in the build config
-* will default to `false`.
+* Visit {@link @warp-drive/core!build-config/debugging | @warp-drive/core debugging} for documentation of the debugging features.
 *
 * @module
 */

package/dist/babel-macros.js

@@ -1,4 +1,4 @@
-import { L as LOGGING } from './debugging-DgRWKeE4.js';
+import { L as LOGGING } from './debugging-4cD97Im5.js';
 import { C as CURRENT_FEATURES } from './canary-features-BUBNGiZ-.js';
 import { C as CURRENT_DEPRECATIONS } from './deprecations-vEj59ee0.js';
 

package/dist/cjs-set-config.cjs

@@ -342,57 +342,10 @@ function getFeatures(isProd) {
 }
 
 /**
- * # Log Instrumentation <Badge type="tip" text="debug only" />
+ * While build-config is its own package, it should always be
+ * used via `@warp-drive/core`.
  *
- * Many portions of the internals are helpfully instrumented with logging.
- * This instrumentation is always removed from production builds.
- *
- * Log instrumentation is "regionalized" to specific concepts and concerns
- * to enable you to enable/disable just the areas you are interested in.
- *
- * To activate a particular group of logs set the appropriate flag to `true`
- * either in your build config or via the runtime helper.
- *
- *
- * ## Runtime Activation
- *
- * ::: tip 💡 Just Works in browser Dev Tools!
- * No import is needed, and the logging config is preserved when the page is refreshed
- * :::
- *
- * ```ts
- * setWarpDriveLogging({
- *   LOG_CACHE: true,
- *   LOG_REQUESTS: true,
- * })
- * ```
- *
- * A runtime helper is attached to `globalThis` to enable activation of the logs
- * from anywhere in your application including from the devtools panel.
- *
- * The runtime helper overrides any build config settings for the given flag
- * for the current browser tab. It stores the configuration you give it in
- * `sessionStorage` so that it persists across page reloads of the current tab,
- * but not across browser tabs or windows.
- *
- * If you need to deactivate the logging, you can call the helper again with the
- * same flag set to `false` or just open a new tab/window.
- *
- * ## Buildtime Activation
- *
- * ```ts
- * setConfig(__dirname, app, {
- *   debug: {
- *     LOG_CACHE: true,
- *     LOG_REQUESTS: false,
- *     LOG_NOTIFICATIONS: true,
- *   }
- * });
- * ```
- *
- * The build config settings are used to set the default values for the
- * logging flags. Any logging flag that is not set in the build config
- * will default to `false`.
+ * Visit {@link @warp-drive/core!build-config/debugging | @warp-drive/core debugging} for documentation of the debugging features.
  *
  * @module
  */

package/dist/{debugging-DgRWKeE4.js → debugging-4cD97Im5.js}

@@ -1,55 +1,8 @@
 /**
- * # Log Instrumentation <Badge type="tip" text="debug only" />
+ * While build-config is its own package, it should always be
+ * used via `@warp-drive/core`.
  *
- * Many portions of the internals are helpfully instrumented with logging.
- * This instrumentation is always removed from production builds.
- *
- * Log instrumentation is "regionalized" to specific concepts and concerns
- * to enable you to enable/disable just the areas you are interested in.
- *
- * To activate a particular group of logs set the appropriate flag to `true`
- * either in your build config or via the runtime helper.
- *
- *
- * ## Runtime Activation
- *
- * ::: tip 💡 Just Works in browser Dev Tools!
- * No import is needed, and the logging config is preserved when the page is refreshed
- * :::
- *
- * ```ts
- * setWarpDriveLogging({
- *   LOG_CACHE: true,
- *   LOG_REQUESTS: true,
- * })
- * ```
- *
- * A runtime helper is attached to `globalThis` to enable activation of the logs
- * from anywhere in your application including from the devtools panel.
- *
- * The runtime helper overrides any build config settings for the given flag
- * for the current browser tab. It stores the configuration you give it in
- * `sessionStorage` so that it persists across page reloads of the current tab,
- * but not across browser tabs or windows.
- *
- * If you need to deactivate the logging, you can call the helper again with the
- * same flag set to `false` or just open a new tab/window.
- *
- * ## Buildtime Activation
- *
- * ```ts
- * setConfig(__dirname, app, {
- *   debug: {
- *     LOG_CACHE: true,
- *     LOG_REQUESTS: false,
- *     LOG_NOTIFICATIONS: true,
- *   }
- * });
- * ```
- *
- * The build config settings are used to set the default values for the
- * logging flags. Any logging flag that is not set in the build config
- * will default to `false`.
+ * Visit {@link @warp-drive/core!build-config/debugging | @warp-drive/core debugging} for documentation of the debugging features.
  *
  * @module
  */

package/dist/debugging.js

@@ -1 +1 @@
-export { D as DEBUG_RELATIONSHIP_NOTIFICATIONS, a as LOG_CACHE, e as LOG_CACHE_POLICY, j as LOG_GRAPH, i as LOG_IDENTIFIERS, k as LOG_INSTANCE_CACHE, l as LOG_METRIC_COUNTS, d as LOG_MUTATIONS, f as LOG_NOTIFICATIONS, c as LOG_OPERATIONS, b as LOG_PAYLOADS, m as LOG_REACT_SIGNAL_INTEGRATION, g as LOG_REQUESTS, h as LOG_REQUEST_STATUS, _ as __INTERNAL_LOG_NATIVE_MAP_SET_COUNTS } from './debugging-DgRWKeE4.js';
+export { D as DEBUG_RELATIONSHIP_NOTIFICATIONS, a as LOG_CACHE, e as LOG_CACHE_POLICY, j as LOG_GRAPH, i as LOG_IDENTIFIERS, k as LOG_INSTANCE_CACHE, l as LOG_METRIC_COUNTS, d as LOG_MUTATIONS, f as LOG_NOTIFICATIONS, c as LOG_OPERATIONS, b as LOG_PAYLOADS, m as LOG_REACT_SIGNAL_INTEGRATION, g as LOG_REQUESTS, h as LOG_REQUEST_STATUS, _ as __INTERNAL_LOG_NATIVE_MAP_SET_COUNTS } from './debugging-4cD97Im5.js';

package/dist/index.js

@@ -4,7 +4,7 @@ import fs from 'fs';
 import path from 'path';
 import { fileURLToPath } from 'url';
 import { C as CURRENT_FEATURES } from './canary-features-BUBNGiZ-.js';
-import { L as LOGGING } from './debugging-DgRWKeE4.js';
+import { L as LOGGING } from './debugging-4cD97Im5.js';
 import { buildMacros } from '@embroider/macros/src/babel.js';
 
 function getEnv(forceMode) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@warp-drive/build-config",
-  "version": "5.9.0-alpha.13",
+  "version": "5.9.0-alpha.15",
   "description": "(Legacy) Build Configuration for projects using WarpDrive",
   "keywords": [
     "ember-data",
@@ -43,7 +43,7 @@
     "semver": "^7.7.2"
   },
   "devDependencies": {
-    "@warp-drive/internal-config": "5.9.0-alpha.13",
+    "@warp-drive/internal-config": "5.9.0-alpha.15",
     "@types/babel__core": "^7.20.5",
     "@types/node": "^20.19.11",
     "@types/semver": "^7.7.1",