Fix module resolution errors in Node.js production deployment

Update import statements and file paths to correctly resolve modules in the production Node.js environment by adding `.js` extensions and adjusting relative paths for compiled ES modules.

Replit-Commit-Author: Agent
Replit-Commit-Session-Id: ceced2fc-aa46-458d-ba87-ddd4b7bb1518
Replit-Commit-Checkpoint-Type: full_checkpoint
Replit-Commit-Screenshot-Url: https://storage.googleapis.com/screenshot-production-us-central1/659922a9-0087-461c-90dd-6d9a58b81d4d/ceced2fc-aa46-458d-ba87-ddd4b7bb1518/SBF5OKZ
This commit is contained in:
paul-nothaft
2025-10-23 16:25:00 +00:00
parent d6d23e74e1
commit 35c0889e05
3 changed files with 213 additions and 2 deletions
+2 -2
View File
@@ -140,9 +140,9 @@ export class MemStorage implements IStorage {
}
}
import { getDatabase } from './db';
import { getDatabase } from './db.js';
import { eq } from 'drizzle-orm';
import * as schema from '@shared/schema';
import * as schema from '../shared/schema.js';
export class DbStorage implements IStorage {
private db = getDatabase();