[Bug]: Investigate StudioCMS windows compatibility issues

[Adammatthiesen]

What happened?

There has been reports on our Discord that users have been unable to run StudioCMS on Windows platforms directly.

Reference: https://discord.com/channels/1309279407743172608/1441857861859672216

Package

studiocms

Version

0.1.0-beta.30

What browsers are you seeing the problem on?

No response

Relevant log output

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and agent prompts for this issue.

• Create Plan

Examples

• Example 1
• Example 2

🔗 Similar Issues

Related Issues

• withstudiocms/studiocms#587
• withstudiocms/studiocms#878
• withstudiocms/studiocms#535
• withstudiocms/ui#135
• withstudiocms/studiocms#449

👤 Suggested Assignees

• Adammatthiesen

---

🧪 Issue enrichment is currently in early access.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

[louisescher]

Related stack trace I got when trying to run the dev command for the StudioCMS repo on a Windows machine:

playground dev: 08:56:23 [vite] (ssr) Error when evaluating SSR module C:\Users\louis\Documents\source\projects\studiocms\playground\astro.config.mts: Only URLs with a scheme in: file, data, and node are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 'c:'
playground dev:       at throwIfUnsupportedURLScheme (node:internal/modules/esm/load:187:11)
playground dev:       at defaultLoad (node:internal/modules/esm/load:82:3)
playground dev:       at ModuleLoader.load (node:internal/modules/esm/loader:815:12)
playground dev:       at ModuleLoader.loadAndTranslate (node:internal/modules/esm/loader:594:31)
playground dev:       at #createModuleJob (node:internal/modules/esm/loader:624:36)
playground dev:       at #getJobFromResolveResult (node:internal/modules/esm/loader:343:34)
playground dev:       at ModuleLoader.getModuleJobForImport (node:internal/modules/esm/loader:311:41)
playground dev:       at async onImport.tracePromise.__proto__ (node:internal/modules/esm/loader:664:25)
playground dev: [astro] Unable to load your Astro config
playground dev: Only URLs with a scheme in: file, data, and node are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 'c:'
playground dev:   Stack trace:
playground dev:     at throwIfUnsupportedURLScheme (node:internal/modules/esm/load:187:11)
playground dev:     at ModuleLoader.load (node:internal/modules/esm/loader:815:12)
playground dev:     at #createModuleJob (node:internal/modules/esm/loader:624:36)
playground dev:     at ModuleLoader.getModuleJobForImport (node:internal/modules/esm/loader:311:41)
playground dev: Failed

[Adammatthiesen]

Related stack trace I got when trying to run the dev command for the StudioCMS repo on a Windows machine:

@louisescher If only that stack traced actually pointed to the real source.... instead of just vite/note esm loader errors... 😢 (this has been the primary issue, since my system refuses to windows)