chore: organize code in modules, absolute imports, better exports

[Lukapetro]

Refactor: Reorganize Project Structure with Modular Design

Reorganizes codebase with a modular, feature-based architecture:

src/
  core/                   # Core functionality
    auth/
    api/
    types/
    utils/
  features/              # Feature modules
    tweets/
    profiles/
    search/
    relationships/
    messages/
    spaces/
      core/
      plugins/
    trends/
  timeline/              # Timeline related functionality
    components/
    types/
  platform/              # Platform specific code
  cli/                   # Command line interface
  scraper/               # Main scraper functionality
  index.ts              # Main library entry point

Changes:

• Moves files into feature-based modules
• Each feature has its own types, tests, and utils
• Core functionality separated from features
• Path aliases enable clean imports (@/core/auth vs ../../core/auth)

Example changes:

• Before: import { TwitterAuth } from '../../core/auth/auth'
• After: import { TwitterAuth } from '@/core/auth'

⚠️ NOTE: This refactor has high impact! Thorough testing needed to catch any broken imports or functionality.

Testing Strategy:

1. Do manual testing of core features
2. Test import functionality in various modules
3. Verify build process works
4. Test published package imports

[Lukapetro]

@wtfsayo after this is merged i can take a look at:

• Retry on timeout should be configurable #46
• make sure all tests are passing! #44

[Lukapetro]

⚠️ NOTE: This refactor has high impact! Thorough testing needed to catch any broken imports or functionality. DO NOT MERGE BLINDLY, it may break features around

[HashWarlock]

I see some imports use @ then others use ../../src is there a reason for this that I'm missing or can they all move to use @ with this change now?

[Lukapetro]

we can use absolute import everywhere @HashWarlock, where you see the imports with ../../ is because there is the old import left that I missed

[wtfsayo]

why inconsistent with @/... path and ../

[Lukapetro]

why inconsistent with @/... path and ../

aight let me fix those, also another thing I've seen is having a convention for naming files. Example:

• ChatClient.ts -> PascalCase
• testParticipant.ts -> camelCase
• platform-interface.ts -> kebab-case

For convenience I would say define a standard and adapt the code. Maybe just a separate doc for the whole elizaOS organization, which applies to all repos @wtfsayo @lalalune

[wtfsayo]

hey so I think the code organisation is good but its hard to truly test unless this is followed up #44;

if you take on #44 you can base it off this branch and can merge together