@object-ui/providers 17.5.0 → 17.6.0

package/CHANGELOG.md

@@ -1,5 +1,33 @@
 # @object-ui/providers — Changelog
 
+## 17.6.0
+
+### Patch Changes
+
+- 5458414: Publish relative import specifiers with explicit `.js` extensions so these six packages load under plain Node ESM.
+  
+  Node's ESM resolver does not extension-search relative specifiers and `tsc` never rewrites them, so an extensionless `./Foo` in the source shipped as an extensionless `./Foo` in `dist` and importing the package entry outside a bundler failed with `ERR_MODULE_NOT_FOUND`. Bundled consumers were unaffected. Unbundled consumers — plain Node ESM, an SSR host importing the package directly, anyone running the published tarball without a build step — can now import these entries, and so can the downstream `@object-ui/plugin-*` packages that evaluate through `mobile`, `permissions` and `providers`.
+- Updated dependencies [88085e3]
+- Updated dependencies [279fb13]
+- Updated dependencies [1184192]
+- Updated dependencies [a2a9747]
+- Updated dependencies [af5e292]
+- Updated dependencies [7f96b10]
+- Updated dependencies [f1d4748]
+- Updated dependencies [578e025]
+- Updated dependencies [598c89a]
+- Updated dependencies [b8b9af4]
+- Updated dependencies [97abb24]
+- Updated dependencies [deb157a]
+- Updated dependencies [d2ce342]
+- Updated dependencies [9695da7]
+- Updated dependencies [58b8346]
+- Updated dependencies [3cf4de0]
+- Updated dependencies [c9dc811]
+- Updated dependencies [a0b9e91]
+- Updated dependencies [99bd015]
+  - @object-ui/types@17.6.0
+
 ## 17.5.0
 
 ### Patch Changes

package/dist/DataSourceProvider.d.ts

@@ -1,4 +1,4 @@
-import type { DataSourceProviderProps } from './types';
+import type { DataSourceProviderProps } from './types.js';
 /**
  * DataSourceProvider - Generic data source context
  *

package/dist/MetadataProvider.d.ts

@@ -1,4 +1,4 @@
-import type { MetadataProviderProps } from './types';
+import type { MetadataProviderProps } from './types.js';
 interface MetadataContextValue {
     metadata: any;
     loading: boolean;

package/dist/ThemeProvider.d.ts

@@ -1,4 +1,4 @@
-import type { ThemePreference, ThemeProviderProps } from './types';
+import type { ThemePreference, ThemeProviderProps } from './types.js';
 interface ThemeContextValue {
     theme: ThemePreference;
     setTheme: (theme: ThemePreference) => void;

package/dist/UploadProvider.js

@@ -199,7 +199,6 @@ async function uploadWithProgress(fetchFn, url, body, options) {
     const maxRetries = options.maxRetries ?? 3;
     const baseDelay = options.retryDelayMs ?? 500;
     let attempt = 0;
-    // eslint-disable-next-line no-constant-condition
     while (true) {
         if (options.signal?.aborted)
             throw new DOMException('aborted', 'AbortError');

package/dist/index.d.ts

@@ -3,9 +3,9 @@
  *
  * Reusable context providers for ObjectUI applications
  */
-export { DataSourceProvider, useDataSource } from './DataSourceProvider';
-export { MetadataProvider, useMetadata } from './MetadataProvider';
-export { ThemeProvider, useTheme } from './ThemeProvider';
-export { UploadProvider, useUpload, createObjectUrlAdapter, createS3Adapter, createAzureBlobAdapter, createObjectStackUploadAdapter, } from './UploadProvider';
-export type { DataSourceProviderProps, MetadataProviderProps, ThemeProviderProps, ThemePreference, } from './types';
-export type { UploadAdapter, UploadOptions, UploadResult, UploadProviderProps, S3AdapterOptions, AzureBlobAdapterOptions, ObjectStackUploadAdapterOptions, } from './UploadProvider';
+export { DataSourceProvider, useDataSource } from './DataSourceProvider.js';
+export { MetadataProvider, useMetadata } from './MetadataProvider.js';
+export { ThemeProvider, useTheme } from './ThemeProvider.js';
+export { UploadProvider, useUpload, createObjectUrlAdapter, createS3Adapter, createAzureBlobAdapter, createObjectStackUploadAdapter, } from './UploadProvider.js';
+export type { DataSourceProviderProps, MetadataProviderProps, ThemeProviderProps, ThemePreference, } from './types.js';
+export type { UploadAdapter, UploadOptions, UploadResult, UploadProviderProps, S3AdapterOptions, AzureBlobAdapterOptions, ObjectStackUploadAdapterOptions, } from './UploadProvider.js';

package/dist/index.js

@@ -3,7 +3,7 @@
  *
  * Reusable context providers for ObjectUI applications
  */
