This PR resolves two critical issues that prevented the typesync application from building and running correctly on Windows environments. These changes ensure a consistent developer experience across all operating systems.

[JoMind]

Key Changes

1. Use rimraf for the "clean" script

   rm -rf is not available on Windows. apps/typesync/package.json now uses rimraf so the command works on all platforms.

2. Ship a cross-platform File-system migration loader

   Problem – The loader that ships with @effect/sql builds the specifier for import() with an OS-specific path (e.g. C:\project\…\1_init.js). On Windows, the Node.js ESM resolver treats the leading C: as a URL scheme and throws the following error:

   Only URLs with a scheme in: file, data, and node are supported …
   Received protocol 'c:'

   (See nodejs/node#31710, effect-ts/effect#4297).

   Fix – We added src/Utils.ts::fromFileSystem() which:

   • Keeps directory as a plain OS path when calling FileSystem.readDirectory.
   • Converts the specifier given to import() with pathToFileURL(...).href (e.g. file:///C:/project/…/1_init.js).
   • Accepts both / and \ in the filename RegExp.

   The loader is plugged into DatabaseService:

   import { fromFileSystem } from "./Utils.js";
   
   const MigratorLive = Migrator.layer({
     loader: fromFileSystem(
       fileURLToPath(new URL("migrations", import.meta.url)),
     ),
   }).pipe(Layer.provide(SqlLive));

   Behaviour on Linux/macOS is unchanged; migrations now load on Windows as well.

These two changes eliminate the build error on clean and the runtime error, so the project builds and runs successfully on Windows, Linux, and macOS.

[Copilot]

Pull Request Overview

This PR ensures typesync builds and runs on Windows by replacing platform-specific scripts and fixing dynamic import paths.

• Swaps rm -rf for cross-platform rimraf in the clean script
• Introduces fromFileSystem to convert OS paths to file:// URLs for the migration loader
• Updates Database.ts to use the new loader

Reviewed Changes

Copilot reviewed 3 out of 4 changed files in this pull request and generated 2 comments.

File	Description
apps/typesync/package.json	Replaced "rm -rf" with "rimraf" in the clean script and added rimraf to devDependencies
apps/typesync/src/Utils.ts	Added fromFileSystem loader that uses pathToFileURL to support Windows migration imports
apps/typesync/src/Database.ts	Switched Migrator loader to use the new fromFileSystem function

Files not reviewed (1)

• pnpm-lock.yaml: Language not supported

Comments suppressed due to low confidence (2)

apps/typesync/src/Utils.ts:146

• Add unit tests for the fromFileSystem loader to cover both POSIX and Windows-style file names and ensure that the import() URL conversion behaves correctly under each environment.

export const fromFileSystem = (

apps/typesync/src/Utils.ts:139

• Expand the JSDoc for fromFileSystem to include a description of the dir parameter and the returned loader type, clarifying expected input and behavior.

/**

[Copilot]

Use path.join or path.resolve to combine dir and basename when constructing the file path, e.g., pathToFileURL(path.join(dir, basename)).href for clarity and cross-platform safety.

[Copilot]

[nitpick] Add a semicolon at the end of this statement to maintain consistency with the surrounding code style.

Suggested change

	}).pipe(Layer.provide(SqlLive))
	}).pipe(Layer.provide(SqlLive));

[nikgraf]

@JoMind great changes, thanks! Can you reapply your commits as signed commits. Due merge rules I can't merge in the organization I can't merge without.

If too complicated let me know and I can try to get your commits and re-apply them manually.

[JoMind]

@JoMind great changes, thanks! Can you reapply your commits as signed commits. Due merge rules I can't merge in the organization I can't merge without.

If too complicated let me know and I can try to get your commits and re-apply them manually.

Sure, signed.