@symbiote-native/sharing 0.0.1 → 0.2.0

package/build/angular/index.js

@@ -1,4 +1,4 @@
 // @symbiote-native/sharing/angular: the Angular entry over the framework-agnostic core. Same
 // reasoning as the React/Vue entries — no per-instance state or event stream to wrap in a
 // service, so this is a plain re-export.
-export * from '../core';
+export * from '../core/index.js';

package/build/core/index.js

@@ -1 +1 @@
-export { isAvailableAsync, shareAsync } from './sharing';
+export { isAvailableAsync, shareAsync } from './sharing.js';

package/build/core/sharing.js

@@ -1,5 +1,5 @@
 import { UnavailabilityError } from 'expo-modules-core';
-import { expoSharing } from './native-module';
+import { expoSharing } from './native-module.js';
 const NATIVE_MODULE_NAME = 'expo-sharing';
 /**
  * Whether the share sheet can be opened on this device. Resolves `true` on Android and iOS.

package/build/react/index.js

@@ -3,4 +3,4 @@
 // hook could own or clean up — so this is a plain re-export, the same shape
 // packages/secure-store's React entry has for the same reason. The one part of expo-sharing that
 // WOULD need a hook (incoming share) is out of scope here; see the README.
-export * from '../core';
+export * from '../core/index.js';

package/build/svelte/index.d.ts

@@ -0,0 +1 @@
+export * from '../core';

package/build/svelte/index.js

@@ -0,0 +1,7 @@
+// @symbiote-native/sharing/svelte: the Svelte entry over the framework-agnostic core.
+// Both exports are stateless free functions — no per-instance state, no event stream, nothing a
+// rune could own or clean up — so this is a plain re-export. The one part of expo-sharing that
+// WOULD need lifecycle (incoming share) is out of scope here; see the README. Svelte's lifecycle
+// bucket is `runes/` (adapters/svelte/src/runes — never React's `hooks` or Vue's
+// `composables`), and this package has none to fill.
+export * from '../core/index.js';

package/build/vue/index.js

@@ -1,4 +1,4 @@
 // @symbiote-native/sharing/vue: the Vue entry over the framework-agnostic core. Same reasoning
 // as the React entry — no per-instance state or event stream to wire onto Vue's reactivity, so
 // this is a plain re-export.
-export * from '../core';
+export * from '../core/index.js';

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@symbiote-native/sharing",
-  "version": "0.0.1",
+  "version": "0.2.0",
   "description": "expo-sharing wrapped for SymbioteNative — one framework-agnostic core, built once and reachable from the React, Vue, and Angular adapters. Opens the platform share sheet for a local file.",
   "license": "MIT",
   "repository": {
@@ -30,6 +30,10 @@
       "types": "./build/react/index.d.ts",
       "default": "./build/react/index.js"
     },
+    "./svelte": {
+      "types": "./build/svelte/index.d.ts",
+      "default": "./build/svelte/index.js"
+    },
     "./angular": {
       "types": "./build-ngc/angular/index.d.ts",
       "react-native": "./build-ngc/angular/index.js",
@@ -40,7 +44,10 @@
     "src",
     "build",
     "build-ngc",
-    "native-link.json"
+    "native-link.json",
+    "!src/**/*.test.*",
+    "!src/**/*.spec.*",
+    "!src/**/*.detox.*"
   ],
   "publishConfig": {
     "access": "public"
@@ -50,15 +57,17 @@
     "expo-modules-core": "57.0.5"
   },
   "peerDependencies": {
+    "@symbiote-native/angular": ">=0.6.2",
     "@symbiote-native/engine": ">=0.1.7",
+    "@symbiote-native/react": ">=0.2.8",
+    "@symbiote-native/svelte": ">=0.1.0",
+    "@symbiote-native/vue": ">=0.3.8",
     "@angular/core": ">=20",
     "@vue/runtime-core": "^3.5.13",
     "react": ">=19.0.0",
     "react-native": ">=0.86",
-    "vue": ">=3.5.0",
-    "@symbiote-native/angular": "0.6.1",
-    "@symbiote-native/react": "0.2.8",
-    "@symbiote-native/vue": "0.3.8"
+    "svelte": ">=5.56.0",
+    "vue": ">=3.5.0"
   },
   "peerDependenciesMeta": {
     "@symbiote-native/angular": {
@@ -67,6 +76,9 @@
     "@symbiote-native/react": {
       "optional": true
     },
+    "@symbiote-native/svelte": {
+      "optional": true
+    },
     "@symbiote-native/vue": {
       "optional": true
     },
@@ -79,24 +91,29 @@
     "react": {
       "optional": true
     },
+    "svelte": {
+      "optional": true
+    },
     "vue": {
       "optional": true
     }
   },
   "devDependencies": {
-    "@angular/compiler": "^22",
-    "@angular/compiler-cli": "^22",
-    "@angular/core": "^22",
+    "@angular/compiler": "~22.0.8",
+    "@angular/compiler-cli": "~22.0.8",
+    "@angular/core": "~22.0.8",
     "@types/node": "^26.0.0",
     "@types/react": "^19.2.0",
     "@vue/runtime-core": "^3.5.13",
     "react": "19.2.3",
+    "svelte": "^5.56.0",
     "typescript": "~6.0.0",
+    "@symbiote-native/angular": "0.7.0",
+    "@symbiote-native/engine": "0.2.0",
+    "@symbiote-native/react": "0.3.0",
+    "@symbiote-native/svelte": "0.2.0",
     "@symbiote-native/test-utils": "0.1.6",
-    "@symbiote-native/react": "0.2.8",
-    "@symbiote-native/engine": "0.1.7",
-    "@symbiote-native/vue": "0.3.8",
-    "@symbiote-native/angular": "0.6.1"
+    "@symbiote-native/vue": "0.4.0"
   },
   "scripts": {
     "typecheck": "tsc --build",

package/src/svelte/index.ts

@@ -0,0 +1,7 @@
+// @symbiote-native/sharing/svelte: the Svelte entry over the framework-agnostic core.
+// Both exports are stateless free functions — no per-instance state, no event stream, nothing a
+// rune could own or clean up — so this is a plain re-export. The one part of expo-sharing that
+// WOULD need lifecycle (incoming share) is out of scope here; see the README. Svelte's lifecycle
+// bucket is `runes/` (adapters/svelte/src/runes — never React's `hooks` or Vue's
+// `composables`), and this package has none to fill.
+export * from '../core';

package/src/core/sharing.test.ts

@@ -1,105 +0,0 @@
-import { afterEach, describe, expect, it, vi } from 'vitest';
-
-const FAKE_NATIVE_SHARING = {
-  shareAsync: vi.fn(async () => undefined),
-};
-
-// The real ExpoSharing native module only exists on device — resolving it via
-// requireNativeModule() at import time would throw in this headless run, so the module-lookup
-// file is faked in place of expo-modules-core's runtime resolution, the same pattern
-// packages/secure-store/src/core/secure-store.test.ts uses.
-vi.mock('./native-module', () => ({
-  expoSharing: FAKE_NATIVE_SHARING,
-}));
-
-// expo-modules-core's real entry transitively imports 'react-native', whose Flow-typed source
-// Vitest's Oxc transform can't parse — so only the members used as values are faked.
-vi.mock('expo-modules-core', () => ({
-  UnavailabilityError: class UnavailabilityError extends Error {
-    constructor(moduleName: string, propertyName: string) {
-      super(`${propertyName} is not available on ${moduleName}`);
-    }
-  },
-}));
-
-const { isAvailableAsync, shareAsync } = await import('./sharing');
-
-const LOCAL_FILE_URL = 'file:///tmp/report.pdf';
-
-afterEach(() => {
-  vi.clearAllMocks();
-});
-
-describe('isAvailableAsync', () => {
-  it('reports availability from the presence of the native share method', async () => {
-    await expect(isAvailableAsync()).resolves.toBe(true);
-  });
-
-  it('reports unavailable when the native module cannot share', async () => {
-    const { shareAsync: native } = FAKE_NATIVE_SHARING;
-    // @ts-expect-error -- simulating a platform where the native module has no such method
-    FAKE_NATIVE_SHARING.shareAsync = undefined;
-
-    await expect(isAvailableAsync()).resolves.toBe(false);
-
-    FAKE_NATIVE_SHARING.shareAsync = native;
-  });
-
-  it('defers to the native check when the module implements one', async () => {
-    const nativeCheck = vi.fn(async () => false);
-    Object.assign(FAKE_NATIVE_SHARING, { isAvailableAsync: nativeCheck });
-
-    await expect(isAvailableAsync()).resolves.toBe(false);
-    expect(nativeCheck).toHaveBeenCalled();
-
-    Reflect.deleteProperty(FAKE_NATIVE_SHARING, 'isAvailableAsync');
-  });
-});
-
-describe('shareAsync', () => {
-  it('passes the url and options straight through', async () => {
-    await shareAsync(LOCAL_FILE_URL, { mimeType: 'application/pdf', dialogTitle: 'Send report' });
-    expect(FAKE_NATIVE_SHARING.shareAsync).toHaveBeenCalledWith(LOCAL_FILE_URL, {
-      mimeType: 'application/pdf',
-      dialogTitle: 'Send report',
-    });
-  });
-
-  it('defaults the options to an empty object', async () => {
-    await shareAsync(LOCAL_FILE_URL);
-    expect(FAKE_NATIVE_SHARING.shareAsync).toHaveBeenCalledWith(LOCAL_FILE_URL, {});
-  });
-
-  it('forwards the iPad anchor rectangle unflattened', async () => {
-    const anchor = { x: 10, y: 20, width: 1, height: 1 };
-    await shareAsync(LOCAL_FILE_URL, { anchor });
-    expect(FAKE_NATIVE_SHARING.shareAsync).toHaveBeenCalledWith(LOCAL_FILE_URL, { anchor });
-  });
-
-  it('throws an UnavailabilityError-shaped error when the native method is absent', async () => {
-    const { shareAsync: native } = FAKE_NATIVE_SHARING;
-    // @ts-expect-error -- simulating a platform where the native module has no such method
-    FAKE_NATIVE_SHARING.shareAsync = undefined;
-
-    await expect(shareAsync(LOCAL_FILE_URL)).rejects.toThrow(
-      'shareAsync is not available on expo-sharing',
-    );
-
-    FAKE_NATIVE_SHARING.shareAsync = native;
-  });
-});
-
-// Validation happens before the native call so a bad url fails with a readable message here
-// rather than as an argument-conversion failure on iOS or a generic share failure on Android.
-describe('url validation', () => {
-  it('rejects an empty url', async () => {
-    await expect(shareAsync('')).rejects.toThrow(/Invalid url provided to Sharing/);
-    expect(FAKE_NATIVE_SHARING.shareAsync).not.toHaveBeenCalled();
-  });
-
-  it('rejects a non-string url before reaching the native module', async () => {
-    // @ts-expect-error -- the guard exists precisely for callers without type checking
-    await expect(shareAsync(undefined)).rejects.toThrow(/Invalid url provided to Sharing/);
-    expect(FAKE_NATIVE_SHARING.shareAsync).not.toHaveBeenCalled();
-  });
-});