@matteoaliano/forest-ui 1.2.3 → 1.2.4

package/dist/theme.d.mts

@@ -387,6 +387,7 @@ declare const container: {
     readonly maxWidthDesktop: 1280;
     readonly paddingDesktop: 32;
     readonly paddingMobile: 16;
+    readonly shellRadius: 24;
 };
 declare const widths: {
     readonly xxs: 320;

package/dist/theme.d.ts

@@ -387,6 +387,7 @@ declare const container: {
     readonly maxWidthDesktop: 1280;
     readonly paddingDesktop: 32;
     readonly paddingMobile: 16;
+    readonly shellRadius: 24;
 };
 declare const widths: {
     readonly xxs: 320;

package/dist/theme.js

@@ -1148,7 +1148,13 @@ function buildComponents(tokens2) {
             borderBottomLeftRadius: radius4.md,
             borderBottomRightRadius: radius4.md,
             opacity: 0.75,
-            boxShadow: "inset 0 2px 4px 0 rgba(0,0,0,0.3)",
+            // The pressed-in cue is carried by the flattened bevel (bottom
+            // border 4px -> 1px) alone in light mode. On the dark-mode face
+            // that geometry reads too faintly, so it keeps the inner shadow.
+            boxShadow: "none",
+            ...theme.applyStyles("dark", {
+              boxShadow: "inset 0 2px 4px 0 rgba(0,0,0,0.3)"
+            }),
             "&::before": { display: "none" },
             // Stays pressed on hover — no bevel re-raise, no brightness lift.
             "&:hover": {
@@ -3184,7 +3190,12 @@ var display = {
 var container = {
   maxWidthDesktop: 1280,
   paddingDesktop: 32,
-  paddingMobile: 16
+  paddingMobile: 16,
+  // Corner radius of the App Shell's content surface where it meets the
+  // chrome. Deliberately a layout value rather than a step on the `radius`
+  // scale: that scale governs components (and the sharper alkemy+ preset caps
+  // it at 12), so a 24 sitting in it would misread as a component radius.
+  shellRadius: 24
 };
 var widths = {
   xxs: 320,