@oxyhq/bloom 0.8.4 → 0.8.5

package/lib/commonjs/theme/native-root-vars.js

@@ -15,8 +15,7 @@ exports.applyNativeRootVars = applyNativeRootVars;
  *     `exports` `import`/`require` conditions to `lib/.../native-root-vars.js`.
  *
  * It deliberately does NOT import `react-native-css/native-internal`. That subpath
- * is native-only: it has no web build, and react-native-css is not even a Bloom
- * dependency. Statically importing it from a file a web bundler resolves breaks
+ * is native-only. Statically importing it from a file a web bundler resolves breaks
  * module resolution outright (the original report: `Rolldown failed to resolve
  * import "react-native-css/native-internal" from .../native-root-vars.js`).
  * Importing it from a file a consumer's `tsc` resolves breaks type-check (TS2307).

package/lib/commonjs/theme/native-root-vars.js.map

@@ -1 +1 @@
-{"version":3,"names":["applyNativeRootVars","_colorPreset","_mode"],"sourceRoot":"../../../src","sources":["theme/native-root-vars.ts"],"mappings":";;;;;;AAEA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACO,SAASA,mBAAmBA,CAACC,YAA0B,EAAEC,KAAuB,EAAQ;EAC7F;EACA;AAAA","ignoreList":[]}
+{"version":3,"names":["applyNativeRootVars","_colorPreset","_mode"],"sourceRoot":"../../../src","sources":["theme/native-root-vars.ts"],"mappings":";;;;;;AAEA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACO,SAASA,mBAAmBA,CAACC,YAA0B,EAAEC,KAAuB,EAAQ;EAC7F;EACA;AAAA","ignoreList":[]}

package/lib/commonjs/theme/native-root-vars.native.js

@@ -17,11 +17,11 @@ var _tokenRegistry = require("./token-registry.js");
 // `node_modules/@oxyhq/bloom/src/**`, and TypeScript does NOT auto-pick-up
 // ambient `.d.ts` files that live under `node_modules`, so
 // `react-native-css/native-internal` is unresolved (TS2307) unless the reference
