@ssa-ui-kit/core 3.20.0 → 3.20.1

package/dist/index.js

@@ -10356,14 +10356,26 @@ __webpack_require__.d(Drawer_index_parts_namespaceObject, {
  * `if (true) return;` in the published bundle, silently, while still firing in
  * this repo's Jest runs.
  *
- * The `typeof process` guard is what makes leaving the value unresolved safe:
- * a runtime that never defines `process` (a plain `<script type="module">`, a
- * bare worker) gets silence rather than a ReferenceError. Erring toward silence
- * is right — no diagnostic is worth crashing a consumer over.
+ * The expression must be a *bare* `process.env.NODE_ENV`, with nothing guarding
+ * it. Bundlers substitute that literal token sequence and nothing else: a
+ * `typeof process === 'undefined'` check in front of it is left untouched, so
+ * in a browser — where there is no `process` global — the guard returns `false`
+ * before the correctly-substituted value is ever reached, and every diagnostic
+ * goes dark for exactly the consumers they exist for. Same bug as the one
+ * above, entered from the other side.
+ *
+ * `try/catch` keeps the guarantee the guard was there for: a runtime that never
+ * defines `process` *and* whose bundler substituted nothing (a plain
+ * `<script type="module">`, a bare worker) throws a ReferenceError, which is
+ * caught here as silence rather than a crash. Erring toward silence is right —
+ * no diagnostic is worth crashing a consumer over.
  */
 const isDevEnvironment = () => {
-  if (typeof process === 'undefined' || !process.env) return false;
-  return process.env.NODE_ENV !== 'production';
+  try {
+    return process.env.NODE_ENV !== 'production';
+  } catch {
+    return false;
+  }
 };
 ;// ./src/utils/detectDuplicateInstance.ts
 /**

package/dist/index.mjs

@@ -10085,14 +10085,26 @@ __webpack_require__.d(Drawer_index_parts_namespaceObject, {
  * `if (true) return;` in the published bundle, silently, while still firing in
  * this repo's Jest runs.
  *
- * The `typeof process` guard is what makes leaving the value unresolved safe:
- * a runtime that never defines `process` (a plain `<script type="module">`, a
- * bare worker) gets silence rather than a ReferenceError. Erring toward silence
- * is right — no diagnostic is worth crashing a consumer over.
+ * The expression must be a *bare* `process.env.NODE_ENV`, with nothing guarding
+ * it. Bundlers substitute that literal token sequence and nothing else: a
+ * `typeof process === 'undefined'` check in front of it is left untouched, so
+ * in a browser — where there is no `process` global — the guard returns `false`
+ * before the correctly-substituted value is ever reached, and every diagnostic
+ * goes dark for exactly the consumers they exist for. Same bug as the one
+ * above, entered from the other side.
+ *
+ * `try/catch` keeps the guarantee the guard was there for: a runtime that never
+ * defines `process` *and* whose bundler substituted nothing (a plain
+ * `<script type="module">`, a bare worker) throws a ReferenceError, which is
+ * caught here as silence rather than a crash. Erring toward silence is right —
+ * no diagnostic is worth crashing a consumer over.
  */
 const isDevEnvironment = () => {
-  if (typeof process === 'undefined' || !process.env) return false;
-  return process.env.NODE_ENV !== 'production';
+  try {
+    return process.env.NODE_ENV !== 'production';
+  } catch {
+    return false;
+  }
 };
 ;// ./src/utils/detectDuplicateInstance.ts
 /**