@hook-sdk/template 0.23.0 → 0.23.1

package/dist/index.d.cts

@@ -213,13 +213,21 @@ declare function AppRoot(props: AppRootProps): react_jsx_runtime.JSX.Element;
  * Two independent signals must agree:
  *
  *   1. Build-time: `import.meta.env.VITE_HOOK_DEV_TOOLS === '1'`. Vite folds
- *      this constant at build time — when unset, the entire dev tree is
- *      tree-shaken from the prod bundle (sideEffects:false in package.json
- *      makes that effective). Set `VITE_HOOK_DEV_TOOLS=1` only in
- *      `.env.staging` builds.
+ *      this constant at the consumer app's build time — when unset, the
+ *      entire dev tree is tree-shaken from the prod bundle. Set
+ *      `VITE_HOOK_DEV_TOOLS=1` only in the staging build env.
  *
  *   2. Runtime: hostname must be staging-ish. Belt-and-suspenders against
  *      a misconfigured build that somehow ships the FAB to prod.
+ *
+ * IMPORTANT: the env access MUST be the literal token
+ * `import.meta.env.VITE_HOOK_DEV_TOOLS`. Vite's static replacement is a
+ * text substitution that only fires on this exact form. Going through a
+ * local alias (`const meta = import.meta; meta.env.X`) defeats the
+ * substitution and the consumer bundle ends up with `undefined` regardless
+ * of what the build env actually has set. See `../vite-env.d.ts` for the
+ * ambient ImportMeta augmentation that keeps TypeScript happy without a
+ * cast at the access site.
  */
 declare function isDevToolsEnabled(): boolean;
 

package/dist/index.d.ts

@@ -213,13 +213,21 @@ declare function AppRoot(props: AppRootProps): react_jsx_runtime.JSX.Element;
  * Two independent signals must agree:
  *
  *   1. Build-time: `import.meta.env.VITE_HOOK_DEV_TOOLS === '1'`. Vite folds
- *      this constant at build time — when unset, the entire dev tree is
- *      tree-shaken from the prod bundle (sideEffects:false in package.json
- *      makes that effective). Set `VITE_HOOK_DEV_TOOLS=1` only in
- *      `.env.staging` builds.
+ *      this constant at the consumer app's build time — when unset, the
+ *      entire dev tree is tree-shaken from the prod bundle. Set
+ *      `VITE_HOOK_DEV_TOOLS=1` only in the staging build env.
  *
  *   2. Runtime: hostname must be staging-ish. Belt-and-suspenders against
  *      a misconfigured build that somehow ships the FAB to prod.
+ *
+ * IMPORTANT: the env access MUST be the literal token
+ * `import.meta.env.VITE_HOOK_DEV_TOOLS`. Vite's static replacement is a
+ * text substitution that only fires on this exact form. Going through a
+ * local alias (`const meta = import.meta; meta.env.X`) defeats the
+ * substitution and the consumer bundle ends up with `undefined` regardless
+ * of what the build env actually has set. See `../vite-env.d.ts` for the
+ * ambient ImportMeta augmentation that keeps TypeScript happy without a
+ * cast at the access site.
  */
 declare function isDevToolsEnabled(): boolean;
 

package/dist/index.js

@@ -2099,8 +2099,7 @@ function I18nProvider({
 
 // src/dev/env.ts
 function isDevToolsEnabled() {
-  const meta = import.meta;
-  if (meta.env?.VITE_HOOK_DEV_TOOLS !== "1") return false;
+  if (import.meta.env.VITE_HOOK_DEV_TOOLS !== "1") return false;
   if (typeof window === "undefined") return false;
   const host = window.location.hostname;
   return host.includes(".staging.") || host === "localhost" || host === "127.0.0.1";