-// travels with the source. react-native-css is intentionally NOT a Bloom
-// dependency — it arrives transitively via a host's NativeWind 5 install, or is
-// absent entirely for NativeWind 4 consumers — so the ambient declaration is the
-// only thing that can type this import, and it MUST reach the consumer. The
-// directive ships raw in `src/` (Bloom publishes `files: ["src", "lib"]`).
+// travels with the source. Bloom now declares react-native-css directly because
+// this native source imports it; the ambient declaration still travels with
+// `src/` so consumer TypeScript programs that read Bloom source see the exact
+// subpath shape. The directive ships raw in `src/` (Bloom publishes
+// `files: ["src", "lib"]`).
 
 /**
  * Publish the active color preset's CSS custom properties into react-native-css's

package/lib/module/theme/native-root-vars.js

@@ -11,8 +11,7 @@
  *     `exports` `import`/`require` conditions to `lib/.../native-root-vars.js`.
  *
  * It deliberately does NOT import `react-native-css/native-internal`. That subpath
- * is native-only: it has no web build, and react-native-css is not even a Bloom
- * dependency. Statically importing it from a file a web bundler resolves breaks
+ * is native-only. Statically importing it from a file a web bundler resolves breaks
  * module resolution outright (the original report: `Rolldown failed to resolve
  * import "react-native-css/native-internal" from .../native-root-vars.js`).
  * Importing it from a file a consumer's `tsc` resolves breaks type-check (TS2307).

package/lib/module/theme/native-root-vars.js.map

@@ -1 +1 @@
-{"version":3,"names":["applyNativeRootVars","_colorPreset","_mode"],"sourceRoot":"../../../src","sources":["theme/native-root-vars.ts"],"mappings":";;AAEA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA,OAAO,SAASA,mBAAmBA,CAACC,YAA0B,EAAEC,KAAuB,EAAQ;EAC7F;EACA;AAAA","ignoreList":[]}
+{"version":3,"names":["applyNativeRootVars","_colorPreset","_mode"],"sourceRoot":"../../../src","sources":["theme/native-root-vars.ts"],"mappings":";;AAEA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA,OAAO,SAASA,mBAAmBA,CAACC,YAA0B,EAAEC,KAAuB,EAAQ;EAC7F;EACA;AAAA","ignoreList":[]}

package/lib/module/theme/native-root-vars.native.js

@@ -11,11 +11,11 @@
 // `node_modules/@oxyhq/bloom/src/**`, and TypeScript does NOT auto-pick-up
 // ambient `.d.ts` files that live under `node_modules`, so
 // `react-native-css/native-internal` is unresolved (TS2307) unless the reference
-// travels with the source. react-native-css is intentionally NOT a Bloom
-// dependency — it arrives transitively via a host's NativeWind 5 install, or is
-// absent entirely for NativeWind 4 consumers — so the ambient declaration is the
-// only thing that can type this import, and it MUST reach the consumer. The
-// directive ships raw in `src/` (Bloom publishes `files: ["src", "lib"]`).
+// travels with the source. Bloom now declares react-native-css directly because
+// this native source imports it; the ambient declaration still travels with
+// `src/` so consumer TypeScript programs that read Bloom source see the exact
+// subpath shape. The directive ships raw in `src/` (Bloom publishes
+// `files: ["src", "lib"]`).
 import { rootVariables } from 'react-native-css/native-internal';
 import { getResolvedTokens } from "./token-registry.js";
 

package/lib/typescript/commonjs/theme/native-root-vars.d.ts

@@ -10,8 +10,7 @@ import { type AppColorName } from './color-presets';
  *     `exports` `import`/`require` conditions to `lib/.../native-root-vars.js`.
  *
  * It deliberately does NOT import `react-native-css/native-internal`. That subpath
- * is native-only: it has no web build, and react-native-css is not even a Bloom
- * dependency. Statically importing it from a file a web bundler resolves breaks
+ * is native-only. Statically importing it from a file a web bundler resolves breaks
  * module resolution outright (the original report: `Rolldown failed to resolve
  * import "react-native-css/native-internal" from .../native-root-vars.js`).
  * Importing it from a file a consumer's `tsc` resolves breaks type-check (TS2307).

package/lib/typescript/commonjs/theme/native-root-vars.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"native-root-vars.d.ts","sourceRoot":"","sources":["../../../../src/theme/native-root-vars.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,KAAK,YAAY,EAAE,MAAM,iBAAiB,CAAC;AAEpD;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA8BG;AACH,wBAAgB,mBAAmB,CAAC,YAAY,EAAE,YAAY,EAAE,KAAK,EAAE,OAAO,GAAG,MAAM,GAAG,IAAI,CAG7F"}
+{"version":3,"file":"native-root-vars.d.ts","sourceRoot":"","sources":["../../../../src/theme/native-root-vars.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,KAAK,YAAY,EAAE,MAAM,iBAAiB,CAAC;AAEpD;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA6BG;AACH,wBAAgB,mBAAmB,CAAC,YAAY,EAAE,YAAY,EAAE,KAAK,EAAE,OAAO,GAAG,MAAM,GAAG,IAAI,CAG7F"}

package/lib/typescript/module/theme/native-root-vars.d.ts

@@ -10,8 +10,7 @@ import { type AppColorName } from './color-presets';
  *     `exports` `import`/`require` conditions to `lib/.../native-root-vars.js`.
  *
  * It deliberately does NOT import `react-native-css/native-internal`. That subpath
- * is native-only: it has no web build, and react-native-css is not even a Bloom
- * dependency. Statically importing it from a file a web bundler resolves breaks
+ * is native-only. Statically importing it from a file a web bundler resolves breaks
  * module resolution outright (the original report: `Rolldown failed to resolve
  * import "react-native-css/native-internal" from .../native-root-vars.js`).
  * Importing it from a file a consumer's `tsc` resolves breaks type-check (TS2307).

package/lib/typescript/module/theme/native-root-vars.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"native-root-vars.d.ts","sourceRoot":"","sources":["../../../../src/theme/native-root-vars.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,KAAK,YAAY,EAAE,MAAM,iBAAiB,CAAC;AAEpD;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA8BG;AACH,wBAAgB,mBAAmB,CAAC,YAAY,EAAE,YAAY,EAAE,KAAK,EAAE,OAAO,GAAG,MAAM,GAAG,IAAI,CAG7F"}
+{"version":3,"file":"native-root-vars.d.ts","sourceRoot":"","sources":["../../../../src/theme/native-root-vars.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,KAAK,YAAY,EAAE,MAAM,iBAAiB,CAAC;AAEpD;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA6BG;AACH,wBAAgB,mBAAmB,CAAC,YAAY,EAAE,YAAY,EAAE,KAAK,EAAE,OAAO,GAAG,MAAM,GAAG,IAAI,CAG7F"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@oxyhq/bloom",
-  "version": "0.8.4",
+  "version": "0.8.5",
   "description": "Bloom UI — Oxy ecosystem component library for React Native + Expo + Web",
   "main": "lib/commonjs/index.js",
   "module": "lib/module/index.js",
@@ -871,6 +871,7 @@
   },
   "dependencies": {
     "nanoid": "^5.1.5",
+    "react-native-css": "3.0.7",
     "react-remove-scroll-bar": "^2.3.8"
   }
 }

package/src/react-native-css.d.ts

@@ -1,21 +1,20 @@
 /**
  * Ambient declaration for `react-native-css/native-internal`.
  *
- * react-native-css is NOT a Bloom dependency — it arrives transitively via the
- * host app's NativeWind install (NativeWind 5 is built on react-native-css@3).
- * Bloom's `native-root-vars.native.ts` statically imports `rootVariables` from
- * this subpath so Metro resolves the `import` export condition to the package's
+ * Bloom's native theme bridge statically imports `rootVariables` from this
+ * subpath so Metro resolves the `import` export condition to the package's
  * `module` build — the SAME family instance the react-native-css renderer
- * (`varResolver`) subscribes to. A runtime `require()` would resolve the
- * `require` condition to the separate `commonjs` build, whose `rootVariables`
- * is a distinct, un-observed family instance (see the file-level comment in
- * `native-root-vars.native.ts`).
+ * (`varResolver`) subscribes to. `react-native-css` is a direct Bloom dependency
+ * because this subpath is imported from published native source, including
+ * NativeWind 4 consumers whose test/native resolvers still select `.native.ts`.
+ * A runtime `require()` would resolve the `require` condition to the separate
+ * `commonjs` build, whose `rootVariables` is a distinct, un-observed family
+ * instance (see the file-level comment in `native-root-vars.native.ts`).
  *
- * Because the package isn't installed in Bloom, `tsc` can't see its published
- * types, so we declare the slice we use here — typed to match react-native-css
- * @3.0.7's `dist/typescript/.../native-internal/root.d.ts` exactly (no `any`,
- * no shims). This file is `.native`-only in spirit; the web fork never imports
- * the subpath, so on web bundlers the static import is never reached.
+ * We declare the slice we use here — typed to match react-native-css @3.0.7's
+ * `dist/typescript/.../native-internal/root.d.ts` exactly (no `any`, no shims).
+ * This file is `.native`-only in spirit; the web fork never imports the subpath,
+ * so on web bundlers the static import is never reached.
  */
 declare module 'react-native-css/native-internal' {
   /**

package/src/theme/native-root-vars.native.ts

@@ -9,11 +9,11 @@
 // `node_modules/@oxyhq/bloom/src/**`, and TypeScript does NOT auto-pick-up
 // ambient `.d.ts` files that live under `node_modules`, so
 // `react-native-css/native-internal` is unresolved (TS2307) unless the reference
-// travels with the source. react-native-css is intentionally NOT a Bloom
-// dependency — it arrives transitively via a host's NativeWind 5 install, or is
-// absent entirely for NativeWind 4 consumers — so the ambient declaration is the
-// only thing that can type this import, and it MUST reach the consumer. The
-// directive ships raw in `src/` (Bloom publishes `files: ["src", "lib"]`).
+// travels with the source. Bloom now declares react-native-css directly because
+// this native source imports it; the ambient declaration still travels with
+// `src/` so consumer TypeScript programs that read Bloom source see the exact
+// subpath shape. The directive ships raw in `src/` (Bloom publishes
+// `files: ["src", "lib"]`).
 import { rootVariables } from 'react-native-css/native-internal';
 
 import { type AppColorName } from './color-presets';

package/src/theme/native-root-vars.ts

@@ -11,8 +11,7 @@ import { type AppColorName } from './color-presets';
  *     `exports` `import`/`require` conditions to `lib/.../native-root-vars.js`.
  *
  * It deliberately does NOT import `react-native-css/native-internal`. That subpath
- * is native-only: it has no web build, and react-native-css is not even a Bloom
- * dependency. Statically importing it from a file a web bundler resolves breaks
+ * is native-only. Statically importing it from a file a web bundler resolves breaks
  * module resolution outright (the original report: `Rolldown failed to resolve
  * import "react-native-css/native-internal" from .../native-root-vars.js`).
  * Importing it from a file a consumer's `tsc` resolves breaks type-check (TS2307).