fix: Inconsistent SQL Migration Files Processing Across Different Operating Systems

[canisminor1990]

Description

When using the readMigrationFiles function, the generated SQL arrays differ between Windows and macOS/Linux environments due to different line ending conventions.

Current Behavior

The readMigrationFiles function reads SQL files and splits them at statement breakpoints. However, it preserves the native line endings:

• On Windows: Lines end with \r\n (CRLF)
• On macOS/Linux: Lines end with \n (LF)

This causes inconsistency in the resulting SQL arrays:

On macOS:

"sql": [
  "ALTER TABLE \"messages\" ADD COLUMN \"client_id\" text;",
  "\nALTER TABLE \"session_groups\" ADD COLUMN \"client_id\" text;",
  // ...more statements with \n line breaks
]

On Windows:

"sql": [
  "ALTER TABLE \"messages\" ADD COLUMN \"client_id\" text;",
  "\r\nALTER TABLE \"session_groups\" ADD COLUMN \"client_id\" text;",
  // ...more statements with \r\n line breaks
]

Expected Behavior

The function should produce consistent SQL arrays regardless of the operating system where it runs.

Proposed Solution

Normalize line endings when reading SQL files:

const query = fs.readFileSync(`${migrationFolderTo}/${journalEntry.tag}.sql`)
  .toString()
  .replace(/\r\n/g, '\n'); // Normalize all line endings to LF

This simple change ensures consistent behavior across all platforms.

---

• refs: [BUG]: readMigrationFiles (drizzle-orm/migrator) Inconsistent SQL Migration Files Processing Across Different Operating Systems #4329