-export { DataSourceProvider, useDataSource } from './DataSourceProvider';
-export { MetadataProvider, useMetadata } from './MetadataProvider';
-export { ThemeProvider, useTheme } from './ThemeProvider';
-export { UploadProvider, useUpload, createObjectUrlAdapter, createS3Adapter, createAzureBlobAdapter, createObjectStackUploadAdapter, } from './UploadProvider';
+export { DataSourceProvider, useDataSource } from './DataSourceProvider.js';
+export { MetadataProvider, useMetadata } from './MetadataProvider.js';
+export { ThemeProvider, useTheme } from './ThemeProvider.js';
+export { UploadProvider, useUpload, createObjectUrlAdapter, createS3Adapter, createAzureBlobAdapter, createObjectStackUploadAdapter, } from './UploadProvider.js';

package/dist/types.d.ts

@@ -1,5 +1,5 @@
 import type { ReactNode } from 'react';
-import type { ThemeModeSchema } from '@objectstack/spec/ui';
+import type { ThemeMode } from '@object-ui/types';
 export interface DataSourceProviderProps {
     dataSource: any;
     children: ReactNode;
@@ -9,31 +9,33 @@ export interface MetadataProviderProps {
     children: ReactNode;
 }
 /**
- * The theme MODE this provider stores and applies: the spec's `ThemeMode`
- * vocabulary (`auto | light | dark`) plus the one legacy spelling this package
- * still accepts.
+ * The theme MODE this provider stores and applies: the `ThemeMode` vocabulary
+ * (`auto | light | dark`) plus the one legacy spelling this package still
+ * accepts.
  *
  * Named `ThemePreference`, not `Theme` (objectui#3161, objectstack#4115 ledger
- * batch 7). `@objectstack/spec/ui` owns `Theme` for a whole theme DOCUMENT —
- * `{ name, label, mode, colors: { primary, background, … }, typography, … }` —
- * so the local declaration was not a drifted copy of the spec's `Theme` at all;
- * it was the spec's `Theme['mode']` under the spec's `Theme` name, which is the
- * more misleading of the two failures: a session reading `Theme` here would
- * conclude an ObjectStack theme is a string. The spec's own name for this
- * concept, `ThemeMode`, is exported too, so THAT name could not be taken either
- * (the "run the new name past the guard first" rule from objectui#3169 — it
- * would have traded one collision for another); and it would be wrong anyway,
- * because of `'system'`.
+ * batch 7). `Theme` names a whole theme DOCUMENT — `{ name, label, mode,
+ * colors: { primary, background, … }, typography, … }` — so the old local
+ * declaration was not a drifted copy of that document type at all; it was
+ * `Theme['mode']` under `Theme`'s name, which is the more misleading of the
+ * two failures: a session reading `Theme` here would conclude an ObjectStack
+ * theme is a string. `ThemeMode`, the vocabulary's own name for what this
+ * really is, could not be taken either (the "run the new name past the guard
+ * first" rule from objectui#3169 — it would have traded one collision for
+ * another); and it would be wrong anyway, because of `'system'`.
  *
- * The three real modes are now the spec enum rather than a hand copy of it, so
- * a mode the spec adds arrives here and `ThemeProvider`'s branch must handle
- * it. `'system'` stays as an explicit local union member: it is the pre-spec
- * spelling of `auto`, still sitting in users' `localStorage`, and the provider
- * treats the two identically (#2942, pinned in `theme-mode-spec-parity`).
- * Reached through the schema's `_zod` carrier so this package takes no zod
- * dependency — same technique as `packages/react/src/spec-input.ts`.
+ * Derivation history (objectui#5716): this union was born reading the spec's
+ * `ThemeModeSchema` through its `_zod` input carrier. The spec then retired
+ * its whole theme module (objectstack#10485), objectui assumed ownership of
+ * the theme document types, and the mode vocabulary's owner is now
+ * `@object-ui/types` (`ThemeMode`, with the `THEME_MODES` runtime witness) —
+ * so the derivation reads from there. A mode the owner adds still arrives
+ * here and `ThemeProvider`'s branch must handle it. `'system'` stays as an
+ * explicit local union member: it is the pre-spec spelling of `auto`, still
+ * sitting in users' `localStorage`, and the provider treats the two
+ * identically (#2942, pinned in `theme-mode-spec-parity`).
  */
-export type ThemePreference = (typeof ThemeModeSchema)['_zod']['input'] | 'system';
+export type ThemePreference = ThemeMode | 'system';
 export interface ThemeProviderProps {
     defaultTheme?: ThemePreference;
     storageKey?: string;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@object-ui/providers",
-  "version": "17.5.0",
+  "version": "17.6.0",
   "type": "module",
   "license": "MIT",
   "description": "Reusable context providers for ObjectUI applications",
@@ -24,8 +24,8 @@
     }
   },
   "dependencies": {
-    "@objectstack/spec": "^17.0.0-rc.6",
-    "@object-ui/types": "17.5.0"
+    "@objectstack/spec": "^17.0.0",
+    "@object-ui/types": "17.6.0"
   },
   "peerDependencies": {
     "react": "^18.0.0 || ^19.0.0",