Error ERR_INVALID_FILE_URL_PATH en Windows al ejecutar embedding-sdk-react start

Nobody has claimed this yet.

### Bug description

I'm trying to use `@metabase/embedding-sdk-react` on Windows, but running the command throws an error related to `fileURLToPath`, complaining that the file URL path must be absolute.

This prevents me from running the SDK successfully.
TypeError [ERR_INVALID_FILE_URL_PATH]: File URL path must be absolute
at getPathFromURLWin32 (node:internal/url:1479:11)
at fileURLToPath (node:internal/url:1510:35)
---

### Steps to reproduce

1. I created my project in:
C:\Users\username\Documents\Proyectos

2. Installed the SDK locally with:
npm install @metabase/embedding-sdk-react --save-dev

3. Ran the SDK with:
npx embedding-sdk-react start

4. I immediately get the error shown above.

---

### Expected behavior

The SDK should start without throwing errors on Windows.
It should properly resolve `file:///` URLs and handle absolute paths without issues.

---

### Environment information

- **Operating System:** Windows 11
- **Node.js version:**

Result: `v22.14.0`

- **SDK version:**

Result: `@metabase/embedding-sdk-react@0.54.5`

- **Project location:** `C:\Users\username\Documents\Proyectos`
- **How installed:** local dev dependency

---

### Additional context

- I’ve tried moving the project to a local path on **C:** drive instead of a network or external drive.
- Tried with the latest Node.js LTS version.
- Tried installing the SDK both globally and locally.
- Cleaned `node_modules` and reinstalled dependencies from scratch.
- The error seems to be that the SDK generates or passes a non-absolute or incorrectly formatted file URL on Windows, which throws an exception from Node's internal `fileURLToPath` call.
- Could be specific to path handling on Windows platform

Thank you!

---

Start by reproducing `npx embedding-sdk-react start` in a Windows 11 project using Node.js v22.14.0 and `@metabase/embedding-sdk-react@0.54.5`. Trace the command's entry point and the `fileURLToPath` call involved in resolving the project path. Done means the SDK starts successfully from the reported Windows path without `ERR_INVALID_FILE_URL_PATH`.

Written by the indexing model from the issue text.