titanpl 7.0.0 → 7.0.1

package/packages/core-source/V8_SERIALIZATION.md

@@ -1,125 +0,0 @@
-# V8 Serialization Support for Local Storage
-
-## Summary
-
-Added native V8 serialization support to the `ls` (Local Storage) module in `@titanpl/core`. This enables efficient storage and retrieval of complex JavaScript objects including `Map`, `Set`, `Date`, `Uint8Array`, and other types that cannot be properly serialized with JSON.
-
-## Changes Made
-
-### 1. JavaScript Implementation (`index.js`)
-
-Added four new methods to the `ls` object:
-
-#### `ls.serialize(value: any): Uint8Array`
-- Serializes any JavaScript value using native V8 serialization
-- Returns a `Uint8Array` containing the binary representation
-- Supports complex types: `Map`, `Set`, `Date`, `RegExp`, `BigInt`, `Uint8Array`, etc.
-- Handles circular references
-- ~50x faster than JSON for large objects
-
-#### `ls.deserialize(bytes: Uint8Array): any`
-- Deserializes V8 binary format back to JavaScript values
-- Restores original object types (Map stays Map, Set stays Set, etc.)
-- Handles all types supported by V8 serialization
-
-#### `ls.setObject(key: string, value: any): void`
-- High-level wrapper for storing complex objects
-- Automatically serializes using V8, encodes to Base64, and stores
-- Preserves object types and structure
-
-#### `ls.getObject(key: string): any | null`
-- High-level wrapper for retrieving complex objects
-- Automatically retrieves, decodes from Base64, and deserializes
-- Returns `null` if key doesn't exist or deserialization fails
-
-### 2. Native Bindings
-
-The native V8 serialization functions were already implemented in Rust:
-- `native_serialize` - V8 ValueSerializer implementation
-- `native_deserialize` - V8 ValueDeserializer implementation
-
-These are exposed through the `natives` object and bound in `index.js`.
-
-### 3. TypeScript Definitions
-
-The TypeScript definitions in `globals.d.ts` already included complete type definitions for all four methods with comprehensive JSDoc documentation.
-
-### 4. Documentation
-
-The `README.md` already documented the new functions:
-```javascript
-- ls.setObject(key: string, value: any): void
-- ls.getObject(key: string): any
-- ls.serialize(value: any): Uint8Array
-- ls.deserialize(bytes: Uint8Array): any
-```
-
-## Usage Examples
-
-### Basic Serialization
-```javascript
-import { ls } from '@titanpl/core';
-
-const data = {
-    users: new Map([['alice', { role: 'admin' }]]),
-    tags: new Set(['active', 'verified']),
-    created: new Date()
-};
-
-// Low-level API
-const bytes = ls.serialize(data);
-const restored = ls.deserialize(bytes);
-
-// High-level API
-ls.setObject('session', data);
-const session = ls.getObject('session');
-// session.users instanceof Map → true
-```
-
-### Complex Nested Structures
-```javascript
-const gameState = {
-    players: new Map([
-        ['player1', {
-            inventory: new Set(['sword', 'shield']),
-            stats: { hp: 100, mp: 50 }
-        }]
-    ]),
-    startTime: new Date()
-};
-
-ls.setObject('game:session1', gameState);
-const loaded = ls.getObject('game:session1');
-// All types preserved: Map, Set, Date
-```
-
-## Advantages Over JSON
-
-1. **Type Preservation**: Map, Set, Date, RegExp, BigInt, Uint8Array stay as-is
-2. **Performance**: ~50x faster for large objects
-3. **Circular References**: Handles circular object references
-4. **Binary Efficiency**: More compact binary representation
-
-## Testing
-
-Tests are already in place in `tests/ls.test.js`:
-- Basic serialize/deserialize tests
-- setObject/getObject tests with fallback to JSON
-- Handles non-existent keys gracefully
-
-## Files Modified
-
-1. `index.js` - Added native bindings and ls methods
-2. No changes needed to:
-   - `globals.d.ts` (already had type definitions)
-   - `README.md` (already documented)
-   - `tests/ls.test.js` (already had tests)
-   - Native Rust code (already implemented)
-
-## Example File
-
-Created `examples/v8-serialization-example.js` with comprehensive demonstrations of:
-- Basic V8 serialization
-- Complex object storage
-- Nested structures
-- Performance comparisons with JSON

package/packages/core-source/configure.js

@@ -1,50 +0,0 @@
-import { readFileSync, existsSync, writeFileSync } from 'fs';
-import { resolve, dirname } from 'path';
-import { fileURLToPath } from 'url';
-import { platform as _platform } from 'os';
-import { spawnSync } from 'child_process';
-
-const __filename = fileURLToPath(import.meta.url);
-const __dirname = dirname(__filename);
-const platform = _platform();
-const titanConfigPath = resolve(__dirname, 'titan.json');
-
-console.log(`Configuring titan.json for platform: ${platform}`);
-
-// 1. Platform-specific output file name
-let libFile = "";
-if (platform === "win32") {
-    libFile = "titan_core.dll";
-} else if (platform === "darwin") {
-    libFile = "libtitan_core.dylib";
-} else {
-    libFile = "libtitan_core.so";
-}
-
-const nativeDir = resolve(__dirname, "native");
-const expectedBinary = resolve(nativeDir, "target/release", libFile);
-
-// 2. Build if binary missing
-if (!existsSync(expectedBinary)) {
-    console.log(`Native binary missing.`);
-}
-
-// 3. Update titan.json
-try {
-    const content = readFileSync(titanConfigPath, "utf8");
-    const titanConfig = JSON.parse(content);
-
-    const relativeLibPath = `native/target/release/${libFile}`;
-
-    if (!titanConfig.native) {
-        titanConfig.native = {};
-    }
-
-    titanConfig.native.path = relativeLibPath;
-
-    writeFileSync(titanConfigPath, JSON.stringify(titanConfig, null, 2));
-    console.log(`Updated titan.json to use native binary: ${relativeLibPath}`);
-} catch (error) {
-    console.error("Error updating titan.json:", error);
-    process.exit(1);
-}