CRITICAL FIX: VFS bug that persisted through v4.5.1-v4.7.4 is NOW FIXED.
Root Cause:
- Storage adapters were not properly extracting standard fields from metadata
- This caused getVerbsBySource_internal() to return 0 relationships despite relationships existing
- VFS PathResolver couldn't navigate directory structure
Solution - Metadata Architecture Refactoring:
1. Move standard fields to top-level of HNSWNounWithMetadata and HNSWVerbWithMetadata
- type, createdAt, updatedAt, confidence, weight, service, data, createdBy
2. Update all 9 storage adapters to extract standard fields from metadata on load
3. Maintain backward compatibility at storage layer (metadata files unchanged)
Changes:
- src/coreTypes.ts: Update HNSWNounWithMetadata and HNSWVerbWithMetadata interfaces
- Add top-level standard fields
- Change data type from unknown to Record<string, any>
- Add confidence field to GraphVerb
- src/storage/baseStorage.ts: Add type cast pattern for standard field extraction
- src/storage/adapters/*.ts: Fix all 9 adapters (memoryStorage, fileSystemStorage, gcsStorage,
s3CompatibleStorage, r2Storage, opfsStorage, azureBlobStorage, typeAwareStorageAdapter)
- Extract standard fields from metadata on load
- Place at top-level of returned entities
- src/api/DataAPI.ts: Read fields from top-level instead of metadata
- src/graph/graphAdjacencyIndex.ts: Convert HNSWVerbWithMetadata to GraphVerb format
- src/utils/metadataIndex.ts: Fix typo (metadata → entityOrMetadata)
- src/types/brainy.types.ts: Add createdBy field to AddParams
- src/types/graphTypes.ts: Add service field to GraphVerb
Test Results:
✅ VFS bug FIXED - vfs.readdir('/') now returns files (was returning empty array)
✅ getVerbsBySource_internal() now returns relationships correctly
✅ Build succeeds with ZERO compilation errors
✅ 95.7% of tests pass (954/997)
Breaking Changes:
- None - backward compatibility maintained at storage layer
Version: 4.8.0
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Extends the import progress callback system to provide real-time updates during
the relationship building phase, eliminating the 1-2 minute silent period for
large imports.
New Features:
- Progress callbacks now fire during relationship building (brain.relateMany)
- New 'phase' field distinguishes 'extraction' vs 'relationships' phases
- Chunk-based progress emission (<0.01% overhead for 573 relationships)
- Works across all import paths: ImportCoordinator, SmartImportOrchestrator, UniversalImportAPI
API Enhancements:
- ImportProgress: Added 'phase' and 'current' fields
- SmartImportProgress: Added 'relationships' phase
- NeuralImportProgress: New interface for UniversalImportAPI
- Refactored to use brain.relateMany() for batch operations
Examples:
- NEW: examples/import-with-progress.ts - Complete demo with progress bars and ETA
- UPDATED: examples/complete-import-demo.ts - Shows both extraction and relationship phases
Performance:
- Minimal overhead: 6 callbacks for 573 relationships = 0.6ms / 5730ms = 0.01%
- Chunk size: 100 relationships per batch (configurable)
- Storage agnostic: Works with all adapters (FileSystem, S3, R2, GCS, Memory, OPFS, TypeAware)
Backward Compatible:
- All new fields are optional
- Existing code continues to work unchanged
- Zero breaking changes
This addresses the UX issue where users couldn't tell if imports were frozen
during the relationship building phase for large datasets.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Updated all fs, path, crypto, os, url, util, events, http, https, net, child_process, stream, and zlib imports
- Changed both static imports and dynamic imports to use node: protocol
- This makes Brainy more bundler-friendly by explicitly marking Node.js built-ins
- Prevents bundlers from attempting to polyfill or bundle these modules
- Reduces bundle size for web applications using Brainy
- Improves tree-shaking and dead code elimination
Benefits for external bundlers:
- Clear distinction between Node.js built-ins and external dependencies
- No ambiguity about what needs polyfilling
- Smaller bundles for browser builds
- Better compatibility with modern bundlers (Webpack 5, Vite, Rollup, esbuild)
🤖 Generated with Claude Code
Co-Authored-By: Claude <noreply@anthropic.com>
