feat: Import .jsonl file with events into the events table

[Anshumancanrock]

Description

Implements a CLI utility for importing NIP-01 events from .jsonl files into the events table.

• Streams the file line-by-line via readline to keep memory usage constant regardless of file size.
• Validates every event before insertion: Joi schema, SHA-256 id hash, and Schnorr signature.
• Inserts events in batched database transactions (default batch size: 1000, configurable via --batch-size).
• Handles all event kinds consistently with the relay: regular inserts with ON CONFLICT DO NOTHING, replaceable/parameterized replaceable upserts using the existing replaceable_events_idx, delete event application in stream order, and ephemeral event filtering.
• Duplicates are skipped gracefully without interrupting the import.
• Interacts directly with the database layer via Knex, bypassing WebSocket and rate limiting.

Related Issue

Closes #406

Motivation and Context

There's no built-in way to seed a relay with existing data or migrate events from another relay. This adds a straightforward CLI for it.

How Has This Been Tested?

• 4 new unit tests covering batching, duplicate tracking, error counting, and persistence failure propagation.
• Full existing test suite passes (493/493).
• TypeScript build and ESLint both clean.

Tested locally against a real PostgreSQL instance , imported 463 events from a .jsonl file and all inserted successfully in ~1s. Progress tracking and final summary both working as expected.

Types of changes

• Non-functional change (docs, style, minor refactor)
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my code changes.
• All new and existing tests passed.

[Anshumancanrock]

Hi @cameri, I tested the imports locally and they work fine. Please take a look when you’re free and let me know if you’d like any changes. Thanks!

[cameri]

Thank you. I will send you an events database for you to test this against. Stay tuned.

[cameri]

My concern here is that this query will drift from the queries in the EventRepository over time.

Is there a reason why the event import service essentially re-implements the database layer instead of re-using it?

[Anshumancanrock]

Hi @cameri, I’ve updated the importer to reuse EventRepository batch writes. It now streams .jsonl line by line, validates each event (schema, id hash, and signature), and persists them in batches: regular events via createMany, replaceable via upsertMany, and delete events via flush + deleteByPubkeyAndIds+ storing the delete event.

Ephemeral events are skipped, duplicates are handled gracefully, and progress/errors are reported during import.

Am i doing something wrong in this approch? Please let me know.